|
Conformance Statement |
for Product Standard: TOGAF 8 TRAINING
Version 1.03
This form contains a series of questions that need to be answered. Use an HTML editor or simple text editor to edit the form to provide the answers. DO NOT EDIT ANY OF THE QUESTIONS. Note that the completed Conformance Statement will be made publicly accessible.
As you answer the questions, please keep in mind the following:
Enter the name, and organization of the author of this Conformance Statement.
| Name | Organization |
|---|---|
| Rob Aalders |
Aalders Analysis & Design Pty Ltd |
Enter the name of the Organization (Enterprise and Division, if applicable), and the Course Title and Version for the product for which TOGAF 8 TRAINING certification is being sought.
| Enterprise Name | Division / Organization |
|---|---|
| Aalders Analysis & Design Pty Ltd |
Aalders Analysis & Design Pty Ltd |
| Course Title and Version Number |
|---|
| TOGAF™ 8.1 Version 1.0 |
The following table contains a checklist of all the items that should be covered in the syllabus of a conformant TOGAF 8 TRAINING Course. For each entry in the Topic column, enter under the Syllabus Reference(s) column the reference to the part of the course syllabus in which the topic is addressed in the course.
There are 6 Topic Areas that must be covered in a conformant course:
TOGAF8 Architecture Development Method (ADM) - Process
TOGAF8 Architecture Development Method (ADM) - Information Sets
TOGAF Foundation Architecture
The Enterprise Continuum
TOGAF and Other Architectures / Frameworks
Architecture Governance
Preliminary Phase: Framework and Principles |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 1.P.1 Defining "How we do Architecture" |
Module 5 - The Preliminary Phase: Framework and
Principles
|
| 1.P.2 Defining the framework to be used | Module 5 - The Preliminary Phase: Framework and Principles |
| 1.P.3 Defining architecture principles | Module 5 - The Preliminary Phase: Framework and Principles |
| 1.P.4 Establishing IT Architecture Governance | Module 5 - The Preliminary Phase: Framework and Principles |
Phase A: Architecture Vision |
|
| Topic | Syllabus Reference(s) |
| 1.A.1. Project Establishment | Module
10 - Phase A: Architecture Vision |
| 1.A.2. Identifying Business Principles, Business Goals, and Business Drivers | Module 10 - Phase A: Architecture Vision |
| 1.A.3. Reviewing Architecture Principles | Module 10 - Phase A: Architecture Vision |
| 1.A.4. Defining Scope | Module 10 - Phase A: Architecture Vision |
| 1.A.5. Defining Constraints | Module 10 - Phase A: Architecture Vision |
| 1.A.6. Defining Stakeholders and concerns, Business Requirements, and Architecture Vision | Module 10 - Phase A: Architecture Vision |
| 1.A.7. Documenting Statement of Architecture Work and Gaining Approval | Module 10 - Phase A: Architecture Vision |
Phase B: Business Architceture |
|
| Topic | Syllabus Reference(s) |
| 1.B.1. Developing a Business Baseline Description. | Module 11-
Phase B: Business Architecture |
| 1.B.2. Reference Models, Viewpoints and Tools. | Module 11- Phase B: Business Architecture |
| 1.B.3. Create Buisness Architecture Model(s). | Module 11- Phase B: Business Architecture |
| 1.B.4. Select Business Architecture building blocks | Module 11- Phase B: Business Architecture |
| 1.B.5. Conduct checkpoint review of architecture model. | Module 11- Phase B: Business Architecture |
| 1.B.6. Review non-functional (qualitative) criteria. | Module 11- Phase B: Business Architecture |
| 1.B.7. Complete the business architecture. | Module 11- Phase B: Business Architecture |
| 1.B.8. Gap analysis and report | Module 11- Phase B: Business Architecture |
Phase C: Information System Architecture - Data |
|
| Topic | Syllabus Reference(s) |
| 1.CD.1. Developing a Data Baseline Description. | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.2. Principles, Reference Models, Viewpoints and Tools. | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.3. Create Data Architecture Model(s). | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.4. Select Data Architecture building blocks | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.5. Conduct checkpoint review of architecture model. | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.6. Review non-functional (qualitative) criteria. | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.7. Complete the Data Architecture. | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
| 1.CD.8. Gap analysis and report | Module 12 -
Phase C Information Systems Architectures Overview, Module 13 - Phase C Data Architecture |
Phase C: Information System Architecture - Applications |
|
| Topic | Syllabus Reference(s) |
| 1.CA.1. Developing an Applications Baseline Description. | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.2. Principles, Reference Models, Viewpoints and Tools. | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.3. Create Applications Architecture Model(s). | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.4. Select Applications Architecture building blocks | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.5. Conduct checkpoint review of architecture model. | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.6. Review non-functional (qualitative) criteria. | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.7. Complete the Applications Architecture. | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
| 1.CA.8. Gap analysis and report | Module 12 -
Phase C Information Systems Architectures Overview, Module 14 - Phase C Applications Architecture |
Phase D: Technology Architecture |
|
| Topic | Syllabus Reference(s) |
| 1.D.1. Create Technology Baseline Description | Module 17 -
Phase D Technology Architecture |
| 1.D.2. Create Target Technology Architecture | Module 17 - Phase D Technology Architecture |
| 1.D.2.1. Create a baseline description in the TOGAF format | Module 17 - Phase D Technology Architecture |
| 1.D.2.2. Consider different architectural viewpoints | Module 17 - Phase D Technology Architecture |
| 1.D.2.3. Create an architectural model of building blocks | Module 17 - Phase D Technology Architecture |
| 1.D.2.4. Select the services portfolio required per building block | Module 17 - Phase D Technology Architecture |
| 1.D.2.5. Confirm that business goals and objectives are met | Module 17 - Phase D Technology Architecture |
| 1.D.2.6. Determine criteria for specification selection | Module 17 - Phase D Technology Architecture |
| 1.D.2.7. Complete the architecture definition | Module 17 - Phase D Technology Architecture |
| 1.D.2.8. Conduct gap analysis | Module 17 - Phase D Technology Architecture |
Phase E: Opportunities and Solutions |
|
| Topic | Syllabus Reference(s) |
| 1.E.1 Identify key business drivers constraining sequence of implementation | Module 18 -
Phase E Opportunities and Solutions |
| 1.E.2 Review gap analysis | Module 18 - Phase E Opportunities and Solutions |
| 1.E.3 Brainstorm technical requirements from functional perspective | Module 18 - Phase E Opportunities and Solutions |
| 1.E.4 Brainstorm co-existence and interoperability requirements | Module 18 - Phase E Opportunities and Solutions |
| 1.E.5 Architecture assessment and gap analysis. | Module 18 - Phase E Opportunities and Solutions |
| 1.E.6 Identify major work packages or projects, classify as new development, purchase opportunity, or reuse of existing system. | Module 18 - Phase E Opportunities and Solutions |
Phase F: Migration Planning |
|
| Topic | Syllabus Reference(s) |
| 1.F.1 Prioritize projects | Module 19 -
Phase F Migration Planning |
| 1.F.2 Estimate resource requirements and availability | Module 19 - Phase F Migration Planning |
| 1.F.3 Perform cost / benefit assessment of the various migration projects | Module 19 - Phase F Migration Planning |
| 1.F.4 Perform risk assessment | Module 19 - Phase F Migration Planning |
| 1.F.5 Generate implementation roadmap (time-lined) | Module 19 - Phase F Migration Planning |
| 1.F.6 Document Migration Plan | Module 19 - Phase F Migration Planning |
Phase G: Implementation Governance |
|
|
Topic |
Syllabus Reference(s) |
| 1.G.1 Formulate project recommendations | Module 20 -
Phase G Implementation Governance |
| 1.G.2 Document Architecture Contract | Module 20 - Phase G Implementation Governance |
| 1.G.3 On-going implementation governance and architecture compliance review. | Module 20 - Phase G Implementation Governance |
Phase H: Architecture Change Management |
|
| Topic | Syllabus Reference(s) |
| 1.H.1 Ongoing monitoring of technology changes | Module 21 -
Phase H Architecture Change Management |
| 1.H.2 Ongoing monitoring of business changes | Module 21 - Phase H Architecture Change Management |
| 1.H.3 Assessment of changes and development of position to act | Module 21 - Phase H Architecture Change Management |
| 1.H.4 Meeting of Architecture Board (or other governing council) to decide on handling changes (technology and business) | Module 21 - Phase H Architecture Change Management |
Requirements Management |
|
| Topic | Syllabus Reference(s) |
| 1.R.1 Key steps in the Requirements Management process | Module 22 -
ADM Architecture Requirements Management |
2. TOGAF 8 Architecture Development Method (ADM) - Information Sets |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 2.1 Framework Definition | Module 5 - The Preliminary Phase: Framework and Principles |
| 2.2 Architecture Principles | Module 5 - The Preliminary Phase: Framework and Principles |
| 2.3 Business Principles, Goals, and Drivers | Module 5 -
The Preliminary Phase: Framework and Principles Module 10 - Phase A: Architecture Vision |
| 2.4 IT Governance Strategy | Module 5 -
The Preliminary Phase: Framework and Principles Module 10 - Phase A: Architecture Vision |
| 2.5 Request for Architecture Work | Module 10 - Phase A: Architecture Vision |
| 2.6 Statement of Architecture Work | Module 10 - Phase A: Architecture Vision |
| 2.7 Architecture Vision | Module 10 - Phase A: Architecture Vision |
| 2.8 Business Architecture | Module 11- Phase B: Business Architecture |
| 2.9 Business Architecture Report | Module 11- Phase B: Business Architecture |
| 2.10 Business Requirements | Module 11- Phase B: Business Architecture |
| 2.11 Technical Requirements | Module 11- Phase B: Business Architecture |
| 2.12 Gap analysis | Module 11-
Phase B: Business Architecture Module 13 - Phase C Data Architecture Module 14 - Phase C Applications Architecture Module 17 - Phase D Technology Architecture |
| 2.13 Data Architecture | Module 13 - Phase C Data Architecture |
| 2.14 Data Architecture Report | Module 13 - Phase C Data Architecture |
| 2.15 Applications Architecture | Module 14 - Phase C Applications Architecture |
| 2.16 Applications Architecture Report | Module 14 - Phase C Applications Architecture |
| 2.17 Technical Architecture | Module 17 - Phase D Technology Architecture |
| 2.18 Technical Architecture Report | Module 17 - Phase D Technology Architecture |
|
2.19 Architecture Viewpoints |
Module 8 -
Views and Viewpoints Module 11- Phase B: Business Architecture Module 13 - Phase C Data Architecture Module 14 - Phase C Applications Architecture Module 17 - Phase D Technology Architecture |
| 2.20 Architecture Views | Module 8 -
Views and Viewpoints Module 11- Phase B: Business Architecture Module 13 - Phase C Data Architecture Module 14 - Phase C Applications Architecture Module 17 - Phase D Technology Architecture |
| 2.21 Re-usable Architecture Building Blocks | Module 9 -
Building Blocks |
| 2.22 Re-usable Solution Building Blocks | Module 9 - Building Blocks |
| 2.23 Impact Analysis - Project list | Module 18 - Phase E Opportunities and Solutions |
| 2.24 Impact Analysis - Migration Plan | Module 19 - Phase F Migration Planning |
| 2.25 Impact Analysis - Implementation recommendations | Module 20 - Phase G Implementation Governance |
| 2.26 Architecture Contracts | Module 6 --
Architecture Governance Module 20 - Phase G Implementation Governance |
| 2.27 Product Information | Module 18 - Phase E Opportunities and Solutions |
| 2.28 Request for Architecture Change | Module 21 - Phase H Architecture Change Management |
| 2.29 New Technology Report | Module 21 - Phase H Architecture Change Management |
| 2.30 Requirements Impact Statement | Module 21 - Phase H Architecture Change Management |
3. TOGAF Foundation Architecture |
|
3.1 The Technical Reference Model (TRM) |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 3.1.1 The purpose, structure and use of the TRM | Module 15 -
Foundation Architecture |
| 3.1.2 Taxonomy of Platform Services | Module 15 - Foundation Architecture |
| 3.1.3 Taxonomy of Application Platform Service Qualities | Module 15 - Foundation Architecture |
3.2 The Standards Information Base (SIB) |
|
| Topic | Syllabus Reference(s) |
| 3.2.1 Access to the SIB | Module 16 -
The Standards Information Base |
| 3.2.2 Searching the SIB | Module 16 - The Standards Information Base |
| 3.2.3 Using the information in the SIB | Module 16 - The Standards Information Base |
4. The Enterprise Continuum |
|
4.1 The Architecture Continuum |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 4.1.1 The concept of the Architecture Continuum | Module 4 -
The Enterprise Continuum |
| 4.1.2 Moving around the Architecture Continuum | Module 4 - The Enterprise Continuum |
| 4.1.3 The Continuum as a repository of reusable Architecture Building Blocks | Module 4 - The Enterprise Continuum |
| 4.1.4 The relationship to the Solutions Continuum | Module 4 - The Enterprise Continuum |
4.2 The Solutions Continuum |
|
| Topic | Syllabus Reference(s) |
| 4.2.1 The concept of the Solutions Continuum | Module 4 - The Enterprise Continuum |
| 4.2.2 Moving around the Solutions Continuum | Module 4 - The Enterprise Continuum |
| 4.2.3 The Solutions Continuum as a repository of reusable Solution Building Blocks | Module 4 - The Enterprise Continuum |
5. TOGAF and Other Architectures / Frameworks |
|
5.1 The Positioning of TOGAF |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 5.1.1 Positioning information | Module 23 -
TOGAF and Other Architectures/Frameworks |
| 5.1.2 Explaining it to users | Module 23 - TOGAF and Other Architectures/Frameworks |
5.2 Examples |
|
| Topic | Syllabus Reference(s) |
| Examples of other Architecture Frameworks referenced in TOGAF (for example, C4ISR, Enterprise Architecture Planning, Zachman Framework, etc.). | Module 23 - TOGAF and Other Architectures/Frameworks |
6. Architecture Governance |
|
6.1 Introduction to Governance |
|
| Topic | Syllabus Reference(s) |
|---|---|
| 6.1.1 Nature of Governance | Module 6 -- Architecture Governance |
| 6.1.2 Levels of Governance | Module 6 -- Architecture Governance |
6.2 TOGAF Architecture Governance Framework |
|
| Topic | Syllabus Reference(s) |
| 6.2.1 Conceptual Structure | Module 6 --
Architecture Governance |
| 6.2.2 Organizational Structure | Module 6 -- Architecture Governance |
6.3 Architecture Governance in Practice |
|
| Topic | Syllabus Reference(s) |
| 6.3.1 Architecture Board | Module 6 -- Architecture Governance |
| 6.3.2 Architecture Compliance | Module 6 -- Architecture Governance |
| 6.3.3 Architecture Contracts | Module 6 -- Architecture Governance |
Does the Course cover the use of tools certified under the TOGAF 8 TOOL SUPPORT program?
Enter "Yes" or "No" as appropriate.
___________NO______________
If YES, identify the tool(s) covered:
Product Supplier Product Identification Version/Release Number Syllabus Reference:(s)
A conforming Course may optionally cover the ways in which tools certified under the TOGAF 8 TOOL SUPPORT program may be used for the development of IT architectures using TOGAF. (Note that tool training per se will be provided by the tool supplier.)
Product Standard: TOGAF 8 TRAINING
Copyright © 2003-2006 The Open Group. All Rights Reserved.