TOGAF Fases

TOGAF Fases
Phase A. Architecture Vision high level description of the baseline and target A, high level view on target A.
Goals:
To secure formal approval to proceed.
To articulate architecture vision.
Initiated by Request for A Work
A Vision document a tool for selling the benefits of the
proposed capability to stakeholders. Describes how new
capability will address stakeholder concerns
Here first validated business principles, b
goals and strategic drivers
Buss principles are most prominent here
Statement of Architecture Work defines the scope and
approach that will be used to
complete an architecture development cycle
Business Scenarious recommended to help
identify and understand requirements. Define
them and articulate the A Vision created in phase
A
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.
Select reference models,viewpoints,and tools
Develop Baseline Business
Architecture Description
If no 1/few architecture assets exists
use Bottom Up approach
Develop Target Business Architecture
Description
Perform gap analysis
Define candidate roadmap components
Resolve impacts across the Architecture
Landscape
Conduct formal stakeholder review
Finalizethe Business Architecture
Create Architecture Definition Document
Phase C. Information System Architecture. Most relevant model to use III Ref Model. Not Objective: definig data entities that are normalized to minimize update anomalies
Develop the Target Application Architecture that
enables the Business Architecture and the
Architecture Vision
Identify candidate Architecture Roadmap
Develop Data A and Application
A in either sequence
Requirements Management Responsible for managing the flow of requirements. It's Ongoing activity, that visited throughout project. Store r and manages their flow into relevant ADM phases
Phase H. Architecture Change Management
Not includes: Business Scenarios. Ensures
that A achieves its target
Simplification change. Example multiple
systems consolidated into 1. To reduce
investments
Incremental change is driven by requirement to
derive aditionsl value from the existing
investment
Rearchitecting change to increase investment in
order to create new value to exploitation
21