Mind Map Gallery TOGAF Fases
This is a mind map about "TOGAF Fases".
Edited at 2020-12-23 10:07:56TOGAF 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 theproposed capability to stakeholders. Describes how newcapability will address stakeholder concerns
Here first validated business principles, bgoals 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 helpidentify and understand requirements. Definethem and articulate the A Vision created in phaseA
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 BusinessArchitecture Description
If no 1/few architecture assets exists use Bottom Up approach
Develop Target Business ArchitectureDescription
Perform gap analysis
Define candidate roadmap components
Resolve impacts across the ArchitectureLandscape
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 thatenables the Business Architecture and theArchitecture Vision
Identify candidate Architecture Roadmap
Develop Data A and ApplicationA 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. Ensuresthat A achieves its target
Simplification change. Example multiplesystems consolidated into 1. To reduceinvestments
Incremental change is driven by requirement toderive aditionsl value from the existinginvestment
Rearchitecting change to increase investment inorder to create new value to exploitation