Phase A: Architecture Vision

Stakeholder Map Matrix
  • Identifies the stakeholders
  • Their influence over the process
  • Their concerns that the architecture needs to address
Value Chain Diagram
  • High level orientation view of an enterprise
  • How enterprise interacts with the outside world
  • Allows high level execs to be quickly on boarded
  • Allows aligning stakeholders for a particular change initiative
  • Focuses on presentational impact
Solution Concept Diagram
  • Provides a high level orientation of the solution that is envisaged in order to meet the objectives of architecture engagement.
  • Not a formal document but a ‘pencil-sketch’ of the expected solution.
  • It highlights areas to be more formally investigated
  • Provides clarity to the execs in terms of the goals of the architecture engagement

Phase B: Business Architecture

Organization / Actor Catalog
  • Definite list of all participants that interact with IT
  • Referenced while developing requirements to test for completeness
  • Entities: Organization Unit, Actor & Location
Driver/Goal/Objective Catalog
  • Provides cross organizational reference of how an organization meets its drivers through its goals, objectives and (optionally) measures.
  • Entities: Organization unit, drivers, goals, objectives, measures(optional)
Role Catalog
  • Provides listing of all authorization levels within an enterprise
  • Serves as an input into identifying organizational change management impacts, defining job functions and executing end-user training.
  • Entities: Role
Business Service / Function Catalog
  • Provides functional decomposition in a form that can be filtered, reported on and queries.
  • Provides supplement to graphical functional decomposition diagrams
  • Entities: Organization Unit, Business service, Business function, Information System service (Optional)
Location Catalog
  • Provides listing of all locations where an enterprise does business OR hosts architectural assets
  • Entities: Location
Process/Event/
Control/Product Catalog
  • Provides hierarchy of processes
  • Provides events that trigger processes
  • Provides output from processes
  • Provides controls applied to the execution of processes
  • Supplement to the Process Flow Diagrams
  • Allows enterprise to see relationships of Processes to Sub-processes in order to identify full chain of impacts resulting from changing a high level process
  • Entities: Process, Event, Control, Product
Contract/Measure Catalog
  • Provides listing of all agreed service contracts & (optionally) measures attached to those contracts
  • Forms master list of Service Levels across enterprise
  • Entities: Business Service, Information System Service, Contract, Measure
Business Interaction Matrix
  • Shows relationships between organizations and business units across the enterprise
  • Helps highlight value chain and dependencies across organizations
  • Entities: organization, Business Function, Business Service, Business Service communicates with Business Service relationships, Business Service is dependent on Business Service relationships
Actor / Role Matrix
  • Shows which actor performs which role
  • Entities: Actor, Role, Actor performs Role relationships
Business Footprint Diagram
  • Describes links between business goals, organizational units, business functions and services
  • Maps the above to technical components delivering required capability
Business Service / Information Diagram
  • Shows information needed to support a business service
  • Shows what information is product/consumed by a business service
Functional Decomposition Diagram
  • Shows capabilities of an enterprise that are relevant to the consideration of an architecture.
Product Lifecycle Diagram
  • Shows life cycle of key entities within an enterprise
Goal / Objective / Service Diagram
  • Defines the ways in which a service contributes to the achievement of a goal or objective(business vision/strategy)
Business Use-case Diagram
  • Displays relationships between consumers and providers of business services.
Organization Decomposition Diagram
  • Describes links between actor, roles and locations within an organization tree
Process Flow Diagram
  • Shows sequential flow of control between activities
Event Diagrams
  • Shows relationship between events and process.

Phase C: Information Systems Architecture – Data Architecture

Data Entity / Data Component Catalog
  • Shows a list of all the data used across the enterprise
  • Includes data entities as well as the data components where the entities are stored.
  • Entities: Data Entity, Logical Data Component, Physical Data Component
Data Entity / Business function Matrix
  • Shows relationship between data entities and the business functions which access the data entities
Application / Data Matrix
  • Shows relationship between applications and the data entities that are accessed/updated by them.
Conceptual Data Diagram
  • Shows conceptual relationship between critical entities in an enterprise
  • Addresses concerns of business stakeholders
  • Uses Entity relationship models & simplified UML class diagrams
Logical Data Diagram
  • Logical view of the relationships between critical data entities in an enterprise
  • Addresses concerns of application developers & database designers
Data Dissemination Diagram
  • Shows relationship between data entities, business service and application components.
  • Shows how logical entities are to be physically realized by application components
Data Security Diagram
  • Shows how enterprise data is kept safe and access is suitably controlled.
  • Shows which actor/role can access which data entity
  • Can be used to show legislation compliance
Data Migration Diagram
  • Shows flow of data from source to target applications
  • Concerned with data cleansing, de-duplication, standardization, normalization etc.
Data Lifecycle Diagram
  • Shows the lifecycle of data entities across an enterprise
  • Separation of data from process allows data to be treated as first class citizen and helps identify common data requirements
Phase C: Information Systems Architecture – Application Architecture
Application Portfolio Catalog
  • Identifies and maintains a list of applications in the enterprise
  • Entities: Information System Service, Logical Application Component, Physical Application Component
Interface Catalog
  • Scopes and documents interfaces between applications
  • Enable overall dependencies between applications to be scoped
  • Entities: Logical Application Component, Physical Application Component, Application communicates with Application relationship
Application / Organization Matrix
  • Shows relationship between applications and the organization units within the enterprise
  • It is a matrix showing Logical / Physical application components on one side axis and Organizational units on the other axis.
Role / Application Matrix
  • Shows relationship between the applications and the roles within the enterprise that use them.
  • 2-dimensional matrix showing applications on one axis, and role on the other axis.
Application / Function Matrix
Application Interaction Matrix
Application Communication Diagram
Application and User Location Diagram
Application Use-Case Diagram
Enterprise Manageability Diagram
Process / Application Realization Diagram
Software Engineering Diagram
Application Migration Diagram
Software Distribution Diagram

Phase D: Technology Architecture

Technology Standards catalog
  • Documents the agreed standards for technology across the enterprise covering:
    Technologies,
    Versions,
    Technology life cycles, and
    Refresh cycles for the technology.
  • Provides snapshot of the enterprise standard technologies that are deployed
    or can be deployed.
  • Helps identify the discrepancies across the enterprise.
  • Entities:
    Platform Service,
    Logical Technology Component,
    Physical Technology Component.
Technology Portfolio catalog
  • Identifies and maintains a list of all the technology in use across enterprise
  • Includes hardware, infrastructure software & application software
  • Provides foundation on which to base remaining matrices and diagrams
  • Typically the starting point of the technology architecture phase.
  • Entities referred to include:
    Platform service,
    Logical Technology Component, and
    Physical Technology Component.
Application / Technology Matrix
  • Documents mapping of applications to technology platform.
  • This matrix shows:
    Logical / Physical Application Components,
    Services, Logical and Physical Technology Components, and
    Physical Technology Components realizes Physical Application Components.
Environment and Locations Diagram
  • Depicts which location hosts which applications.
  • Identifies what technologies and/or applications are used at which locations.
  • Identifies the locations from which business users interact with the applications.
Platform Decomposition Diagram
  • Depicts the technology platform that supports the operations of the Information Systems architecture.
  • Covers all aspects of the infrastructure platform.
  • Provides an overview of the enterprise’s technology platform.
  • It can simply be an informal ‘eye-chart’ providing an overview of the technology environment.
  • May show details of the specifications such as Product versions, #CPUs.
Processing Diagram
  • Shows how deployable units of code/configuration are deployed onto the technology platform.
  • A deployable unit represents a business function, service or application components.
  • This diagram addresses
    – Which set of application components need to be grouped to form a deployable unit.
    – how one deployable unit connects to another
    – how app config & usage requirements generate load or capacity requirements for different technology components.
Networked Computing / Hardware Diagram
  •  This diagram shows ‘as deployed’ logical view of the logical application components in a distributed network computing environment.
Communications Engineering Diagram
  •  This diagram shows the means of communication – the method of sending and receiving information – between assets in the Technology Architecture.

Phase E: Opportunities and Solutions

Process Context Diagram
Benefits Diagram

Leave a Reply

Your email address will not be published. Required fields are marked *

Post Navigation