Enterprise architecture training course, based on TOGAF® Level 2 ArchiMate® Level 2
Purpose This course prepares students to apply the TOGAF architecture framework and the ArchiMate visual modeling language to business and technology transformation efforts. Enterprise and solution architects who have completed this course can take a set of business objectives and work collaboratively within an organization to design, plan and oversee a program of business and technology transformation to achieve or support those objectives. Architects can use the ArchiMate language to visualize and effect business transformation defined with the TOGAF framework.
Intended Audience This course is for practicing enterprise and solution architects who are either certified at both the TOGAF Foundation level and the ArchiMate Foundation level, or have equivalent knowledge.
Approach The course presents all of the TOGAF Level 2 topics as specified by The Open Group [1]. With each TOGAF topic, the course presents relevant ArchiMate language elements and viewpoints, and assigns exercises that requires student teams to develop, complete, or analyze applicable Archiate views. To the greatest extent possible, the course is taught using the ArchiMate views listed in the Outline section of this document. In this way, students learn the TOGAF Level 2 material using clear, standard graphics, and learn to apply visual modeling techniques per the ArchiMate Level 2 conformance requirements [2].
Outline This outline is based on the TOGAF Level 2 conformance requirements found in [1]. It summarizes that material, reorganizes parts of it, and combines it with ArchiMate material. Therefore, the structure of the course is based on TOGAF, and each half-day numbered session titled in blue boldface below begins with an overview that identifies the most relevant ArchiMate languages elements and viewpoints. For nearly all topics, this outline lists views based on standard ArchiMate viewpoints. These views illustrate standard TOGAF concepts and realize standard TOGAF artifacts. They are described with the viewpoints on which they are based, e.g. “Project view” for a view based on the ArchiMate Project Viewpoint. For further details on the course content, consult the References section at the end of this document.
Course Outline
Getting Started
- 1.1. Course Overview
- 1.1.1. Project view: Course Structure and Objectives.
- 1.1.2. Applicability of the ArchiMate language to TOGAF framework implementation
- 1.2. TOGAF Architecture Development Method (ADM) Preliminary Phase
- 1.2.1. Goal Realization view: Business Principles, Goals and Drivers
- 1.2.2. Organization view: Enterprise Architecture Team and Organization
- 1.2.3. Goal Contribution view: Architecture Principles
- 1.2.4. Architecture Governance
- 1.2.4.1.1. Business Process view: Architecture Governance Framework
- 1.2.4.1.2. Business Function view: Architecture Governance Framework Organizational Structure
- 1.2.4.2. Business Scenarios Technique
- 1.2.4.2.1. Information Structure view: Business Scenario
- 1.2.4.2.2. Project view: Business Scenario Development
Vision and Business Architecture
- 1.3. Phase A. Architecture Vision
- 1.3.1. Information Structure view: Business Transformation Readiness Assessment Summary
- 1.3.2. Introductory view: Architecture Vision
- 1.3.3. Actor Cooperation view: TOGAF Value Chain Diagram
- 1.3.4. Architecture Content Framework, including TOGAF Content Metamodel
- 1.3.4.1.1. Information Structure view: Content Metamodel Overview
- 1.3.5. Stakeholder Management
- 1.3.5.1. Motivation view: Stakeholders, their concerns, and business requirements
- 1.3.6. Architecture Implementation Support Techniques
- 1.3.6.1. Requirements Realization view: Interoperability Requirements
- 1.4. Phase B. Business Architecture
- 1.4.1. Gap Analysis
- 1.4.1.1. Product view: TOGAF Business Footprint Diagram
- 1.4.2. Business Architecture Building Blocks
- 1.4.3. Business Architecture Roadmaps
- 1.4.3.1. Implementation and Migration View: Business Roadmap
Information Systems Architecture
- 1.5. Phase C. Data Architecture
- 1.5.1. Information Structure view: Conceptual, Logical and Physical Data
- 1.5.2. Total view: TOGAF Data Dissemination Diagram
- 1.5.3. Landscape views: Baseline and Target Data Storage by Business Area
- 1.6. Phase C. Application Architecture
- 1.6.1. Application Cooperation view: TOGAF Application Communication Diagram
- 1.6.2. Application Usage view: TOGAF Process/Application Realization Diagram
- 1.6.3. Landscape views: Baseline and Target Application Usage by Service Line
Technology Architecture and Reference Models
- 1.7. Phase D. Technology Architecture
- 1.7.1. Infrastructure usage view: Infrastructure Usage by Applications
- 1.7.2. Infrastructure view: Core Infrastructure Architecture
- 1.7.3. Infrastructure view: TOGAF Environments and Locations Diagram
- 1.8. Reference Models
- 1.8.1. Layered view: TOGAF Technical Reference Model
- 1.8.2. Layered view: TOGAF Information Infrastructure Reference Model
Migration Planning
- 1.9. Phase E. Opportunities and Solutions
- 1.9.1. Implementation and Migration view: High-Level Roadmap
- 1.10. Phase F. Migration Planning
- 1.10.1. Implementation and Migration view: Detailed Roadmap
- 1.10.2. Stakeholder view: Project Prioritization Drivers and Assessments
Implementation Governance and Change Management
- 1.11. Phase G. Implementation Governance
- 1.11.1. Service Realization view: Business Service Deployment Blueprint with Highlighted Business
Process and Application Service Gaps
- 1.11.2. Implementation and Deployment view: Solution Deployment Blueprint with Highlighted
Infrastructure Gaps
- 1.12. Phase H. Architecture Change Management
- 1.12.1. Product view: Required Product Changes with Highlighted Business Process and Application
Service Gaps
- 1.12.2. Infrastructure Usage View: Application Usage and Quality of Service Monitoring
Managing Scope, Requirements, Results and Reuse
- 1.13. Architecture Partitioning
- 1.13.1. Business Function view: Architecture Partitioning by Business Function
- 1.13.2. Application Usage view: Architecture Partitioning by Application Function
- 1.14. Architecture Requirements Management
- 1.14.1. Goal Realization view: Contribution of Requirements to Goals
- 1.14.2. Requirements Realization view: Realization of Requirements through Implemented Components
- 1.15. Architecture Repository Management and Enterprise Continuum
- 1.15.1. Information Structure view: Architecture Repository Content
- 1.15.2. Information Structure view: Architecture Repository Implementation
- 1.15.3. Business Process view: Enterprise Continuum
Adapting the ADM to the Challenges at Hand
- 1.16. Iteration
- 1.16.1. Project views: Architecture Capability, Architecture Development, Transition Planning and Architecture Governance Iterations.
- 1.17. Security
- 1.17.1. Motivation view: Security Drivers and Requirements
- 1.17.2. Information Structure view: Data classification
- 1.18. Service Oriented Architecture (SOA)
- 1.18.1. Business Function view: SOA Governance
- 1.18.2. Layered view: Open Group SOA Reference Architecture
- 1.18.3. Infrastructure Usage view: Application Inter operation via an Enterprise Service Bus Developing and Assessing Architecture Capability
- 1.19. Organizational Structure and Function
- 1.19.1. Business Process view: Mature Architecture Capability
- 1.20. Skills
- 1.20.1. Organization view: Architecture Roles
- 1.20.2. Information Structure view: Skill Taxonomy
- 1.21. Maturity Models
- 1.21.1. Information Structure view: Model Taxonomy
- 1.21.2. Stakeholder view: Maturity Levels
- 1.22. Preparing for Certification Exams
- 1.23. Course Retrospective with Open Q&A
Exam Information
Cancellation Policy
A 100% refund, minus a 5% processing fee, will be given to students who drop or withdraw from the EA Principals, Inc. class no later than the 21st day prior to the announced scheduled start date. No refund will be given within 21 days of the published start date. Students missing a portion of a class, due to emergencies or unforeseen circumstances, will be able to attend the next class on the same topic for the days missed, without additional fee. Students need not reregister; however, they must notify EA Principals, Inc. (by email or telephone), so the registration fee for the makeup class can be waived and class logistics provided. Note: This refund policy does not apply if using special discount codes that have “no refund” specified in the usage instructions.