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

1. Deliverable

1.1. Prelim

1.1.1. Princicples

1.1.2. Goals and drivers

1.2. Vision

1.2.1. Vision

1.2.1.1. Problem descriptioon

1.2.1.2. Objective of SOW

1.2.1.3. Summary views for baseline and target architectures- Solution concept

1.2.2. Capability assessment

1.2.2.1. Business capability -baeline and target

1.2.2.2. IT function

1.2.2.3. Arch function

1.2.3. tailored EA framework

1.2.3.1. Tailored EA method

1.2.3.2. Tailored content

1.2.3.3. Tool

1.2.3.4. Interface/integration with other mgmt. framewworks

1.3. Arch dev

1.3.1. Arch definition

1.3.1.1. Baseline and target architectures- 4 domains

1.3.1.2. Gap analysis

1.3.1.3. Rationale and justification

1.3.1.4. Transitin architectures- 4 domains

1.3.2. Architecture requriementts

1.3.2.1. Rquiemetns and success criteria

1.3.2.1.1. Functional

1.3.2.1.2. Interoperability

1.3.2.1.3. IT service

1.3.2.2. Business and app service contracts

1.3.2.3. Implementation guidelines/specs/stds

1.3.3. REquirmnts impact assessment

1.3.3.1. REf to specific arch req

1.3.3.2. Priority of reqa

1.3.3.3. ADM phase to be revisited

1.4. Migration

1.4.1. Roadmap

1.4.1.1. Work package portfolio

1.4.1.2. Implementation factor/deduction matrix

1.4.1.3. Consolidated gaps,solution and dependency matrix

1.4.1.4. Transition architectures

1.4.2. Implementation/migration plan

1.4.2.1. Migrtion strategy

1.4.2.2. Project /portfolio breakdown

1.4.2.3. Project charters

1.5. Governance

1.5.1. (Arch) Change request

1.5.2. Comms plan

1.5.3. Complaince assessment

1.5.4. Implementatin governance model

1.5.4.1. Processes

1.5.4.2. Org structure

1.5.4.3. Roles and resp

1.5.4.4. Checkpoints and success crteria

1.5.5. EA Org model

1.5.5.1. Scope in terms of partitions

1.5.5.2. Maturity and gaps

1.5.5.3. Roles and resp

1.5.5.4. Constraints for EA work

1.5.5.5. Budget and financials

1.5.5.6. Governance and support

1.6. Contractual

1.6.1. Rquest for EA work

1.6.2. Contracts

1.6.3. State of EA work

2. Artefacts/views

2.1. Prelim/Vision

2.1.1. Principles catalog

2.1.2. Stakeholder map

2.1.3. VCD

2.2. Business

2.2.1. Motivation

2.2.1.1. Driver goal objective catalog

2.2.1.2. Contracts/measures catalog

2.2.1.3. Goal-objective-service

2.2.2. People

2.2.2.1. Org/actor catalog

2.2.2.2. Actor-org diagram/matrix

2.2.2.3. role catalog

2.2.2.4. Role allocation

2.2.2.5. Location catalog

2.2.2.6. Location organization

2.2.3. Function

2.2.3.1. Business service/functoin catalog

2.2.3.2. Functional decomposition

2.2.3.3. Business footprint diagram

2.2.3.4. Business interaction matrix

2.2.4. Process

2.2.4.1. Process/event/control/product catalog

2.2.4.2. Process flow

2.2.4.3. Business use case diagram

2.2.4.4. Service-information diagram

2.2.5. Information

2.2.5.1. Data dictoinary

2.2.5.2. Cocneptual data diagram

2.2.5.3. Product lifecycle diagram

2.3. IS

2.3.1. App

2.3.1.1. CAtalogs

2.3.1.1.1. App portfolio catalog

2.3.1.1.2. Interface catalog

2.3.1.2. Matrices/ traceability

2.3.1.2.1. App -user-location diagram

2.3.1.2.2. App-organiztion matrix

2.3.1.2.3. Process-system realization

2.3.1.3. Core diagrams

2.3.1.3.1. App communication diagrams

2.3.1.3.2. App use case

2.3.1.4. Extensions

2.3.1.4.1. App migration diagram

2.3.1.4.2. Enterprise manageability diagram

2.3.2. Data

2.3.2.1. Data entity (conceptual)/data component (logical) catalog

2.3.2.2. Data Modeling

2.3.2.2.1. Logical data diagram

2.3.2.2.2. Service data diagram

2.3.2.3. Matrices/ traceability

2.3.2.3.1. Data dissemination diagram

2.3.2.3.2. Data entity- function matrix

2.3.2.3.3. App- data matrix

2.3.2.4. Extensions

2.3.2.4.1. Data security diagram

2.3.2.4.2. Data migration diagram/matrix

2.4. Technology

2.4.1. Catalogs

2.4.1.1. Tech standards

2.4.1.2. Tech portfolio

2.4.2. Matrices

2.4.2.1. App - Tech

2.4.3. Diagrams

2.4.3.1. Env and location diagram

2.4.3.2. Network computing hardware diagram

2.4.3.3. Platform decomposition diagrma

2.4.3.4. Processing diagram

2.4.3.4.1. Installtion

2.4.3.4.2. Executon

2.4.3.4.3. Persistence data

2.4.3.5. Communication engiineeing diagram

2.5. Opp/solutions/migrations/Requireents

2.5.1. Project context diagram

2.5.2. Benefits diagram

2.5.3. Requiremets catalog

3. Repository

3.1. Meta model

3.2. Ref library

3.2.1. Ref architectures

3.2.2. Ref models

3.2.3. Templates

3.2.4. Viewpoint library

3.3. Arch landscape

3.3.1. strategic archtitecture

3.3.2. Segment arrcitecture

3.3.3. capability architecture

3.4. Arch capability

3.5. Governance log

3.5.1. Decision log

3.5.1.1. Justification for arch features of projects

3.5.1.2. Product selections

3.5.1.3. Changes to standards

3.5.1.4. Deviations from standards

3.5.1.5. Change request approvals

3.5.1.6. Re-use assessments

3.5.2. Compliance assessment

3.5.2.1. Project overview and progress

3.5.2.2. Arch checklists

3.5.2.3. Complance to standards

3.5.2.4. Corrective/recommended actions

3.5.3. Capability assessments

3.5.4. Calendar

3.5.5. Project portfolio

3.5.5.1. Arch scope of prject

3.5.5.2. ARch roles and resp. associated with project

3.5.6. Perofmrance measuremetn

3.6. Standards information base

3.6.1. Types

3.6.1.1. Regulatory

3.6.1.2. Industry specific

3.6.1.3. Org specific

3.6.2. Categories

3.6.2.1. Busienss

3.6.2.2. App

3.6.2.3. Data

3.6.2.4. Technology

3.7. Other enterpris repositry

3.7.1. Requeirements repository

3.7.2. Solutions repostory