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