Conformance Statement Checklist |
for TOGAF 7 TRAINING Product Standard
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 Checklist 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 Checklist.
Name | Organization | Email Address |
---|---|---|
Enter the name of the Organization (Enterprise, Division, etc.) for which TOGAF 7 TRAINING certification is being sought.
Enterprise Name | Division / Organization |
---|---|
Enter the name of the course for which TOGAF 7 TRAINING certification is being sought (or the names of the courses, where a group of related courses are to be certified).
Course Title and Version Number |
---|
Question 7 in the TOGAF TRAINING Conformance Statement Questionnaire asks about the topic coverage of the Course to be certified. The following table contains a checklist of all the items that should be covered in the syllabus of a conformant 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.
1. TOGAF Architecture Development Method (ADM) - Process |
|
Phase A: Initiation and Framework |
|
Topic | Syllabus Reference(s) |
---|---|
1.A.1. Establish IT Governance | |
1.A.2. Formulate, document, publish and mandate the Architecture Principles | |
1.A.3. Obtain and verify the Request for Architecture Work | |
1.A.4. Identify, document and rank the problem that is driving the project | |
1.A.5. Identify environment and document, as business architecture models, the business and technical environment where the problem situation is occurring | |
1.A.6. Identify and document desired objectives, the results of handling the problems successfully | |
1.A.7. Identify human actors and their place in business model, the human participants and their roles | |
1.A.8. Identify computer actors and their place in technology model, the computing elements and their roles | |
1.A.9. Identify and document roles, responsibilities and measures of success per actor, the required scripts per actor, and the desired results of handling the situation properly | |
1.A.10. Document the Statement of Architecture Work | |
1.A.11. Check the original motivation for the project against the Statement of Architecture Work and Business Architecture, and refine only if necessary | |
1.A.12. Document, verify and deliver Business Architecture Version 1. | |
Phase B: Baseline Description |
|
Topic | Syllabus Reference(s) |
1.B.1. Verify access to organization's Solutions Continuum to identify re-usable Solutions Building Blocks (if available) | |
1.B.2. Identify existing technology in a brainstorming session specifically set-up to identify re-usable assets | |
1.B.3. Brainstorm candidate architecture building blocks in a discovery session and document | |
1.B.4. Document, verify and deliver Business Architecture Version 2 | |
1.B.5. Add any newly identified re-usable Solutions Building Blocks to organization's Solutions Continuum | |
Phase C: Target Architecture |
|
Topic | Syllabus Reference(s) |
1.C.1. Create a baseline description in the TOGAF format | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.C.2. Consider different architectural viewpoints | |
|
|
|
|
|
|
|
|
|
|
|
|
1.C.3. Create an architectural model of building blocks | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.C.4. Select the services portfolio required per building block | |
|
|
|
|
|
|
|
|
|
|
|
|
1.C.5. Confirm that the business goals and objectives are met | |
|
|
|
|
|
|
1.C.6. Determine criteria for specification selection | |
|
|
|
|
|
|
1.C.7. Complete the architecture definition | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.C.8 Conduct a gap analysis | |
|
|
|
|
|
|
|
|
|
|
Phase D: Opportunities and Solutions |
|
Topic | Syllabus Reference(s) |
1.D.1 Verify access to functional descriptions of products that are candidates for the implementation | |
1.D.2 Verify access to architectural descriptions of elements that are candidates for the implementation | |
1.D.3 Brainstorming session on technical requirements from a functional perspective | |
1.D.4 Brainstorming session on co-existence and interoperability requirements | |
1.D.5 Architecture assessment and gap analysis. | |
1.D.6 Project identification and classification (such as new development, purchase opportunity, or redeployment of existing system) | |
1.D.7 Document, verify and deliver Impact Analysis Project List | |
Phase E: Migration Planning |
|
Topic | Syllabus Reference(s) |
1.E.1 Project prioritization | |
1.E.2 Migration brainstorm session | |
1.E.3 Dependencies, costs and benefits assessment of the various migration projects | |
1.E.4 Risk assessment | |
1.E.5 Roadmap (time-lined) generation | |
1.E.6 Document, verify and deliver Impact Analysis Migration Plan | |
Phase F: Implementation |
|
Topic | Syllabus Reference(s) |
1.F.1 Project recommendation formulation, for each separate implementation project | |
|
|
|
|
|
|
|
|
|
|
|
|
1.F.2 Document the Architecture Contract | |
|
|
Phase G: Architecture Maintenance |
|
Topic | Syllabus Reference(s) |
1.G.1 Verify access to new technology reports | |
1.G.2 Verify access to new business changes | |
1.G.3 Ongoing monitoring of technology changes | |
1.G.4 Ongoing monitoring of business changes | |
1.G.5 Assessment of changes and development of position to act | |
1.G.6 Meeting of governing council to decide on handling changes (technology and business) | |
1.G.7 Document, verify and deliver Technical Architecture updates. | |
1.G.8 Document, verify and deliver New Requests for Architecture Work |
2. TOGAF Architecture Development Method (ADM) - Information Sets |
|
Topic | Syllabus Reference(s) |
---|---|
2.1 The Architecture Principles | |
2.2 The Request for Architecture Work | |
2.3 The Statement of Architecture Work | |
2.4 Architecture Views | |
2.5 Re-usable Solution Building Blocks | |
2.6 Re-usable Architecture Building Blocks | |
2.7 Product Information | |
2.8 New Technology Reports | |
2.9 The Business Architecture | |
2.10 The Technical Architecture | |
2.11 The Impact Analysis | |
|
|
|
|
|
|
2.12 The Architecture Contract |
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 |
|
Examples of other Architecture Frameworks referenced in TOGAF (for example, C4ISR, Enterprise Architecture Planning, Zachman Framework, etc.). |