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