Get Started. It's Free
or sign up with your email address
Togaf ACM by Mind Map: Togaf ACM

1. Repository

1.1. Content Meta model

1.2. Ref library

1.2.1. Ref architectures

1.2.2. Ref models

1.2.3. Templates

1.2.4. Viewpoint library

1.3. Arch landscape

1.3.1. strategic archtitecture

1.3.2. Segment arrcitecture

1.3.3. capability architecture

1.4. Arch capability

1.5. Governance log

1.5.1. Decision log Justification for arch features of projects Product selections Changes to standards Deviations from standards Change request approvals Re-use assessments

1.5.2. Compliance assessment Project overview and progress Arch checklists Complance to standards Corrective/recommended actions

1.5.3. Capability assessments

1.5.4. Calendar

1.5.5. Project portfolio Arch scope of prject ARch roles and resp. associated with project

1.5.6. Perofmrance measuremetn

1.6. Standards information base

1.6.1. Types Regulatory Industry specific Org specific

1.6.2. Categories Busienss App Data Technology

1.7. Other enterpris repositry

1.7.1. Requeirements repository

1.7.2. Solutions repostory

2. content framework provides a structural model for architectural content that allows the major work products that an architect creates to be consistently defined, structured, and presented

3. output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape

4. architectural work product that describes an aspect of the architecture Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things)

5. Building block

5.1. Architecture building blocks (ABB)

5.2. Solution building blocks (SBB)

6. (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions

7. Artefacts and views (by ADM phase)

7.1. Prelim/Vision

7.1.1. Principles catalog

7.1.2. Stakeholder map

7.1.3. Value Chain diagram

7.2. Business

7.2.1. Motivation Driver goal objective catalog Contracts/measures catalog Goal-objective-service

7.2.2. People Org/actor catalog Actor-org diagram/matrix role catalog Role allocation Location catalog Location organization

7.2.3. Function Business service/functoin catalog Functional decomposition Business footprint diagram Business interaction matrix

7.2.4. Process Process/event/control/product catalog Process flow Business use case diagram Service-information diagram

7.2.5. Information Data dictoinary Cocneptual data diagram Product lifecycle diagram

7.3. IS

7.3.1. App CAtalogs App portfolio catalog Interface catalog Matrices/ traceability App -user-location diagram App-organiztion matrix Process-system realization Core diagrams App communication diagrams App use case Extensions App migration diagram Enterprise manageability diagram

7.3.2. Data Data entity (conceptual)/data component (logical) catalog Data Modeling Logical data diagram Service data diagram Matrices/ traceability Data dissemination diagram Data entity- function matrix App- data matrix Extensions Data security diagram Data migration diagram/matrix

7.4. Technology

7.4.1. Catalogs Tech standards Tech portfolio

7.4.2. Matrices App - Tech

7.4.3. Diagrams Env and location diagram Network computing hardware diagram Platform decomposition diagrma Processing diagram Installtion Executon Persistence data Communication engiineeing diagram

7.5. Opp/solutions/migrations/Requireents

7.5.1. Project context diagram

7.5.2. Benefits diagram

7.5.3. Requiremets catalog

8. Deliverable

8.1. Prelim

8.1.1. Princicples

8.1.2. Goals and drivers

8.2. Vision

8.2.1. Vision Problem descriptioon Objective of SOW Summary views for baseline and target architectures- Solution concept

8.2.2. Capability assessment Business capability -baeline and target IT function Arch function

8.2.3. tailored EA framework Tailored EA method Tailored content Tool Interface/integration with other mgmt. framewworks

8.3. Arch dev

8.3.1. Arch definition Baseline and target architectures- 4 domains Gap analysis Rationale and justification Transitin architectures- 4 domains

8.3.2. Architecture requriementts Rquiemetns and success criteria Functional Interoperability IT service Business and app service contracts Implementation guidelines/specs/stds

8.3.3. REquirmnts impact assessment REf to specific arch req Priority of reqa ADM phase to be revisited

8.4. Migration

8.4.1. Roadmap Work package portfolio Implementation factor/deduction matrix Consolidated gaps,solution and dependency matrix Transition architectures

8.4.2. Implementation/migration plan Migrtion strategy Project /portfolio breakdown Project charters

8.5. Governance

8.5.1. (Arch) Change request

8.5.2. Comms plan

8.5.3. Complaince assessment

8.5.4. Implementatin governance model Processes Org structure Roles and resp Checkpoints and success crteria

8.5.5. EA Org model Scope in terms of partitions Maturity and gaps Roles and resp Constraints for EA work Budget and financials Governance and support

8.6. Contractual

8.6.1. Rquest for EA work

8.6.2. Contracts

8.6.3. State of EA work

9. content framework provides an underlying structure for the ADM that defines inputs and outputs in more detail and puts each deliverable into the context of the holistic architecture view of the enterprise