|
Conformance Statement |
for Product Standard: TOGAF 8 TRAINING
Version 1.0
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, organization, and email address of the author of this Conformance Statement.
| Name | Organization |
|---|---|
| Judith Jones | Architecting-the-Enterprise Limited |
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 |
|---|---|
| Architecting-the-Enterprise Limited |
| Course Title and Version Number |
|---|
| TOGAF 8 Certification for Practitioners (Version 1.xx) |
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 025 |
| 1.P.2 Defining the framework to be used | Module 025 |
| 1.P.3 Defining architecture principles | Module 025 |
| 1.P.4 Establishing IT Architecture Governance | Module 025 |
Phase A: Architecture Vision | |
| Topic | Syllabus Reference(s) |
| 1.A.1. Project Establishment | Module 026 |
| 1.A.2. Identifying Business Principles, Business Goals, and Business Drivers | Module 026 |
| 1.A.3. Reviewing Architecture Principles | Module 026 |
| 1.A.4. Defining Scope | Module 026 |
| 1.A.5. Defining Constraints | Module 026 |
| 1.A.6. Defining Stakeholders and concerns, Business Requirements, and Architecture Vision | Module 026 |
| 1.A.7. Documenting Statement of Architecture Work and Gaining Approval | Module 026 |
Phase B: Business Architecture | |
| Topic | Syllabus Reference(s) |
| 1.B.1. Developing a Business Baseline Description. | Module 027 |
| 1.B.2. Reference Models, Viewpoints and Tools. | Module 027 |
| 1.B.3. Create Buisness Architecture Model(s). | Module 027 |
| 1.B.4. Select Business Architecture building blocks | Module 027 |
| 1.B.5. Conduct checkpoint review of architecture model. | Module 027 |
| 1.B.6. Review non-functional (qualitative) criteria. | Module 027 |
| 1.B.7. Complete the business architecture. | Module 027 |
| 1.B.8. Gap analysis and report | Module 027 |
Phase C: Information System Architecture - Data | |
| Topic | Syllabus Reference(s) |
| 1.CD.1. Developing a Data Baseline Description. | Module 030 |
| 1.CD.2. Principles, Reference Models, Viewpoints and Tools. | Module 030 |
| 1.CD.3. Create Data Architecture Model(s). | Module 030 |
| 1.CD.4. Select Data Architecture building blocks | Module 030 |
| 1.CD.5. Conduct checkpoint review of architecture model. | Module 030 |
| 1.CD.6. Review non-functional (qualitative) criteria. | Module 030 |
| 1.CD.7. Complete the Data Architecture. | Module 030 |
| 1.CD.8. Gap analysis and report | Module 030 |
Phase C: Information System Architecture - Applications | |
| Topic | Syllabus Reference(s) |
| 1.CA.1. Developing an Applications Baseline Description. | Module 029 |
| 1.CA.2. Principles, Reference Models, Viewpoints and Tools. | Module 029 |
| 1.CA.3. Create Applications Architecture Model(s). | Module 029 |
| 1.CA.4. Select Applications Architecture building blocks | Module 029 |
| 1.CA.5. Conduct checkpoint review of architecture model. | Module 029 |
| 1.CA.6. Review non-functional (qualitative) criteria. | Module 029 |
| 1.CA.7. Complete the Applications Architecture. | Module 029 |
| 1.CA.8. Gap analysis and report | Module 029 |
Phase D: Technology Architecture | |
| Topic | Syllabus Reference(s) |
| 1.D.1. Create Technology Baseline Description | Module 031 |
| 1.D.2. Create Target Technology Architecture | Module 031 |
| 1.D.2.1. Create a baseline description in the TOGAF format | Module 032 |
| 1.D.2.2. Consider different architectural viewpoints | Module 032 |
| 1.C.2.3. Create an architectural model of building blocks | Module 032 |
| 1.C.2.4. Select the services portfolio required per building block | Module 032 |
| 1.C.2.5. Confirm that business goals and objectives are met | Module 033 |
| 1.C.2.6. Determine criteria for specification selection | Module 033 |
| 1.C.2.7. Complete the architecture definition | Module 033 |
| 1.C.2.8. Conduct gap analysis | Module 033 |
Phase E: Opportunities and Solutions | |
| Topic | Syllabus Reference(s) |
| 1.E.1 Identify key business drivers constraining sequence of implementation | Module 034 |
| 1.E.2 Review gap analysis | Module 034 |
| 1.E.3 Brainstorm technical requirements from functional perspective | Module 034 |
| 1.D.4 Brainstorm co-existence and interoperability requirements | Module 034 |
| 1.D.5 Architecture assessment and gap analysis. | Module 034 |
| 1.D.6 Identify major work packages or projects, classify as new development, purchase opportunity, or reuse of existing system. | Module 034 |
Phase F: Migration Planning | |
| Topic | Syllabus Reference(s) |
| 1.F.1 Prioritize projects | Module 035 |
| 1.F.2 Estimate resource requirements and availability | Module 035 |
| 1.F.3 Perform cost / benefit assessment of the various migration projects | Module 035 |
| 1.F.4 Perform risk assessment | Module 035 |
| 1.F.5 Generate implementation roadmap (time-lined) | Module 035 |
| 1.F.6 Document Migration Plan | Module 035 |
Phase G: Implementation Governance | |
|
Topic |
Syllabus Reference(s) |
| 1.G.1 Formulate project recommendations | Module 036 |
| 1.G.2 Document Architecture Contract | Module 036 |
| 1.G.3 On-going implementation governance and architecture compliance review. | Module 036 |
Phase H: Architecture Change Management | |
| Topic | Syllabus Reference(s) |
| 1.H.1 Ongoing monitoring of technology changes | Module 037 |
| 1.H.2 Ongoing monitoring of business changes | Module 037 |
| 1.H.3 Assessment of changes and development of position to act | Module 037 |
| 1.H.4 Meeting of Architecture Board (or other governing council) to decide on handling changes (technology and business) | Module 037 |
Requirements Management | |
| Topic | Syllabus Reference(s) |
| 1.R.1 Key steps in the Requirements Management process | Module 038 |
2. TOGAF 8 Architecture Development Method (ADM) - Information Sets | |
| Topic | Syllabus Reference(s) |
|---|---|
| 2.1 Framework Definition | Modules 025 |
| 2.2 Architecture Principles | Modules 019 |
| 2.3 Business Principles, Goals, and Drivers | Modules 026 |
| 2.4 IT Governance Strategy | Modules 016 |
| 2.5 Request for Architecture Work | Modules 026 |
| 2.6 Statement of Architecture Work | Modules 026 |
| 2.7 Architecture Vision | Modules 026 |
| 2.8 Business Architecture | Modules 027 |
| 2.9 Business Architecture Report | Modules 027 |
| 2.10 Business Requirements | Modules 026 |
| 2.11 Technical Requirements | Modules 026 |
| 2.12 Gap analysis | Modules 027 |
| 2.13 Data Architecture | Modules 030 |
| 2.14 Data Architecture Report | Modules 030 |
| 2.15 Applications Architecture | Modules 029 |
| 2.16 Applications Architecture Report | Modules 029 |
| 2.17 Technical Architecture | Modules 031 |
|
2.18 Technical Architecture Report |
Modules 031 |
|
2.1 Architecture Viewpoints |
Modules 021 |
| 2.20 Architecture Views | Modules 021 |
| 2.21 Re-usable Architecture Building Blocks | Modules 009 |
| 2.22 Re-usable Solution Building Blocks | Modules 009 |
| 2.23 Impact Analysis - Project list | Modules 034 |
| 2.24 Impact Analysis - Migration Plan | Modules 035 |
| 2.25 Impact Analysis - Implementation recommendations | Modules 036 |
| 2.26 Architecture Contracts | Modules 036 |
| 2.27 Product Information | Modules 036 |
| 2.28 Request for Architecture Change | Modules 037 |
| 2.29 New Technology Report | Modules 037 |
| 2.30 Requirements Impact Statement | Modules 038 |
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 011 |
| 3.1.2 Taxonomy of Platform Services | Module 012 |
| 3.1.3 Taxonomy of Application Platform Service Qualities | Module 011 |
3.2 The Standards Information Base (SIB) | |
| Topic | Syllabus Reference(s) |
| 3.2.1 Access to the SIB | Module 010 |
| 3.2.2 Searching the SIB | Module 010 |
| 3.2.3 Using the information in the SIB | Module 032 |
4. The Enterprise Continuum | |
4.1 The Architecture Continuum | |
| Topic | Syllabus Reference(s) |
|---|---|
| 4.1.1 The concept of the Architecture Continuum | Module 009 |
| 4.1.2 Moving around the Architecture Continuum | Module 009 |
| 4.1.3 The Continuum as a repository of reusable Architecture Building Blocks | Module 009 |
| 4.1.4 The relationship to the Solutions Continuum | Module 009 |
4.2 The Solutions Continuum | |
| Topic | Syllabus Reference(s) |
| 4.2.1 The concept of the Solutions Continuum | Module 009 |
| 4.2.2 Moving around the Solutions Continuum | Module 009 |
| 4.2.3 The Solutions Continuum as a repository of reusable Solution Building Blocks | Module 009 |
5. TOGAF and Other Architectures / Frameworks | |
5.1 The Positioning of TOGAF | |
| Topic | Syllabus Reference(s) |
|---|---|
| 5.1.1 Positioning information | Modules 002, 003, 005, 007 |
| 5.1.2 Explaining it to users | Module 008 |
5.2 Examples | |
| Topic | Syllabus Reference(s) |
| Examples of other Architecture Frameworks referenced in TOGAF (for example, C4ISR, Enterprise Architecture Planning, Zachman Framework, etc.). | Modules 040, 041 |
6. Architecture Governance | |
6.1 Introduction to Governance | |
| Topic | Syllabus Reference(s) |
|---|---|
| 6.1.1 Nature of Governance | Module 016 |
| 6.1.2 Levels of Governance | Module 016 |
6.2 TOGAF Architecture Governance Framework | |
| Topic | Syllabus Reference(s) |
| 6.2.1 Conceptual Structure | Module 017 |
| 6.2.2 Organizational Structure | Module 017 |
6.3 Architecture Governance in Practice | |
| Topic | Syllabus Reference(s) |
| 6.3.1 Architecture Board | Module 017 |
| 6.3.2 Architecture Compliance | Module 018 |
| 6.3.3 Architecture Contracts | Module 024 |
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 The Open Group. All Rights Reserved.