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

1. ADM

2. Architecture content

3. Architecture capability

3.1. Governance

3.1.1. Governance repository

3.1.1.1. Reference data

3.1.1.2. Process status

3.1.1.3. Audit information

3.2. Compliance

3.2.1. Compliance assessment

3.2.2. Dispensation process

4. Enterprise continuum

4.1. Architecture context

4.1.1. External factors

4.1.2. Business strategy

4.1.3. Exisitng operations

4.2. Architecture continuum

4.2.1. Foundation architecture

4.2.1.1. Togaf TRM

4.2.2. Common systems architecture

4.2.2.1. (Operations architecture)Business

4.2.2.1.1. Supply chain

4.2.2.1.2. Customer service

4.2.2.2. Applicatins

4.2.2.2.1. IIRM - Boundaryless information

4.2.2.3. Technology

4.2.2.3.1. Network architecture

4.2.2.3.2. Security archtiecture

4.2.3. Industry specific architecture

4.2.3.1. Busness

4.2.3.1.1. eTOM - Telecom processes

4.2.3.1.2. ACCORD - Insurance processes

4.2.3.2. IS

4.2.3.2.1. SID - Telecom data model

4.2.3.2.2. Data model for Retail-active store

4.2.3.3. Technology

4.2.4. Org specific architecture

4.3. Solution continuum

4.3.1. Foundation solutioons

4.3.1.1. Business -centric

4.3.1.1.1. Training/consulting

4.3.1.1.2. Support

4.3.1.1.3. Generic org structures

4.3.1.2. Applications-centric

4.3.1.2.1. IT service mgmt taxonomy (ITIL)

4.3.1.3. Data -centric

4.3.1.3.1. Foundation data structures- EDIFACT

4.3.1.4. Technology -centric

4.3.1.4.1. Programming languages SBB(TRM SE services)

4.3.1.4.2. OS es (TRM OS/Kernels)

4.3.2. Common systems solutions

4.3.2.1. Business centric

4.3.2.1.1. BPO services - for processes ABB

4.3.2.1.2. KPO services - for Org related ABB

4.3.2.2. Data centric

4.3.2.2.1. Information needs e.g. data warehousing

4.3.2.3. App specific

4.3.2.3.1. Packaged applications

4.3.2.3.2. Products for CRM, SCM etc.

4.3.2.3.3. BPM solutions for cross-industry

4.3.2.3.4. Portals -for integrated access to info

4.3.2.4. Technology

4.3.2.4.1. Security system product

4.3.2.4.2. IaaS services -AWS, etc.

4.3.3. Industry specific solutions

4.3.3.1. Physical db schema

4.3.3.2. BPM based solutions

4.3.4. Org specific solutions

4.3.4.1. Hosted app service provider

4.4. Partitioning

4.4.1. Architectures

4.4.1.1. Grouping of stakeholders()

4.4.1.2. Manageable complexity

4.4.1.3. Hieararchy and navigation of structures

4.4.1.4. Define processes, roles and resp to relevant group within partition

4.4.2. Solutions

4.4.2.1. Subject matter (functions)

4.4.2.2. time period

4.4.2.3. maturity/volatality

4.4.3. Prelim phase

4.4.3.1. Org structure for architecture team work

4.4.3.1.1. Governance applicable to team

4.4.3.1.2. Team members

4.4.3.1.3. Reporting boundaries

4.4.3.2. Responsibilties -partitioned architectures under remit of team

4.4.3.2.1. Subject matter areas (functions)

4.4.3.2.2. Level of detail -capability/segment

4.4.3.2.3. Time periods to be covered -2020/30

4.4.3.2.4. Stakeholders for resp. partition

4.4.3.3. Relationship between partitions

4.4.3.3.1. Overlap - for partitions based on time periods

4.4.3.3.2. Drill down - for partitions based on level of detail/depth

4.4.3.3.3. dovetail - based on subject matter

4.4.4. Integrations of partition content

4.4.4.1. cross domain view

4.4.4.1.1. across breadth of enterprsie

4.4.4.1.2. for single segment

4.4.4.2. cross segment view

4.4.4.2.1. Across all domains

4.4.4.2.2. Across individual domains

4.4.4.3. Summary of transition arch in vision

4.4.4.3.1. Across breadth of enterprise

4.4.4.3.2. across business function/geography

5. ADM Supporting

5.1. Busines scenarios

5.1.1. Describes

5.1.1.1. Problem and objectives

5.1.1.2. Business and tech env/ processes

5.1.1.3. People/computers to execute scenario

5.1.1.4. Outcome from execution

5.1.2. Process:

5.1.2.1. Areas

5.1.2.1.1. Problem

5.1.2.2. Gather

5.1.2.2.1. scenario workshops

5.1.2.3. analyze

5.1.2.3.1. Business arch work

5.1.2.4. Refine

5.1.3. REsulting in

5.1.3.1. Stakeholder needs

5.1.3.1.1. Concerns

5.1.3.1.2. Requirements

5.1.3.2. Implementing architectures

5.2. Iterations

5.2.1. comprehensive landscape

5.2.1.1. Unrelated projects across ADM bound by SOW

5.2.1.2. Iterations for architectures at diff level

5.2.1.3. Concurrent iterations for Architectures at diff levels

5.2.2. Within ADM cycles

5.2.2.1. Architecture development

5.2.2.1.1. Multiple Dev phases concurrently

5.2.2.1.2. Cycles between multiple dev phases

5.2.2.1.3. Circle back to update Dev phases

5.2.2.2. Governance iterations

5.2.2.3. Transition planning

5.2.3. Architecture capability

5.2.3.1. Iteration of prelim to address scope of work

5.2.3.2. Above caused by ARch change in Ph H

5.2.4. Architecture engagements

5.2.4.1. Identifying change

5.2.4.1.1. Support business strategy

5.2.4.1.2. portfolio mgmt of E2E landscape

5.2.4.1.3. Portfolio mgmt of projects

5.2.4.2. Defining change

5.2.4.2.1. Define foundaton change initaitives

5.2.4.2.2. Define bounded change initiatives

5.2.4.3. Implementing change

5.2.4.3.1. Architecture governance