A summary or high level view TOGAF 9 give a quick introduction on the Crop Circle or ADM

1. TOGAF Introduction
Crop Circle Overview

2. Preliminary Phase
• Inputs
1. TOGAF
2. Other Architecture Framework(s)
3. Business principles, business goals, and
business drivers
4. Architecture Governance strategy
5. IT strategy
6. Existing Organizational Model for Enterprise
Architecture
7. Existing Architecture Framework, if any
8. Existing architecture principles, if any
9. Existing Architecture Repository, if any
• Steps
• Outputs
1. Organizational Model for Enterprise
Architecture
2. Tailored Architecture Framework, including
architecture principles
3. Initial Architecture Repository
4. Restatement of, or reference to, business
principles, business goals, and business
drivers
5. Request for Architecture Work
6. Governance Framework
1. Scope the enterprise organizations impacted
2. Confirm governance and support frameworks
3. Define and establish the enterprise architecture team and organization
4. Identify and establish architecture principles
5. Select and tailor Architecture Framework(s)
6. Implement architecture tools

3. Preliminary Phase
• The following catalogs, matrices, and
diagrams may be produced in (Preliminary).
– Catalogs:
• Principles Catalog
– Matrices:
• Stakeholder Map Matrix
– Core diagrams:
• None
– Extension diagrams:
• None

4. Phase A: Architecture Vision
• Steps
1. Establish the architecture project
2. Identify stakeholders, concerns, and business
requirements
3. Confirm and elaborate business goals, business
drivers, and constraints
4. Evaluate business capabilities
5. Assess readiness for business transformation
6. Define scope
• Outputs
1. Statement of Architecture Work
2. Refined statements of business principles, business goals,
and business drivers
3. Architecture principles
4. Capability assessment
5. Tailored Architecture Framework
6. Architecture Vision, including:
1. Refined key high-level stakeholder requirements
2. Baseline Architecture (vision)
3. Target Architecture (vision)
7. Communications Plan
8. Additional content populating the Architecture Repository
• Inputs
1. Request for Architecture Work
2. Business principles, business goals, and
business drivers
3. Organizational Model for Enterprise
Architecture
4. Tailored Architecture Framework,
including architecture principles
5. Populated Architecture Repository; that
is, existing architecture documentation
(framework description, architecture
descriptions, existing Baseline
descriptions, etc.)
• Steps
7. Confirm and elaborate architecture principles,
including business principles
8. Develop Architecture Vision
9. Define the Target Architecture value propositions
and KPIs
10. Identify the business transformation risks and
mitigation activities
11. Develop enterprise architecture plans and the
Statement of Architecture Work; secure approval

5. Phase A: Architecture Vision
• The following catalogs, matrices, and
diagrams may be produced in Phase A
(Architecture Vision).
– Catalogs:
• None
– Matrices:
• None
– Core diagrams:
• Value Chain Diagram
• Solution Concept Diagram
– Extension diagrams:
• None

6. Phase B: Business Architecture
• Steps
• Outputs
1. Statement of Architecture Work, updated
1. Select reference models, viewpoints, and tools
2. Develop Baseline Business Architecture Description
3. Develop Target Business Architecture Description
4. Perform Gap Analysis
5. Define roadmap components
6. Resolve impacts across the Architecture Landscape
7. Conduct formal stakeholder review
8. Finalize the Business Architecture
9. Create the Architecture Definition Document
if necessary Validated business principles,
business goals, and business drivers
2. Elaborated Business Architecture
principles
3. Draft Architecture Definition Document
containing content updates
4. Draft Architecture Requirements
Specification including content updates
• Inputs
1. Request for Architecture Work
2. Business principles, business goals, and business drivers
3. Capability Assessment
4. Communications Plan
5. Organizational Model for Enterprise Architecture
6. Tailored Architecture Framework
7. Approved Statement of Architecture Work
8. Architecture principles, including business principles,
when pre-existing
9. Enterprise Continuum
10. Architecture Repository
11. Architecture Vision

7. Phase B: Business Architecture
• The following catalogs, matrices, and
diagrams may be produced in Phase B
(Business Architecture).
– Catalogs:
• Organization/Actor catalog
• Driver/Goal/Objective catalog
• Role catalog
• Business Service/Function catalog
• Location catalog
• Process/Event/Control/Product catalog
• Contract/Measure catalog
– Matrices:
• Business Interaction matrix
• Actor/Role matrix
– Core diagrams:
• Business Footprint Diagram
• Business Service/ Information diagram
• Functional Decomposition diagram
• Product Lifecycle diagram
– Extension diagrams:
• No extension diagrams are defined to be created
during Phase A.
• Goal/Objective/Ser vice diagram
• Use-case diagram
• Organization Decomposition diagram
• Process Flow diagram
• Event diagram

8. Phase C: Data Architecture
• Steps
• Outputs
1. Statement of Architecture Work, updated if
1. Select reference models, viewpoints, and tools
2. Develop Baseline Data Architecture Description
3. Develop Target Data Architecture Description
4. Perform Gap Analysis
5. Define roadmap components
6. Resolve impacts across the Architecture Landscape
7. Conduct formal stakeholder review
8. Finalize the Data Architecture
9. Create Architecture Definition Document
necessary
2. Validated data principles, or new data principles
3. Draft Architecture Definition Document,
containing content updates
4. Draft Architecture Requirements Specification,
including content updates
5. Data Architecture components of an
Architecture Roadmap
• Inputs
1. Request for Architecture Work
2. Capability Assessment
3. Communications Plan
4. Organizational Model for Enterprise Architecture
5. Tailored Architecture Framework
6. Application principles
7. Data principles, if existing
8. Statement of Architecture Work
9. Architecture Vision
10. Architecture Repository
11. Draft Architecture Definition Document:
1. Baseline Architecture (detailed or vision)
2. Target Architecture (detailed or vision)
12. Draft Architecture Requirements Specification:
1. Gap Analysis results
2. Relevant technical requirements
13. Business Architecture components of an Architecture Roadmap

9. Phase C: Data Architecture
• The following catalogs, matrices, and
diagrams may be produced in Phase C
(Data Architecture).
– Catalogs:
• Data Entity/Data Component Catalog
– Matrices:
• Data Entity/Business Function Matrix
• System Data Matrix
– Core diagrams:
• Class Diagram
• Data Dissemination Diagram
– Extension diagrams:
• Data Security Diagram
• Class Hierarchy Diagram
• Data Migration Diagram
• Data Lifecycle Diagram

10. Phase C: Application Architecture
• Steps
• Outputs
1. Statement of Architecture Work, updated if
1. Select reference models, viewpoints, and tools
2. Develop Baseline Application Architecture Description
3. Develop Target Application Architecture Description
4. Perform Gap Analysis
5. Define roadmap components
6. Resolve impacts across the Architecture Landscape
7. Conduct formal stakeholder review
8. Finalize the Application Architecture
9. Create Architecture Definition Document
necessary
2. Validated application principles, or new
application principles
3. Draft Architecture Definition Document,
containing content updates.
4. Draft Architecture Requirements Specification,
including content updates
5. Application Architecture components of an
Architecture Roadmap
• Inputs
1. Request for Architecture Work
2. Capability Assessment
3. Communications Plan
4. Organizational Model for Enterprise Architecture
5. Tailored Architecture Framework
6. Application principles
7. Data principles
8. Statement of Architecture Work
9. Architecture Vision
10. Architecture Repository
11. Draft Architecture Definition Document:
1. Baseline Architecture (detailed or vision)
2. Target Architecture (detailed or vision)
12. Draft Architecture Requirements Specification:
1. Gap Analysis results
2. Relevant technical requirements
13. • Business Architecture components of an Architecture Roadmap

11. Phase C: Application Architecture
• The following catalogs, matrices,
and diagrams may be produced in
Phase C (Application
Architecture).
– Catalogs:
• Application Portfolio Catalog
• Interface Catalog
– Matrices:
• System/Organisation Matrix
• Role/System Matrix
• System / Function Matrix
• Application Interaction Matrix
– Core diagrams:
• Application Communication Diagram
• Application and User Location Diagram
• System Use-Case Diagram
– Extension diagrams:
• Enterprise Manageability Diagram
• Process / System Realisation Diagram
• Software Engineering Diagram
• Application Migration Diagram
• Software Distribution Diagram

12. Phase D: Technology Architecture
• Steps
• Outputs
1. Statement of Architecture Work, updated if
1. Select reference models, viewpoints, and tools
2. Develop Baseline Application Architecture Description
3. Develop Target Application Architecture Description
4. Perform Gap Analysis
5. Define roadmap components
6. Resolve impacts across the Architecture Landscape
7. Conduct formal stakeholder review
8. Finalize the Application Architecture
9. Create Architecture Definition Document
necessary
2. Validated technology principles or new
technology principles (if generated here)
3. Draft Architecture Definition Document,
containing content updates
4. Draft Architecture Requirements Specification ,
including content updates
5. Technology Architecture components of an
Architecture Roadmap
• Inputs
1. Request for Architecture Work
2. Capability Assessment
3. Communications Plan
4. Organizational Model for Enterprise Architecture
5. Tailored Architecture Framework
6. Technology principles
7. Statement of Architecture Work
8. Architecture Vision
9. Architecture Repository
10. Draft Architecture Definition Document:
1. Baseline Architecture (detailed)
2. Target Architecture (detailed)
11. Draft Architecture Requirements Specification:
1. Gap Analysis results
2. Relevant technical requirements
12. Business, Data, and Application Architecture components of an
Architecture Roadmap

13. Phase D: Technology Architecture
• The following catalogs, matrices,
and diagrams may be produced in
Phase D (Technology
Architecture).
– Catalogs:
• Technology Standards Catalog
• Technology Portfolio Catalog
– Matrices:
• System / Technology Matrix
– Core diagrams:
• Environments and Location Diagram
• Platform Decomposition Diagram
– Extension diagrams:
• Processing Diagram
• Networked Computing / Hardware Diagram
• Communications Engineering Diagram

14. Phase E: Opportunities and Solutions
• Inputs
1. Product information
2. Request for Architecture Work
3. Capability Assessment
4. Communications Plan
5. Planning Methodologies
6. Organizational Model for Enterprise Architecture
7. Tailored Architecture Framework
8. Statement of Architecture Work
9. Architecture Vision
10. Architecture Repository
11. Draft Architecture Definition Document
12. Draft Architecture Requirements Specification
13. Change Requests for existing programs and projects
• Steps
• Outputs
1. Statement of Architecture Work, updated if necessary
2. Architecture Vision, updated if necessary
3. Draft Architecture Definition Document, including content updates
for:
1. Identification of increments
2. Interoperability and co-existence requirements
3. Implementation and Migration Strategy
4. Inclusion of project list and project charters
4. Draft Architecture Requirements Specification, updated if necessary
5. Capability Assessment, including content updates for:
1. Enterprise Architecture Maturity Profile
2. Transformation Readiness Report
6. Transition Architectures (see Section 10.5.2), including:
1. Consolidated Gaps, Solutions, and Dependencies Assessment
2. Risk Register
3. Impact analysis – project list
4. Dependency Analysis Report
5. Implementation Factor Assessment and Deduction matrix
7. Implementation and Migration Plan (outline)
1. Determine/confirm key corporate change attributes
2. Determine business constraints for implementation
3. Review and consolidate Gap Analysis results from Phases B to D
4. Review IT requirements from a functional perspective
5. Consolidate and reconcile interoperability requirements
6. Refine and validate dependencies
7. Confirm readiness and risk for business transformation
8. Formulate high-level Implementation and Migration Strategy
9. Identify and group major work packages
10. Identify Transition Architectures
11. Create portfolio and project charters and update the architectures

15. Phase E: Opportunities and Solutions
• The following catalogs, matrices,
and diagrams may be produced in
Phase E (Opportunities and
Solutions).
– Catalogs:
• No catalogs are defined to be created during Phase E.
– Matrices:
• No matrices are defined to be created during Phase E.
– Core diagrams:
• Project Context Diagram
• Benefits Diagram
– Extension diagrams:
• No extension diagrams are defined to be created during
Phase E.

16. Phase F: Migration Planning
• Inputs
1. Request for Architecture Work
2. Capability Assessment
3. Communications Plan
4. Organizational Model for Enterprise Architecture
5. Governance Models and Frameworks
6. Tailored Architecture Framework
7. Statement of Architecture Work
8. Architecture Vision
9. Architecture Repository
10. Draft Architecture Definition Document, including:
1. Strategic Migration Plan
2. Impact analysis – project list and charters
11. Draft Architecture Requirements Specification
12. Change Requests for existing programs and projects
13. Consolidated and validated Architecture Roadmap
14. Transition Architectures
15. Implementation and Migration Plan (outline)
• Steps
• Outputs
1. Implementation and Migration Plan (detailed)
2. Finalized Architecture Definition Document
3. Finalized Architecture Requirements Specification
4. Finalized Architecture Roadmap
5. Transition Architecture
6. Re-Usable Architecture Building Blocks (ABBs)
7. Requests for Architecture Work for the architecture aspects of
implementation projects (if any)
8. Architecture Contracts for implementation projects
9. Implementation Governance Model
10. Change Requests arising from lessons learned
1. Confirm management framework interactions for the Implementation and Migration Plan
2. Assign a business value to each project
3. Estimate resource requirements, project timings, and availability/delivery vehicle
4. Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
5. Confirm Transition Architecture increments/phases and update Architecture Definition Document
6. Generate the Architecture Implementation Roadmap (time-lined) and Migration Plan
7. Establish the architecture evolution cycle and document lessons learned

17. Phase G: Implementation Governance
• Inputs
1. Request for Architecture Work
2. Capability Assessment
3. Organizational Model for Enterprise Architecture
4. Tailored Architecture Framework
5. Statement of Architecture Work
6. Architecture Vision
7. Architecture Repository
8. Architecture Definition Document
9. Architecture Requirements Specification
10. Architecture Roadmap
11. Transition Architecture
12. Implementation Governance Model
13. Architecture Contract
14. Request for Architecture Work identified in Phases E and F
15. Implementation and Migration Plan
• Steps
• Outputs
1. Implementation and Migration Plan (detailed)
2. Architecture Contract (signed) (see Section 11.5.1)
3. Compliance Assessments
4. Change Requests
5. Impact Analysis – Implementation Recommendations
6. Architecture-compliant solutions deployed, including:
1. The architecture-compliant implemented system
2. Populated Architecture Repository
3. Architecture compliance recommendations and dispensations
4. Recommendations on service delivery requirements
5. Recommendations on performance metrics
6. Service Level Agreements (SLAs)
7. Architecture Vision, updated post-implementation
8. Architecture Definition Document, updated post-implementation
9. Transition Architecture, updated post-implementation
10. Business and IT operating models for the implemented solution
1. Confirm scope and priorities for deployment with development management
2. Identify deployment resources and skills
3. Guide development of solutions deployment
4. Perform enterprise Architecture Compliance Reviews
5. Implement business and IT operations
6. Perform post-implementation review and close the implementation

18. Phase H: Architecture Change Management
• Inputs
1. Request for Architecture Work identified in Phases E and F
2. Organizational Model for Enterprise Architecture
3. Tailored Architecture Framework
4. Statement of Architecture Work
5. Architecture Vision
6. Architecture Repository
7. Architecture Definition Document
8. Architecture Requirements Specification
9. Architecture Roadmap
10. Change Requests due to technology changes
11. Change Requests due to business changes
12. Change Requests from lessons learned
13. Transition Architecture
14. Implementation Governance Model
15. Architecture Contract (signed)
16. Compliance Assessments
17. Implementation and Migration Plan
• Steps
• Outputs
1. Architecture updates
2. Changes to Architecture Framework and
principles
3. New Request for Architecture Work, to initiate
another cycle of the ADM
4. Statement of Architecture Work, updated if
necessary
5. Architecture Contract, updated if necessary
6. Compliance Assessments, updated if necessary
1. Establish value realization process
2. Deploy monitoring tools
3. Manage risks
4. Provide analysis for architecture change management
5. Develop change requirements to meet performance targets
6. Manage governance process
7. Activate the process to implement change

19. Requirements Management
• Steps
1. Baseline requirements:
1. Determine priorities arising from current phase of ADM
2. Confirm stakeholder buy-in to resultant priorities
3. Record requirements priorities and place in
requirements repository
2. Monitor baseline requirements
3. Identify changed requirements and record priorities:
1. Identify changed requirements. Ensure the
requirements are prioritized by the architect(s)
responsible for the current phases and by the relevant
stakeholders
• Outputs
1. Changed requirements in the Architecture
Requirements Specification
2. Requirements Impact Assessment, which
identifies the phases of the ADM that need to be
revisited to address any changes.
3. The final version must include the full
implications of the requirements (e.g., costs,
timescales, and business metrics).
• Inputs
1. The inputs to the Requirements
Management process are the requirements-related
outputs from each ADM phase.
2. The first high-level requirements are
produced as part of the Architecture Vision.
3. Each architecture domain then generates
detailed requirements.
4. Deliverables in later ADM phases contain
mappings to new types of requirements
(e.g., conformance requirements).
• Steps
2. Record new priorities
3. Ensure that any conflicts are identified and managed
throughout the phases
4. Generate Requirements Impact Statement for steering
the architecture team
4. Update the requirements repository with
information relating to the changes
requested, including stakeholder views
affected.

20. Viewpoints for Requirements Management
• The following catalogs,
matrices, and diagrams may
be produced in the
Requirements Management
Phase.
– Catalogs:
• Requirements Management Catalog.
– Matrices:
• No matrices are defined to be created during
Requirements Management Phase.
– Core diagrams:
• No core diagrams are defined to be created
during the Requirements Management phase.
– Extension diagrams:
• No extension diagrams are defined to be created
during the Requirements Management phase.

22. If you have one last breath use it to
say...