Building deliverables for phase A: Architecture vision
In phase A of the TOGAF Architecture Development Method (ADM) you establish the scope of the architecture effort, get buy in from senior management and line management, and develop the vision of the architecture effort.
The following inputs are required to build phase A:
▪Request for Architecture Work: The phase starts with a Request for Architecture Work being delivered from the sponsoring organization to the architecture organization. The architecture organization uses this to build a Statement of Architecture (see outputs below).
▪Enterprise Continuum: Existing documentation of the enterprise architecture (framework description, architectural descriptions, existing baseline descriptions, and so forth) can be documented in the Business Architecture diagram elements, and the Business Architecture definition, within which you list Architecture building block and Solution building block.
The phase starts with a Request for Architecture Work, delivered from the sponsoring organization to the architecture organization, and results in a the production of a Statement of Architecture Work.
Procedure
1 To capture information about the project, create a Project definition:
▪In the Explorer, click the All filter button.
▪Right-click Definitions, and then click New.
▪In the Select New Type for All dialog box, select Project, and then click OK.
▪Type a name for the new definition, and then click OK.
▪In the Dictionary Object - Project dialog box, type a statement that describes the project, and then click OK.
2 Identify the Business Goal and Business driver of the organization.
3 Review the existing principles of the Enterprise Architecture. Document the principles that govern the enterprise architecture, including Business principles, Data principles, Application principles, and Technology principles. Create Principle definitions to hold this information, and for each, document the Statement of the principle, the rationale used to arrive at it, and its implications.
4 Define what is inside and outside the scope of the enterprise architecture effort. Capture the Scope of an architecture project in the Statement of Architecture Work definition type. You can also specify the scope of each particular project in the Scope Detail tab of the Project definition type.
5 Within the Request for Architecture Work definition, specify the constraints that must be dealt with, including organization-wide constraints and project-specific constraints (time, schedule, resources, and so forth).
6 Identify the Stakeholders and Concerns, Business Requirements, and Architecture Vision. In this step, you can do some or all of these:
▪Identify the key stakeholders and their concerns and/or objectives. You can use a Stakeholder Relationship diagram (see Stakeholder Relationship Diagrams).
▪Define the key business to be addressed in this architecture effort (see Validating enterprise architecture against requirements). Requirements can be modeled in an external tool such as IBM Rational DOORS, and affixed to the architecture Statement of Work via the SA/DOORS link, or, if you do not have IBM Rational DOORS, you can create business requirements in System Architect via the Requirements definition type, or any other applicable definition type that you add to the tool through metamodel customization.
▪Specify an architecture vision that will address the requirements, within the defined scope and constraints, and conforming with the business and architectural principles.
▪You can textually specify the Architecture Vision in Page 2 of the Summary tab of the Statement of Architecture Work definition.
Note The Business Motivation Model (BMM), as modeled in an Enterprise Direction diagram (see BMM), provides a definition type called Vision (see Vision statements), which is used to specify the Vision of the organization from a business perspective. This is a separate concept than the Vision of the architecture.
7 The TOGAF ADM recommends modeling your business scenarios as a useful technique to discover and document your business requirements, and to help you create an architectural vision that responds to those requirements. You can model business scenarios using one of the following methods:
▪You can use the Business scenario to textually capture business process steps, actors and roles involved in each scenario, and so forth.
8 Begin to model the as is (baseline) and to be (target) architectures, according to the TOGAF ADM. You can use the following modeling options to help you get started:
▪You can use the workspace functionality (see Creating a workspace) within System Architect to model these baseline and target architectures: creating a workspace for the baseline, version 0.1, and creating a workspace for the target, version 0.1.
▪As an aide to articulating the architecture vision, you can create Solution Concept diagrams to provide a high-level view of the solution for an initiative. You can use a business concept diagram for this (see Business Concept diagram).
9 Finish the Statement of Architecture Work definition. Document the estimated resources needed, and develop a roadmap and schedule for the proposed development. You can textually specify these items or link to them in the Reference Documents tab of the in the Statement of Architecture Work definition.
Result
The following outputs are created as a result of building phase A:
▪Statement of Architecture Work
▪Project, including scope, constraints, and the plan for the architectural work
