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:

  • All questions must have answers before the form is submitted to The Open Group for review and publication.
  • Some questions have Rationale statements that will help you in developing your answers.
  • If you have any questions or concerns, you can send mail to the TOGAF Certification Administrator at The Open Group.

Enter the name, and organization of the author of this Conformance Statement.

Name

Organization

Harmen van den Berg

BiZZdesign


1. Mandatory Requirements


1.1 Organization and Course Information

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

 BiZZdesign

Academy

 

Course Title and Version Number

 Practical Enterprise Architecture with TOGAFTM  8.1.1: Certification Training

 Version 1.0

 


1.2 Conformance Checklist - TOGAF 8 TRAINING

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

1.   TOGAF 8 Architecture Development Method (ADM) - Process

Preliminary Phase: Framework and Principles

Topic

Syllabus Reference(s)

1.P.1  Defining "How we do Architecture"

Part 2 section 2.1, slides 19-20

1.P.2  Defining the framework to be used

Part 2 section 2.1, slides 19-20

1.P.3  Defining architecture principles

Part 2 section 2.1, slides 19-20 and Part 4 section 2, slides 4‑12

1.P.4  Establishing IT Architecture Governance

Part 2 section 2.1, slides 19-20 and Part 4 section 5, slides 34‑49

Phase A: Architecture Vision

Topic

Syllabus Reference(s)

1.A.1. Project Establishment

Part 2 section 2.1, slides 22-27

1.A.2. Identifying Business Principles, Business Goals, and Business Drivers

Part 2 section 2.1, slides 22-27

1.A.3.  Reviewing Architecture Principles

Part 2 section 2.1, slides 22-27

1.A.4.  Defining Scope

Part 2 section 2.1, slides 22-27

1.A.5.  Defining Constraints

Part 2 section 2.1, slides 22-27

1.A.6.  Defining Stakeholders and concerns, Business Requirements, and Architecture Vision

Part 2 section 2.1, slides 22-27

1.A.7.  Documenting Statement of Architecture Work and Gaining Approval

Part 2 section 2.1, slides 22-27

Phase B: Business Architecture

Topic

Syllabus Reference(s)

1.B.1. Developing a Business Baseline Description.

Part 2 section 2.2, slides 29-35

1.B.2. Reference Models, Viewpoints and Tools.

Part 2 section 2.2, slides 29-35

 

1.B.3. Create Business Architecture Model(s).

Part 2 section 2.2, slides 29-35

 

1.B.4. Select Business Architecture building blocks

Part 2 section 2.2, slides 29-35

 

1.B.5. Conduct checkpoint review of architecture model.

Part 2 section 2.2, slides 29-35

 

1.B.6. Review non-functional (qualitative) criteria.

Part 2 section 2.2, slides 29-35

 

1.B.7. Complete the business architecture.

Part 2 section 2.2, slides 29-35

 

1.B.8. Gap analysis and report

Part 2 section 2.2, slides 29-35

Phase C: Information System Architecture - Data

Topic

Syllabus Reference(s)

1.CD.1. Developing a Data Baseline Description.

Part 2 section 2.2, slides 36-49

 

1.CD.2. Principles, Reference Models, Viewpoints and Tools.

Part 2 section 2.2, slides 36-49

 

1.CD.3. Create Data Architecture Model(s).

Part 2 section 2.2, slides 36-49

1.CD.4. Select Data Architecture building blocks

Part 2 section 2.2, slides 36-49

 

1.CD.5. Conduct checkpoint review of architecture model.

Part 2 section 2.2, slides 36-49

 

1.CD.6. Review non-functional (qualitative) criteria.

Part 2 section 2.2, slides 36-49

 

1.CD.7. Complete the Data Architecture.

Part 2 section 2.2, slides 36-49

1.CD.8. Gap analysis and report

Part 2 section 2.2, slides 36-49

Phase C: Information System Architecture - Applications

Topic

Syllabus Reference(s)

1.CA.1. Developing an Applications Baseline Description.

Part 2 section 2.2, slides 36-49

 

1.CA.2. Principles, Reference Models, Viewpoints and Tools.

Part 2 section 2.2, slides 36-49

 

1.CA.3. Create Applications Architecture Model(s).

Part 2 section 2.2, slides 36-49

 

1.CA.4. Select Applications Architecture building blocks

Part 2 section 2.2, slides 36-49

 

1.CA.5. Conduct checkpoint review of architecture model.

Part 2 section 2.2, slides 36-49

 

1.CA.6. Review non-functional (qualitative) criteria.

Part 2 section 2.2, slides 36-49

 

1.CA.7. Complete the Applications Architecture.

Part 2 section 2.2, slides 36-49

 

1.CA.8. Gap analysis and report

Part 2 section 2.2, slides 36-49

Phase D: Technology Architecture

Topic

Syllabus Reference(s)

1.D.1. Create Technology Baseline Description

Part 2 section 2.2, slides 50-67

 

1.D.2. Create Target Technology Architecture

Part 2 section 2.2, slides 50-67

 

1.D.2.1. Create a baseline description in the TOGAF format

Part 2 section 2.2, slides 50-67

 

1.D.2.2. Consider different architectural viewpoints

Part 2 section 2.2, slides 50-67

 

1.D.2.3. Create an architectural model of building blocks

Part 2 section 2.2, slides 50-67

 

1.D.2.4. Select the services portfolio required per building block

Part 2 section 2.2, slides 50-67

 

1.D.2.5. Confirm that business goals and objectives are met

Part 2 section 2.2, slides 50-67

 

1.D.2.6. Determine criteria for specification selection

Part 2 section 2.2, slides 50-67

 

1.D.2.7. Complete the architecture definition

Part 2 section 2.2, slides 50-67

 

1.D.2.8. Conduct gap analysis

Part 2 section 2.2, slides 50-67

Phase E: Opportunities and Solutions

Topic

Syllabus Reference(s)

1.E.1 Identify key business drivers constraining sequence of implementation

Part 2 section 2.3, slides 68-72

 

1.E.2 Review gap analysis

Part 2 section 2.3, slides 68-72

1.E.3 Brainstorm technical requirements from functional perspective

Part 2 section 2.3, slides 68-72

 

1.E.4 Brainstorm co-existence and interoperability requirements

Part 2 section 2.3, slides 68-72

 

1.E.5 Architecture assessment and gap analysis.

Part 2 section 2.3, slides 68-72

 

1.E.6 Identify major work packages or projects, classify as new development, purchase opportunity, or reuse of existing system.

Part 2 section 2.3, slides 68-72

 

Phase F: Migration Planning

Topic

Syllabus Reference(s)

1.F.1 Prioritize projects

Part 2 section 2.3, slides 73-77

1.F.2 Estimate resource requirements and availability

Part 2 section 2.3, slides 73-77

 

1.F.3 Perform cost / benefit assessment of the various migration projects

Part 2 section 2.3, slides 73-77

 

1.F.4 Perform risk assessment

Part 2 section 2.3, slides 73-77

1.F.5 Generate implementation roadmap (time-lined)

Part 2 section 2.3, slides 73-77

 

1.F.6 Document Migration Plan

Part 2 section 2.3, slides 73-77

Phase G: Implementation Governance

Topic

Syllabus Reference(s)

1.G.1 Formulate project recommendations

Part 2 section 2.3, slides 78-82

1.G.2 Document Architecture Contract

Part 2 section 2.3, slides 78-82

1.G.3 On-going implementation governance and architecture compliance review.

Part 2 section 2.3, slides 78-82

 

Phase H: Architecture Change Management

Topic

Syllabus Reference(s)

1.H.1 Ongoing monitoring of technology changes

Part 2 section 2.4, slides 84-88

 

1.H.2 Ongoing monitoring of business changes

Part 2 section 2.4, slides 84-88

 

1.H.3 Assessment of changes and development of position to act

Part 2 section 2.4, slides 84-88

 

1.H.4 Meeting of Architecture Board (or other governing council) to decide on handling changes (technology and business)

Part 2 section 2.4, slides 84-88

 

Requirements Management

Topic

Syllabus Reference(s)

1.R.1 Key steps in the Requirements Management process

Part 2 section 2.4, slides 89-93

 

2.   TOGAF 8 Architecture Development Method (ADM) - Information Sets

Topic

Syllabus Reference(s)

2.1 Framework Definition

Part 2 section 1

2.2 Architecture Principles

Part 4 section 2, slides 4-12

2.3 Business Principles, Goals, and Drivers

Part 2 section 2.1, slides 20-21

2.4 IT Governance Strategy

Part 2 section 2.1, slides 20-21

2.5 Request for Architecture Work

Part 2 section 1, slides 4-5

2.6 Statement of Architecture Work

Part 2 section 1, slides 6-7

2.7 Architecture Vision

Part 2 section 1, slides 8-9

2.8 Business Architecture

Part 2 section 2.2, slides 29-35

2.9 Business Architecture Report

Part 2 section 2.2, slides 29-35

2.10 Business Requirements

Part 2 section 2.4, slides 91-93

2.11 Technical Requirements

Part 2 section 2.4, slides 91-93

2.12 Gap analysis

Part 2 section 2.4, slides 91-93

2.13 Data Architecture

Part 2 section 2.2, slides 36-49

2.14 Data Architecture Report

Part 2 section 2.2, slides 36-49

2.15 Applications Architecture

Part 2 section 2.2, slides 36-49

2.16 Applications Architecture Report

Part 2 section 2.2, slides 36-49

2.17 Technical Architecture

Part 2 section 2.2, slides 50-67

2.18 Technical Architecture Report

Part 2 section 2.2, slides 50-67

2.19 Architecture Viewpoints

Part 4 section 4, slides 22-33

2.20 Architecture Views

Part 4 section 4, slides 22-33

2.21 Re-usable Architecture Building Blocks

Part 3 section 1, slides 3-5

2.22 Re-usable Solution Building Blocks

Part 3 section 1, slides 3-5

2.23 Impact Analysis - Project list

Part 2 section 1, slides 12-13 and Part 2 section 2.3, slides 68-72

2.24 Impact Analysis - Migration Plan

Part 2 section 1, slides 12-13 Part 2 section 2.3, slides 73-77

2.25 Impact Analysis - Implementation recommendations

Part 2 section 1, slides 12-13 Part 2 section 2.3, slides 78-82

2.26 Architecture Contracts

Part 2 section 1, slides 10-11

2.27 Product Information

Part 2 section 2.4, slides 84-88

2.28 Request for Architecture Change

Part 2 section 2.4, slides 84-88

2.29 New Technology Report

Part 2 section 2.4, slides 84-88

2.30 Requirements Impact Statement

Part 2 section 2.4, slides 89-93

 

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

Part 3 section 4, slides 13-16

3.1.2 Taxonomy of Platform Services

Part 3 section 4, slides 21-32

3.1.3 Taxonomy of Application Platform Service Qualities

Part 3 section 4, slide 33

3.2 The Standards Information Base (SIB)

Topic

Syllabus Reference(s)

3.2.1 Access to the SIB

Part 3 section 4, slides 35-36

3.2.2 Searching the SIB

Part 3 section 4, slides 35-36

3.2.3 Using the information in the SIB

Part 3 section 4, slides 35-36

 

4. The Enterprise Continuum

4.1 The Architecture Continuum

Topic

Syllabus Reference(s)

4.1.1 The concept of the Architecture Continuum

Part 3 section 2, slides 6-7

4.1.2 Moving around the Architecture Continuum

Part 3 section 2, slides 6-7

4.1.3 The Continuum as a repository of reusable Architecture Building Blocks

Part 3 section 1, slides 3-5 and section 2, slides 6-7

4.1.4 The relationship to the Solutions Continuum

Part 3 section 2, slide 9

4.2 The Solutions Continuum

Topic

Syllabus Reference(s)

4.2.1 The concept of the Solutions Continuum

Part 3 section 2, slide 8

4.2.2 Moving around the Solutions Continuum

Part 3 section 2, slide 8

4.2.3 The Solutions Continuum as a repository of reusable Solution Building Blocks

Part 3 section 1, slides 3-5 and section 2, slides 8

 

5. TOGAF and Other Architectures / Frameworks

5.1 The Positioning of TOGAF

Topic

Syllabus Reference(s)

5.1.1 Positioning information

Part 5

5.1.2 Explaining it to users

Part 5

5.2 Examples

Topic

Syllabus Reference(s)

Examples of other Architecture Frameworks referenced in TOGAF (for example, C4ISR, Enterprise Architecture Planning, Zachman Framework, etc.).

Part 5

 

6. Architecture Governance

6.1 Introduction to Governance

Topic

Syllabus Reference(s)

6.1.1 Nature of Governance

Part 4 section 5, slides 35-38

6.1.2 Levels of Governance

Part 4 section 5, slides 35-38

6.2 TOGAF Architecture Governance Framework

Topic

Syllabus Reference(s)

6.2.1 Conceptual Structure

Part 4 section 5, slide 50

6.2.2 Organizational Structure

Part 4 section 5, slide 51

6.3 Architecture Governance in Practice

Topic

Syllabus Reference(s)

6.3.1 Architecture Board

Part 4 section 5, slides 46-49

6.3.2 Architecture Compliance

Part 4 section 5, slides39-45

6.3.3 Architecture Contracts

Part 2 section 1, slides 10-11


2. Optional Requirements


2.1 Optional Training in TOGAF Tools

Does the Course cover the use of tools certified under the TOGAF 8 TOOL SUPPORT program?

Enter "Yes" or "No" as appropriate.

Response: Yes

_________________________

If YES, identify the tool(s) covered:

Product Supplier

Product Identification

Version/Release Number

Syllabus Reference:(s)

BiZZdesign

BiZZdesign Architect

2

Part 6; and on many places in part 2, 3 and 4

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Rationale:

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.)

Reference:

Product Standard: TOGAF 8 TRAINING


Copyright © 2003-2006 The Open Group. All Rights Reserved.