ADM Deliverables Flashcards
The Role of Architecture Deliverables
The TOGAF standard identifies deliverables that are produced as outputs from executing the ADM cycle and potentially consumed as inputs at other points in the ADM.
Key Deliverables
- Architecture Building Blocks (ABBs)
- Architecture Contract
- Architecture Definition Document
- Architecture Principles
- Architecture Repository
- Architecture Requirements Specification
- Architecture Roadmap
- Architecture Vision
- Business Principles, Business Goals, and Business Drivers
- Capability Assessment
- Change Request
- Communications Plan
- Compliance Assessment
- Implementation and Migration Plan
- Implementation Governance Model
- Organizational Model for Enterprise Architecture
- Request for Architecture Work
- Requirements Impact Assessment
- Solution Building Blocks
- Statement of Architecture Work
- Tailored Architecture Framework
Architecture Contracts
- Joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.
- Produced in Phase G: Implementation Governance.
- Successful implementation of these agreements will be delivered through effective Architecture Governance.
Architecture Definition Document
- The deliverable container for the core architectural artifacts created during a project and for important related information.
- Spans all architecture domains (Business, Data, Application, and Technology) and also examines all relevant states of the architecture (baseline, transition, and target).
Architecture Definition Document
- Created in Phase A, where it is populated with artifacts created to support the Architecture Vision.
- Updated in Phase B, with Business Architecture-related material, and subsequently updated with Information Systems Architecture material in Phase C, and then with Technology Architecture material in Phase D. Where the scope of change to implement the Target Architecture requires an incremental approach, the Architecture Definition Document will be updated to include one or more Transition Architectures in Phase E.
Transition Architecture
Shows the enterprise at an architecturally significant state between the Baseline and Target Architectures.
Architecture Definition Document
Provides a qualitative view of the solution and aims to communicate the intent of the architects.
Architecture Requirements Specification
Provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture.
Architecture Principles
- Initial output of the Preliminary Phase
- General rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.
Architecture Repository
Acts as a holding area for all architecture-related projects within the enterprise.
Architecture Requirements Specification
Provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture.
Architecture Roadmap
- Lists individual work packages that will realize the Target Architecture and lays them out on a timeline to show progression from the Baseline Architecture to the Target Architecture.
- The Architecture Roadmap is incrementally developed throughout Phases E and F, and informed by the roadmap components developed in Phases B, C, and D.
Architecture Vision
Provides a high-level summary of the changes to the enterprise that will follow from successful deployment of the Target Architecture.
Created in Phase A.
Business Principles, Business Goals, and Business Drivers
Provide context for architecture work, by describing the needs and ways of working employed by the enterprise.
Capability Assessment
Provides understanding of the baseline and target capability level of the enterprise. This assessment is first carried out in Phase A and updated in Phase E.