Module 6 - Information Architecture / Information Systems Architecture
Overview Module 6 defines the Information Architecture or Information Systems Architecture within an organisation. The module focusses on identifying data, integration and applications required to support the different functions, capabilities and processes within the organisation. The module expands the business architecture converting the business view of the architecture into a more technically functional view of the architecture. With the aid of visual tools, the information architecture aims to communicate the core components of ICT needed to support the organisation.
Module Objectives This module addresses the following objectives 1. Understand reference models and how to develop them 2. Enterprise applications 3. Understand information maps and data 4. Integration and integration patterns 5. Role of security and privacy
Components of Information Architecture
Information architecture is comprised of several components, Figure 32. These components include 1. Applications – the category or types of systems needed to support the organisation. 2. Data – the information required to run the organisation 3. Integration – the ways in which applications and data are connected within the organisation. This is not shown individually in the Figure below but rather implied as a component of Data. Integration is shown as a separate component based on the critical nature of the service and the specialised technology and skills required to support this component.
Figure 1 : Content Metamodel Overview Source TOGAF (2011)
Reference Models
Reference models are generic models which represent the applications, data and integration for a specific industry. These models are normally developed managed and maintained by different industry specific companies using community resources to contribute to the development and refinement of these models. Examples of these include: 1. ARTS data model – Retail data model 2. Energistics data model – Energy data model 3. OMG – object meta group has a number of software models for different industries.
TOGAF, (2011) outlines several types of common architectures, reference models. These reference models range from foundation (generic) to organisation specific. The reference models also depict abstract concepts such as architecture as well as physical concepts such as solutions. Reference models will be revisited in Module 7 – Technology architecture. A reference model can be decomposed or elaborated into greater levels of details as it moves from generic to specific. The amount of reuse for the model also decreases as one moves from generic to specific.
Figure 2 : Reference Models Source TOGAF (2011) Reading
Selected Reading 6.1 The Open, G 2011, TOGAF Version 9.1.
Read Chapter 35 Section 1 and 2.
TOGAF, (2011) Section 35.1 introduces some basic concepts and definitions. This introduces the concept of concerns. Concerns relate to the main problems / interests a stakeholder perceives and are crucially important to the success of a system. These concerns are different to requirements.
These different models provide a frame of reference for organisations and act as a blueprint. The reference models can be used to model different viewpoints and address different stakeholder concerns.
Reference models simplify and abstract a lot of detail to make information relevant to the different stakeholders.
Reading
Selected Reading 6.2 Government, A 2016, Australian Government Architecture Reference Models, Australia Government, Department of Finance.
http://www.finance.gov.au/policy-guides-procurement/australian-government-architectureaga/aga-rm/2-reference-model-overview/
The Australian Government has developed a series of reference models to represent different domains (data, service, performance) of the architecture. The models are used to allow stakeholders to visualize components and allow for interagency collaboration. They describe the most important components of the architecture and aid in developing a consistent and common framework. Reference models are developed at a high level in order to remove complexity focusing on concepts. This allows for different stakeholders, technical and non-technical to review, discuss and validate gaining a common understanding.
Applications
Applications Architecture is the organisational view of all the software required to support the business and its processes. This includes the interactions, interdependencies and interoperations between the applications. At the information architecture level the applications are not specific to the actual software, vendor and solution but remains abstracted at the definition or category level.
Gartner, (2016) developed the magic quadrant, a method for analyzing the capabilities of vendors and their software. The software is categorized into different categories in order to compare these different capabilities. Forrester, (2016) developed a similar methodology called the Wave methodology to assess software. Each of these vendors has categorised software.
The levels of the categories provide a good foundation for the description of applications. Understanding the capabilities, features and benefits of the applications without the low level detail of the vendor, software and versions.
Examples of these categories include: 1. Enterprise Resource Planning (ERP) 2. Customer Relationship Management (CRM)
3. Collaboration, messaging and email
In the figure below, Microsoft (2012), Micrsoft Industry Architecture for Banking outlines an Information Architecture. The section LOB Application Platform outlines the categories of the applications which can support the organisation.
There are many different ways in which this information can be displayed. The importance is to understand the stakeholder to which the information is being presented and tailor the view and viewpoint for the stakeholder. Therefore, you may have many different viewpoints representing the same information.
Mapping applications to one or more business capabilities allows an organisation to understand how applications support the business.
Figure 3 : Logical Reference Model Source Microsoft (2012)
Selected Reading 6.3 The Open, G 2011, TOGAF Version 9.1.
Read Chapter 11 Section 11.1 and 11.2
TOGAF, (2011) outlines the need for an understanding of the target application architecture which can support the business architecture and the architecture vision. This concept ensures that applications are being selected to support business capabilities and the concerns and requirements of the business.
Assignment Exercise Use the organisation selected and use your capability model and develop the following matrices: 1. Application / Capability matrix 2. Application/ Stakeholder or Role matrix
Data
Kitchin, (2014) identifies data as a key resource in the modern world.
Figure 4 : Knoweldge Pyramid Source Kitchin (2014) Kitchin (2014) presents the above figure of a knowledge pyramid to depict the different types of information. One can see from the pyramid that as you progress up the pyramid information becomes more actionable, being able to provide organisations with valuable insights. When mapping information in a information architecture it is important to understand which information is required by the different business capabilities. Data is captured during the different business processes. Understanding what information supports the business processes and capabilities is key to understanding how this information can be used to gain valuable insights and competitive advantage.
Gaining a common understanding and definition of information across different capabilities and processes is key to being able to use the information.
Figure 5 : Data Management Maturity Model Source CMMI Institute, (2016)
Data Management is a discipline on its own as outline by CMMI Institute, (2016) in the above figure.
Figure 6 : DAMA Framework Source DAMA, (2014) Likewise, DAMA (2014) has a similar framework for the management of information. Data is becoming viewed as an asset within an organisation and a way of delivering value. In Module 3 we discussed the concept for an organisation to become more customer centric. Collecting data on a customer and analysing this information to understand them is a common way to become more customer centric. As the world becomes more digitally enabled, the creation and use of data (machine data and user data) will exponentially increase.
Reading
Selected Reading 6.4 Kitchin, R 2014, The Data Revolution: Big Data, Open Data, Data Infrastructures and Their Consequences, London, viewed 2016/11/05, .
Read Chapter 1
Kitchin, R (2014) defines data and provides examples of the different types of data. Storing data requires significant thought and design so as to make information consistent across multiple data sets. With the increase in information and the exchange of information standards and definitions are essential to facilitate the sharing of information.
Selected Reading 6.5 DAMA 2014, DAMA-DMBOK2 Framework, DAMA, USA, https://www.dama.org/>.
Read Section 4.1 Knowledge Areas The different knowledge areas give you a perspective on the way to manage and maintain information.
Selected Reading 6.6 The Open, G 2011, TOGAF Version 9.1.
Read Chapter 10 Section 10.1 and 10.2
TOGAF (2011) outlines some key considerations for data architecture being 1. Data management 2. Data migration 3. Data governance
As can be seen from the more specialised frameworks of CMMI and DAMA, they focus on data where TOGAF gives a more general overview of Data architecture.
Selected Reading 6.7 Ambler, S 2013, Data Modeling 101, Agile Data, viewed 5/11/2016, .
Data modeling is a technique which is used to represent data and its relationships. Ambler,S (2013) outlines the fundamental skills used to enable one to model and present information.
Assignment Exercise Select the organisation you have identified and use your capability model to develop the following matrices: 1. Application / Data matrix 2. Data / Capability matrix 3. Data / Stakeholder or Role matrix
Identify the core data which will be used in the applications, its relationships between the data. Develop a high level data model to represent the data and relationships. Also remember to develop a glossary with a unique definition for each entity.
Integration
Data moves between applications inside and outside of an organisation. Depending on the classification of data, the frequency of interchange, the volume of data and privacy there are several ways information can be shared: 1. Real time a. Messaging b. Application programming interfaces c. Direct integration 2. Batch a. File transfer b. Direct integration
Reading
Selected Reading 6.8 Ferreira, DR 2013, Enterprise systems integration: a process-oriented approach, Springer, Heidelberg.
Read Chapter 1
Figure 7 : Integration options Source Ferreira, DR (2013)
Ferreira, DR (2013), outlines the evolution of integration options from 1970 till today in Figure 38 above.
Figure 8 : Point to Point integration Source Ferreira, DR (2013)
Systems can be integrated individually providing a point to point integration option. This is costly and becomes complex as applications expand within an organisation as depicted in Figure 39 above.
Figure 9 : Orchestration and Messaging integration Source Ferreira, DR (2013)
Applications connect in an efficient manner through orchestration or messaging in place of point to point outlined in Figure 40.
Reading
Selected Reading 6.9 Mulesoft 2016, Microservices vs Monolithic Architecture, Mulesoft, viewed 11/2016, .
Read entire article
Selected Reading 6.10 Clark, K 2016, Microservices, SOA, and APIs: Friends or enemies?, IBM, http://www.ibm.com/developerworks/websphere/library/techarticles/1601_clarktrs/1601_clark.html>.
Read entire article
Clark, K 2016 explains the differences between microservices, API’s and service orientated architectures. As can be seen from Figure 41 below these are not exclusive and can work together.
Figure 10 : SOA’s, API’s and Microservices Source Clark K (2016)
Clark K (2016) outlines the similarities and differences of these components as
• Microservices architecture is an alternative approach to structuring applications. An application is broken into smaller, completely independent components, enabling them to have greater agility, scalability, and availability. • Service Orientated Architecture (SOA) exposes the functions of applications as more readily accessible service interfaces, making it easier to use their data and logic in the next generation of applications. • APIs (Application Programming Interface) is commonly used to refer to any interface that is exposed either internally or externally • SOA and API’s are largely synonymous, as API’s are the evolution of the service exposure from SOA with increased management and security capabilities.
Optional Reading 6.11 Nadareishvili I, Mitra R, McLarty M, and Amundsen M, 2016, Microservice Architecture Aligning Principles, Practices, and Culture, O’Reilly, http://transform.ca.com/API-microservicesoreilly-landing-page-request.html
Today there are many ways to integrate systems from orchestration services, application programming interfaces, micro services, extraction, transformation and loading and file transfers. Each of these have different capabilities and depending on the requirements needed by the systems being integrated will depend on the preferred method.
The technical detail of how systems will integrate is not necessary at the information architecture level but rather the following attributes are required: 1. Frequency – how often do the applications need to integrate 2. Volume – the amount of data needed to be integrated 3. Security – how secure does the integration need to be 4. Privacy – the sensitivity of the data 5. Format - the format of the interchange
Assignment Exercise
Select the organisation you have identified and use your capability model to develop the following matrices: • Application / Data Integration matrix
Module Review Questions
1. How can application programming interfaces and microservices support organisations in being more adaptable to change? 2. Why should the service landscape be developed and aligned to the business capability model as opposed to the business processes? 3. Data provides organisations with an insight and ability to engage in a meaningful way with customers, how can organisations ensure, privacy and protection are maintained, assured and monitored?
Module Review Question Responses
1. How can application programming interfaces and microservices support organisations in being more adaptable to change? a. Microservices – an alternative approach to structuring applications. An application is broken into smaller, completely independent components, enabling them to have greater agility, scalability, and availability. b. API’s - are the evolution of the service exposure from SOA with increased management and security capabilities. 2. Why should the service landscape be developed and aligned to the business capability model as opposed to the business processes? a. Businesses change processes over time. Capabilities are more stable as business change the capabilities less frequency. Exposing capabilities allows companies to assemble and mix to deliver services and processes through orchestration. 3. Data provides organisations with an insight and ability to engage in a meaningful way with customers, how can organisations ensure, privacy and protection are maintained, assured and monitored? a. Data governance and monitoring
Module Summary
Information Architecture extents the business architecture to define application, data and integration components. At this stage you have multiple additional models or visual aids to represent the additional overlays and information on the business architecture. The purpose of the incremental information is to continually collaborate and validate the solution. Sufficient information has been collected and corroborated at the stage to start the development of the technology architecture. Defining information, integration and applications defines a modular information architecture which can respond to internal and external change.
References
Ambler, S 2013, Data Modeling 101, Agile Data, viewed 5/11/2016, .
Clark, K 2016, Microservices, SOA, and APIs: Friends or enemies?, IBM, http://www.ibm.com/developerworks/websphere/library/techarticles/1601_clarktrs/1601_clark.html>.
DAMA 2014, DAMA-DMBOK2 Framework, DAMA, USA, https://www.dama.org/>.
Ferreira, DR 2013, Enterprise systems integration: a process-oriented approach, Springer, Heidelberg.
Forrester 2016, The Forrester Wave Methodology Guide, Forrester, viewed 11/2016, .
Gartner 2016, Magic Quadrant, Gartner, USA, http://www.gartner.com/technology/research/methodologies/research_mq.jsp>.
Government, A 2016, Australian Government Architecture Reference Models, Australia Government, Department of Finance.
PMI, 2013, Managing Guide in Organisations: A Practice Guide, Project Management Institute, USQ.
CMMI Institute, 2016, Data Management Maturity, CMMI, USA, http://cmmiinstitute.com/datamanagement-maturity>.
Kitchin, R 2014, The Data Revolution: Big Data, Open Data, Data Infrastructures & Their Consequences, London, viewed 2016/11/05, .
Mulesoft 2016, Microservices vs Monolithic Architecture, Mulesoft, viewed 11/2016, .
The Open, G 2011, TOGAF Version 9.1.
Nadareishvili I, Mitra R, McLarty M, and Amundsen M, 2016, Microservice Architecture Aligning Principles, Practices, and Culture, O’Reilly, http://transform.ca.com/API-microservices-oreillylanding-page-request.html