Master Solution Architecture

MSA Section Mandatory Section? View Architecture Phase Security related? Mandatory View? Risk Owner Effort large Effort medium Effort small
1. Architecture Vision
1.1 Problem Description
1.1.1 Stakeholders and their Concerns No Stakeholder Catalogue Conceptual No Project Manager 3 2 1
1.2.1 Business Vision Statement No Driver/Goal/Objective Catalog Conceptual No Project Manager 3 2 1
1.3.1 Architecture Scope Yes Architecture Scope analysis/capture Conceptual No Yes Project Manager 3 2 1
1.5.1 Risks Yes Architecture
2.1 Mapping to Architecture Repository Architecture Repository analysis/capture Conceptual No No 2 2 1
2.1.1 Artifacts No Business Glossary Catalog Conceptual No No Project Manager 3 2 1
2.2.1 Business Architecture Models No Architecture
2.3.1 Business Architecture Models Yes Product Lifecycle Diagram Logical No Project Manager 1 1 1
2.3.1 Business Architecture Models Yes Business Event Diagram Logical No Project Manager 3 2 1
2.3.1 Business Architecture Models Yes Business Interaction Matrix Logical No Project Manager 3 2 1
2.3.1 Business Architecture Models Yes Organization/Actor Catalog Physical No Project Manager 1 1 1
2.3.1 Business Architecture Models Yes Process/Event/Control/Product Catalog Physical No Project Manager 3 2 1
2.3.1 Business Architecture Models Yes Process Flow Diagram Logical Yes No Project Manager 7 5 3
2.3.1 Business Architecture Models Yes Actor/Role Matrix Logical Yes Yes Project Manager 3 2 1
2.3.1 Business Architecture Models Yes Contract/Measure Catalog Logical Yes Yes Project Manager 3 2 1
3.1 Conceptual Requirements Summary No (Conceptual) Architecture Requirements analysis/capture Conceptual No Yes 5 3 1
1.1.2 Problem Analysis No Business Model Diagram Conceptual No Project Manager 3 2 1
1.1.2 Problem Analysis No Strategy/Capability Matrix Conceptual No Project Manager 3 2 1
1.1.2 Problem Analysis No Business Capability Map Conceptual No No Project Manager 3 2 1
1.1.2 Problem Analysis No Capability/Organization Matrix Conceptual No No Project Manager 1 1 1
1.2 Business Vision
1.2.2 Business Vision Diagram No Value Stream Map Conceptual No Project Manager 3 2 1
1.2.2 Business Vision Diagram No Goal/Objective/Business Service Diagram Conceptual No No Project Manager 7 5 2
1.3.2 Solution Concept Diagram Yes Business Footprint Diagram Conceptual No Architecture 3 2 1
1.3.2 Solution Concept Diagram Yes Solution Concept Diagram Conceptual No Yes Architecture 3 2 1
1.5.2 Issues Yes Architecture
2. Architecture Definition
2.1.2 Mapping to Architecture Landscape Yes Architecture
2.2 Baseline Architecture Baseline Architecture views analysis/capture Conceptual No No 7 5 3
2.2.2 Data Architecture Models No Architecture
2.3.2 Data Architecture Models Yes Data Entity/Data Component Catalog Logical Yes Architecture 3 2 1
2.3.2 Data Architecture Models Yes Logical Data Diagram Logical Yes Architecture 3 2 1
2.3.2 Data Architecture Models Yes Application/Data Matrix Logical Yes Yes Architecture 3 2 1
2.3.2 Data Architecture Models Yes Data Dissemination Diagram Physical Yes Yes Architecture 3 2 1
2.3.2 Data Architecture Models Yes Data Lifecycle Diagram Logical Yes No Architecture 5 3 1
2.3.2 Data Architecture Models Yes Data Migration Diagram Physical No No Architecture 3 2 1
2.3.2 Data Architecture Models Yes Data Security Diagram Logical No Yes Architecture 3 2 12
3.2 Logical Requirements Summary Yes (Logical) Architecture Requirements analysis/capture Logical No Yes 13 7 3
1.2.3 Change Drivers and Opportunities No Change drivers and opportunities analysis/capture Conceptual No No Architecture 3 2 1
1.3 Resulting Architecture Model
1.3.3 Architecture Principles No Principles Catalog Conceptual Yes No Architecture 3 2 1
1.5.3 Assumptions No Architecture
2.1.3 Mapping to Reference Models Yes Architecture
2.2.3 Application Architecture Models No Architecture
2.3 Target Architecture
2.3.3 Application Architecture Models Yes Enterprise Manageability Diagram Logical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Role/Application Matrix Logical Yes Architecture 3 2 1
2.3.3 Application Architecture Models Yes Software Engineering Diagram Logical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application Migration Diagram Physical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application/Function Matrix Logical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Interface Catalog Physical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application Use-Case Diagram Logical No Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application/Organization Matrix Physical Yes Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application Communication Diagram Logical Yes Yes Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application Interaction Matrix Logical Yes Yes Architecture 3 2 1
2.3.3 Application Architecture Models Yes Software Distribution Diagram Physical Yes Yes Architecture 3 2 1
2.3.3 Application Architecture Models Yes Application and User Location Diagram Physical Yes Yes Architecture 5 3 1
2.3.3 Application Architecture Models Yes Process-Application Realisation Logical No No Architecture 3 2 1
3. Architecture Requirements Specification Yes Project Manager
3.3 Physical Requirements Summary Yes (Physical) Architecture Requirements analysis/capture Physical No Yes 7 5 3
1.2.4 Detailed Objectives (Desired Outcomes) No Detailed Objectives analysis/capture Conceptual No No Project Manager 3 2 1
1.3.4 Constraints Yes Technology Portfolio Catalog Conceptual Yes Architecture 1 1 1
1.3.4 Constraints Yes Non-Functional Requirements Conceptual Yes Yes Architecture 3 2 1
1.3.4 Constraints Yes Application Portfolio Catalog Conceptual No Yes Architecture 1 1 1
1.4 Architecture Decisions Yes Scope phase architecture decisions analysis/capture Conceptual No No Architecture 1 1 1
1.5.4 Dependencies No Project Manager
2.1.4 Mapping to Standards Yes Architecture
2.2.4 Technology Architecture Models No Architecture
2.3.4 Technology Architecture Models Yes Networked Computing/Hardware Diagram Physical No Architecture 3 2 1
2.3.4 Technology Architecture Models Yes Application/Technology Matrix Physical Yes Architecture 3 2 1
2.3.4 Technology Architecture Models Yes Environments and Locations Diagram Physical Yes Architecture 3 2 1
2.3.4 Technology Architecture Models Yes Platform Decomposition Diagram Physical Yes Architecture 3 2 1
2.3.4 Technology Architecture Models Yes Processing Diagram Physical No Architecture 3 2 1
2.3.4 Technology Architecture Models Yes Network and Communications Diagram Physical Yes Yes Architecture 3 2 1
2.4 Gap Analysis No Solution Options Report Logical No Project Manager 10 10 10
1.3.5 Policies and Standards Yes Technology Standards Catalog Conceptual Yes Yes Architecture 1 1 1
1.5 Risks, Issues, Assumptions and Dependencies Yes Scope phase risk/issues/dependencies/assumptions analysis/capture Conceptual No Yes Architecture 3 2 1
2.1.5 Re-Use Assessment Yes Architecture
2.5 Impact Assessment No Project Manager
1.3.6 Architecture Summary Yes Business Use-Case Diagram Conceptual No Architecture 3 2 1
1.3.6 Architecture Summary Yes Organization Decomposition Diagram Conceptual No Architecture 3 2 1
1.3.6 Architecture Summary Yes Data Entity/Business Function Matrix Conceptual Yes No Architecture 3 2 1
1.3.6 Architecture Summary Yes Business Service/Function Catalog Conceptual Yes Yes Architecture 3 2 1
1.3.6 Architecture Summary Yes Business Service/Information Diagram Conceptual Yes Yes Architecture 3 2 1
1.3.6 Architecture Summary Yes Conceptual Data Diagram Conceptual Yes Yes Architecture 1 1 0
1.3.6 Architecture Summary Yes Role Catalog Conceptual Yes Yes Architecture 3 2 1
1.3.6 Architecture Summary Yes Functional Decomposition Diagram Conceptual No Yes Architecture 3 2 1
1.3.6 Architecture Summary Yes Location Catalogue Conceptual Yes Yes Architecture 1 1 1
1.3.7 Requirements Mapped to Target Architecture No Requirements Target Architecture mapping analysis/capture Conceptual Yes No Project Manager 3 2 1