1.1. Architecture Principles - Not detailed policies that prescribe behavior and requirements. Provides a foundation for making A and planning decisions, framing policies, procedures, standards and supporting resolutions of contradictory situations To guide decision making/ assets use within the enterprise. Recommended to use in developing A Vision

1.1.1. Qualities

1.1.1.1. Understandable

1.1.1.2. Robust

1.1.1.3. Complete

1.1.1.4. Consistent

1.1.1.5. Stable

1.1.2. Components

1.1.2.1. Name

1.1.2.2. Statement

1.1.2.3. Rationale - highlights the business benefits for adhering to the principle

2.2. A Vision document - a tool for selling the benefits of the proposed capability to stakeholders. Describes how new capability will address stakeholder concerns

2.4. Buss principles are most prominent here

2.5. Statement of Architecture Work - defines the scope and approach that will be used to complete an architecture development cycle

2.6. Business Scenarious - recommended to help identify and understand requirements. Define them and articulate the A Vision created in phase A

3. Phase B. Business Architecture. To demonstrate how stakeholder concerns are addressed in the Buss A. Provides prerequisite knowledge for undertaking work in the other a domains. Not to defining the strategic business plan.

3.1. Select reference models,viewpoints,and tools

3.2. Develop Baseline Business Architecture Description

3.2.1. If no 1/few architecture assets exists - use Bottom Up approach

6. Phase E. Opportunities and solutions - Directly concerned with the planning for the implementation of the target a. Purpose - to define initial implementation plan

6.2. Architecture Contract - establishes connection between A organization and implementation organization. Agreement between dev partners and sponsors on the A deliverables

6.3. A Roadmap - to show change from baseline to target a

6.4. BB become impl specific

7. Phase F. Migration Planning - used to finalize a set of transition architecture that will support implementation

7.1. Implementation and Migration Plan coordinates with other framework

8. Pahse G. Implementation Governance - focuses on the governance and management of A contracts that cover the overall implementation and deployment process. Ensures that impl project conform to the defined A. Establishes connection between A org and impl org. Provides a oversight of the implementation