Presentation is loading. Please wait.

Presentation is loading. Please wait.

Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.

Similar presentations


Presentation on theme: "Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the."— Presentation transcript:

1 Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the following mapping of these domains. Source

2 Scope of Preliminary Phase: Framework and Principles The outputs of this phase are: Framework Definition: ZF: Business/Function (model of the architecture development process) [Row 2,Colunm 2] Architecture principles : ZF: Scope/Data [R1,C1], Scope/Function[R1,C2], Scope/Network [R1,C3], Scope/People, Scope/Time[R1,C4], Scope/Motivation[R1,C6] Restatement of, or reference to, business principles, business goals, and business drivers: ZF: Composite of: Scope/Motivation[R1,C6], Business/Motivation [R2,C6] Source

3 Phase A: Architecture Vision The outputs of this phase are: -Approved Statement of Architecture Work, including in particular: Scope and constraints ZF: Scope/Data[R1,C1], Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5] Note: The Scope/Motivation cell [R1,C6] is presumed to be addressed by strategic business planning activities outside the scope of the Architecture Vision. -Plan for the architecture work -Refined statements of business principles, business goals, and strategic drivers: ZF: Scope/Data[R1,C1], Scope/Motivation [R1,C6] -Architecture principles (if not previously existing) : ZF: Scope/Data[R1,C1], Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5], Scope/Motivation[R1,C6] -Architecture Vision/Business Scenario, including: *Baseline Business Architecture, Version 0.1 ZF: Business/Data[R2,C2], Business/Function[R2,C2], Business/Network[R2,C3], Business/People[R2,C4], Business/Time[R2,C5], Business/Motivation[R2,C6] *Baseline Technology Architecture, Version 0.1 : ZF: System/Data[R3,C2], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5], System/Motivation[R3,C6] *Target Business Architecture, Version 0.1 : ZF: Business/Data[R2,C2], Business/Function[R2,C2], Business/Network[R2,C3], Business/People[R2,C4], Business/Time[R2,C5], Business/MotivationR2,C6 *Target Technology Architecture, Version 0.1 : ZF: System/Data[R3,C2], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5], System/Motivation[R3,C6]

4 Scope of Phase A: Architecture Vision Source

5 Phase B: Business Architecture The outputs of this phase are: -Statement of Architecture Work (updated if necessary) -Validated business principles, business goals, and strategic drivers: ZF: Scope/Data[R1,C1], Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5] Note: The Scope/Motivation cell [R1,C6] is presumed to be addressed by strategic business planning activities outside the scope of the Architecture Vision. -Target Business Architecture: *Organization structure, identifying business locations and relating them to organizational units: ZF: Scope/Network[R1,C3], Scope/People[R1,C4], Business/Network[R2,C3], Business/People[R2,C4] *Business goals and objectives, for each organizational unit: ZF: Scope/Network[R1,C3], Scope/Time[R1,C5], Business/Network[R2,C3], Business/Time[R2,C5], Business/Motivation [R2,C6] Note: The Scope/Motivation cell [R1,C6] is presumed to be addressed by strategic business planning activities outside the scope of the Business Architecture. *Business functions - a detailed, recursive step involving successive decomposition of major functional areas into sub-functions: ZF: Scope/Function[R1,C2], Business/Function [R2,C2] *Business services - the services that each enterprise unit provides to its customers, both internally and externally: ZF: Business/Function[R2,C2], System/Function [R3,C2] *Business processes, including measures and deliverables: ZF: Business/Function[R2,C2], Business/Time [R2,C5] *Business roles, including development and modification of skills requirements: ZF: Scope/People[R1,C4], Business/People [R2,C4] *Correlation of organization and functions; relate business functions to organizational units in the form of a matrix report: ZF: Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Business/Function[R2,C2], Business/Network[R2,C3], Business/People [R2,C4] -Baseline Business Architecture, Version 1.0 (detailed), if appropriate -Views corresponding to the selected viewpoints addressing key stakeholder concerns -Gap analysis results -Technical requirements (drivers for the Technology Architecture work): identifying, categorizing, and prioritizing the implications for work in the remaining architecture domains; for example, by a dependency/priority matrix (e.g., guiding trade-off between speed of transaction processing and security); list the specific models that are expected to be produced (e.g., expressed as primitives of the Zachman Framework) ZF: System/Motivation [R3,C6] -Business Architecture Report -Updated business requirements

6 Scope of Phase B: Business Architecture Source

7 Phase C: Information System Architectures: Data Architecture The outputs of this phase are: -Statement of Architecture Work (updated if necessary) -Baseline Data Architecture, Version 1.0, if appropriate -Validated principles, or new data principles (if generated here): ZF: Scope/Data[R1,C1], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5] -Target Data Architecture, Version 1.0: *Business data model: ZF: Business/Data [R2,C1] *Logical data model: ZF: System/Data [R3,C1]. *Data management process models: ZF: System/Function[R3,C2], System/People[R3,C3] *Data entity/business function matrix: ZF: Composite of Business/People[R2,C4], System/Data[R3,C1], System/Function[R3,C2] *Data interoperability requirements: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4] -Viewpoints addressing key stakeholder concerns -Views corresponding to the selected viewpoints; for example: *Data dissemination view: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4] *Data lifecycle view: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Time[R3,C5] *Data security view: ZF: Composite of System/Function[R3,C2], System/Data[R3,C1], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5] *Data model management view: ZF: Composite of Business/Data[R2,C1], System/Data[R3,C1], Business/Time[R2,C4], System/Time[R3,C5] -Gap analysis results -Relevant technical requirements that will apply to this evolution of the architecture development cycle: ZF: System/Motivation[R3,C6] -Data Architecture Report, summarizing what was done and the key findings -Impact Analysis -Updated business requirements, if appropiate

8 Scope of Phase C: Data Architecture Source

9 Phase C: Information System Architectures: Application Architecture The outputs of this phase are: -Statement of Architecture Work (updated if necessary) -Baseline Application Architecture, Version 1.0, if appropriate -Validated application principles, or new application principles (if generated here): ZF: Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5] -Target Application Architecture, Version 1.0: *Process systems model: ZF: System/Function[R3,C2] *Systems/place model: ZF: System/Network[R3,C3] *People/systems model: ZF: System/People[R3,C4] *Systems/time model: ZF: System/Time[R3,C5] *Applications interoperability requirements: ZF: Composite of System/Data[R1,C3], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5], System/Motivation[R3,C6] -Viewpoints addressing key stakeholder concerns -Views corresponding to the selected viewpoints; for example: *Common applications services view: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5] *Applications interoperability view: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/Time[R3,C5] *Applications/information view: ZF: Composite of System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/Time[R3,C5] *Applications/user locations view: ZF: Composite of System/Network[R3,C3], System/People[R3,C4] -Gap analysis results *Areas where the Business Architecture may need to change to cater for changes in the Applications Architecture : ZF: Composite of Business/Data[R2,C1], Business/Function[R2,C2], Business/Network[R2,C3], Business/People[R2,C4], Business/Time[R2,C5] *Identify any areas where the Data Architecture (if generated at this point) may need to change to cater for changes in the Applications Architecture : ZF: Composite of Business/Data[R2,C1], Business/People[R2,C4], Business/Time[R2,C5] *Identify any constraints on the Technology Architecture about to be designed : ZF: System/Motivation[R3,C6] -Applications Architecture Report, summarizing what was done and the key findings -Impact Analysis -Updated business requirements, if appropiate

10 Scope of Phase C: Application Architecture Source

11 Phase D: Technology Architecture The outputs of Phase D are given below, first by relevant individual step, and then as a composite for the whole phase. -Statement of Architecture Work (updated if necessary) Step 1: Create a Baseline Description in the TOGAF Format The outputs of this step are: -Technology Architecture principles (if not existing): ZF: Scope/Data[R1,C1], Scope/Function[R1,C2], Scope/Network[R1,C3], Scope/People[R1,C4], Scope/Time[R1,C5], Scope/Motivation[R1,C6] -Target Technology Architecture, Version 0.2: *Technology Architecture - Constraints *Technology Architecture - Architecture Principles *Technology Architecture - Requirements Traceability, key questions list *Technology Architecture - Requirements Traceability, criteria for selection of service portfolio *Technology Architecture Model, Version 0.1: ZF: Technology/Function[R4,C2], Technology/Network[R4,C3]

12 Scope of Phase D: Technology Architecture – Step 1 Source

13 Phase D: Technology Architecture Step 2: Consider Architecture Reference Models, Viewpoints, and Tools The outputs of this step are: -Target Technology Architecture, Version 0.3: *Technology Architecture - Architecture Viewpoints -Networked computing/hardware view: ZF: System/Network[R3,C3], Technology/Network[R4,C3] -Communications view: ZF: Composite of: System/Network[R3,C3], System/People[R3,C4], Technology/Network[R4,C3], Technology/People[R4,C4] -Processing view: ZF: System/Data[R3,C1], System/Function[R3,C2], System/Network[R3,C3], System/People[R3,C4], System/Time[R3,C5], Technology/Data[R4,C1], Technology/Function[R4,C2], Technology/Network[R4,C, Technology/People[R4,C4], Technology/Time[R4,C5] -Cost view: ZF: Technology/Motivation[R4,C6] -Standards view: ZF: Technology/Motivation[R4,C6] *Technology Architecture – Constraints: ZF: System/Motivation[R3,C6]

14 Scope of Phase D: Technology Architecture – Step 2 Source

15 Phase D: Technology Architecture Step 3: Create an Architectural Model of Building Blocks The outputs of this step are: -Target Technology Architecture, Version 0.4: *Technology Architecture Model -Networked computing/hardware view: ZF: Technology/Network[R4,C3], System/Network[R3,C3] -Communications view: ZF: Composite of: Technology/Network[R4,C3], Technology/People[R4,C4], System/Network[R3,C3], System/People[R3,C4] -Processing view: ZF: ZF: Technology/Network[R4,C3], Technology/Time[R4,C5], Technology/People[R4,C4], Technology/Data[R4,C1], Technology/Function[R4,C2], System/Network[R3,C3], System/Time[R3,C5], System/People[R3,C4], System/Data[R3,C2], System/Function[R3,C2] -Cost view: ZF: Technology/Motivation[R4,C6] -Standards view: ZF: Technology/Motivation[R4,C6] *Technology Architecture – change requests and/or extensions or amendments to be incorporated in an organization-specific Architecture Continuum

16 Scope of Phase D: Technology Architecture – Step 3 Source

17 Phase D: Technology Architecture Step 4: Select the Services Portfolio Required per Building Block The outputs of this step are: -Target Technology Architecture, Version 0.5: *Technology Architecture – target services (a description of the service portfolios required also known as an Organization-Specific Framework): ZF: Technology/Network[R4,C3], Technology/Time[R4,C5], Technology/People[R4,C4], Technology/Data[R4,C1], Technology/Function[4R,C2], Technology/Motivation[R4,C6] *Technology Architecture – change requests and/or extensions or amendments to be incorporated in an organization-specific Architecture Continuum

18 Scope of Phase D: Technology Architecture – Step 4 Source

19 Phase D: Technology Architecture Step 5: Conduct a Gap Analysis The outputs of this step are: -Target Technology Architecture, Version 1.0: *Technology Architecture – gap report: ZF: Composite of Technology/Data[R4,C1], Technology/ Function[R4,C2], Technology/Network[R4,C3], Technology/People[R4,C4], Technology/Time[R4,C5], Technology/Motivation[R,4C6] *Technology Architecture – change requests and/or extensions or amendments to be incorporated in an organization-specific Architecture Continuum

20 Scope of Phase D: Technology Architecture – Step 5 Source

21 Composite of Phase D: Technology Architecture Source


Download ppt "Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the."

Similar presentations


Ads by Google