TOGAF 9 Part 1 Foundation Level E-Learning Workbook

TOGAF 9 Part 1 Foundation Level
E-Learning Workbook
The aim of this workbook is to provide you with a mechanism to make notes while you are completing the online course in order to prepare you for the TOGAF 9 Certification Exam. The workbook consists of thirteen separate modules and should be used in conjunction with the thirteen modules of the E-learning course.
2012 Edition
Table of Contents
Introduction ...................................................................................................................................................2 PART I - Module 1: The TOGAF 9 certification program ....................................................................3 PART 1 - Module 2: The basic concepts of Enterprise Architecture and TOGAF ..............................4 PART I - Module 3: The core concepts...................................................................................................8 PART II - Module 4: How each of the ADM phases contributes to the success of enterprise architecture .............................................................................................................................................. 11 PART II - Module 5: The ADM cycle and the objectives of each phase, and how to adapt and scope the ADM ................................................................................................................................................. 15 PART III - Module 6: The ADM guidelines and techniques .............................................................. 24 PART IV - Module 7: The concepts of views and viewpoints and their role in communicating with stakeholders ............................................................................................................................................ 30 PART IV - Module 8: The concept of building blocks ........................................................................ 32 PART IV - Module 9: The key deliverables of the ADM cycle ........................................................... 34 PART V - Module 10: The concept of the Enterprise Continuum; its purpose and constituent parts ................................................................................................................................................................. 36 PART V - Module 11: The Architecture Repository............................................................................ 40 PART VI - Module 12: The TOGAF reference models ..................................................................... 42 PART VII - Module 13: How Architecture Governance contributes to the Architecture Development Cycle ........................................................................................................................................................ 44 Appendix A: The key terminology of TOGAF 9 ................................................................................. 48
Introduction
The aim of this workbook is to allow you to make notes about key learning points as they come up in the online course. This will help you make sure you understand the important concepts and ideas in each module. These notes will also be valuable when you are preparing for the TOGAF 9 Foundation Level Exam. This workbook consists of thirteen modules, divided into seven parts, which correspond to the modules you will be completing during the online course. At the end of each part you can test yourself by taking the online quiz. How to Study using the Workbook A number of learning requirements are outlined in the workbook for every module. These requirements are defined by The Open Group and form the basis of everything you need to know in order to pass the TOGAF Part 1 Examination. As you navigate through the e-learning course, you can check the required learning unit for each slide and make notes against it. To match up each learning requirement in the workbook with the learning content on your screen you can cross reference the corresponding slide name and its unique reference code. Wherever you are in the e-learning course you can check the learning requirement from within your browser by opening the Reference Materials box in the menu bar directly beneath the slide. You can access the TOGAF Version 9.1 online document if you would like to
The online version of TOGAF 9 is used as a reference in this study guide. http://pubs.opengroup.org/architecture/togaf9-doc/arch/
PART I - Module 1: The TOGAF 9 certification program

Purpose:
The purpose of this Learning Unit is to help the Candidate understand the TOGAF Certification program.
Learning Outcomes
Explain the TOGAF Certification program, and distinguish between the levels for certification
Note: This Learning unit is not part of the material required to study for certification
PART 1 - Module 2: The basic concepts of Enterprise Architecture and TOGAF

Purpose:
The purpose of this Learning Unit is to introduce the basic concepts of Enterprise Architecture and TOGAF.
Learning Outcomes
List the business benefits of having an enterprise architecture REFERENCE: M1-026 (Read Why does EA Matter attachment)
Notes
(TOGAF9 CHAPTER 1.2)
Describe the structure of TOGAF, and briefly explain the contents of each of the parts
REFERENCE: M1-040 (Read Chapter 1 of the TOGAF 9 standard attachment)

Notes
Briefly describe the relationship between the ADM and other parts of TOGAF (Enterprise Continuum, Architecture Repository, Foundation Architecture, Supporting Guidelines and Techniques)

Notes
Describe what an enterprise is

Notes
Explain the purpose of an enterprise architecture

Notes
Explain what architecture is in the context of TOGAF REFERENCE: M1-019, M1-084

Notes
List the different types of architecture that TOGAF deals with REFERENCE: M1-021
Notes
Define what an Architecture Framework is REFERENCE: M1-030, M1-080, M1-081, M1-082

Notes
Explain why TOGAF is suitable as a framework for enterprise architecture REFERENCE: M1-031
Notes
Briefly explain what TOGAF is REFERENCE: M1-042

Notes
PART I - Module 3: The core concepts

Purpose
The purpose of this Learning Unit is to help the Candidate explain the core concepts of TOGAF.
Learning Outcomes
Explain the purpose of the supporting guidelines and techniques, and the difference between guidelines and techniques REFERENCE: M2-007
Notes
The Architecture Content Framework: deliverables, artifacts, and building blocks (TOGAF9 CHAPTER 2.5, TOGAF9 CHAPTER 31.1) REFERENCE: M2-012
Notes
The Enterprise Continuum REFERENCE: M2-014

Notes
The Architecture Repository REFERENCE: M2-015

Notes
How to establish and maintain an enterprise Architecture Capability REFERENCE: M2-021

Notes
Establishing the Architecture Capability as an operational entity REFERENCE: M2-022

Notes
The TOGAF Document Categorization Model REFERENCE: M2-023

Notes
10
PART II - Module 4: How each of the ADM phases contributes to the success of enterprise architecture
Purpose
The purpose of this Learning Unit is to understand the ADM cycle, briefly explain the objective of each phase in the cycle, and how to adapt and scope the ADM for use.
Learning Outcomes
How to use TOGAF with other frameworks REFERENCE: M3-011

Notes
List the main reasons why you would need to adapt the ADM REFERENCE: M3-011
Notes
11
Explain the need for the ADM process to be governed

REFERENCE: M3-012 Notes
Describe the major information areas managed by a governance repository (TOGAF9 CHAPTER 5.4) REFERENCE: M3-013
Notes
Briefly explain the reasons for scoping an architecture activity REFERENCE: M3-014
Notes
12
List the possible dimensions for limiting the scope REFERENCE: M3-015
Notes
Briefly explain the need for an integration framework that sits above individual architectures REFERENCE: M3-016
Notes
The ADM: phase names and the purpose of each phase (high-level) REFERENCE: M3-006
Notes
13
Briefly describe the key points of the ADM cycle SLIDE REFERENCE: M3-008
Notes
Describe a typical set of steps, such as those for Phase D

REFERENCE: M3-009 Notes
Describe the versioning convention for deliverables used in Phases A to D REFERENCE: M3-010
Notes
14
PART II - Module 5: The ADM cycle and the objectives of each phase, and how to adapt and scope the ADM
Purpose
The purpose of this Learning Unit is to help the Candidate understand how each of the ADM phases contributes to the success of enterprise architecture by understanding the objectives, and the approach for each phase.
Learning Outcomes
Briefly describe the ADM cycle, its phases, and the objective of each phase
REFERENCE: Review ALL slides of Module 5 to answer this Learning Outcome Notes
Describe the objectives of the Preliminary Phase REFERENCE: F6-005, F6-006

Notes
(TOGAF9 CHAPTER 6 SECTION 1)
15
Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase
(TOGAF9 CHAPTER 6 SECTION 2):
Defining the enterprise Identifying key drivers and elements in the organizational context Defining the requirements for architecture work Defining the Architecture Principles that will inform any architecture work Defining the framework to be used Defining the relationships between management frameworks Outlining the enterprise architecture maturity
REFERENCE: F6-008
Notes
Describe the main objectives of Phase A REFERENCE: F6-009

Notes
16
Briefly explain the two main aspects to the approach in Phase A Creating the Architecture Vision Business Scenarios
REFERENCE: F6-012
Notes
Describe the main objectives of Phase B REFERENCE: F6-017 - F6-018

Notes
17
Briefly explain the main aspects of the approach in Phase B Developing the Baseline Description Business Modeling Using the Architecture Repository
REFERENCE: F6-019
Notes
Describe the main objectives of Phase C REFERENCE: F6-024

Notes
(TOGAF9 CHAPTER 9, 10, 11 SECTION 1)
18
Briefly explain the approach in Phase C recommended by TOGAF, including: Key considerations for Data Architecture (TOGAF9 CHAPTER 10 SECTION 2) Using the Architecture Repository (TOGAF9 CHAPTER 10 SECTION 2, CHAPTER 11 SECTION 2)
REFERENCE: F6-027 F6-028

Notes
Describe the main objectives of Phase D REFERENCE: F6-032

Notes
19
Briefly explain the approach to Phase D including: Using the Architecture Repository
REFERENCE: F6-034
Notes
Describe the main objectives of Phase E REFERENCE: F6-035

Notes
Briefly explain the approach to Phase E REFERENCE: F6-037, F6-056

Notes
20
Describe the main objectives of Phase F REFERENCE: F6-038

Notes
Briefly explain the approach to Phase F REFERENCE: F6-040

Notes
Describe the main objectives of Phase G REFERENCE: F6-041

Notes
21
Briefly explain the approach to Phase G REFERENCE: F6-043

Notes
Describe the main objectives of Phase H REFERENCE: F6-044

Notes
Briefly explain the approach to Phase H including:
(TOGAF9 CHAPTER 16 SECTION 2),:
Drivers for change Enterprise architecture management process Guidelines for maintenance versus architecture redesign
REFERENCE: F6-046
Notes
22
Briefly explain how Requirements Management fits into the ADM cycle REFERENCE: F6-052
Notes
Describe the nature of the Requirements Management process REFERENCE: F6-052

Notes
Describe the approach to Requirements Management REFERENCE: F6-053 - F6-054

Notes
23
PART III - Module 6: The ADM guidelines and techniques

Purpose
The purpose of this Learning Unit is to introduce the Candidate to the ADM Guidelines and Techniques available to support application of the ADM.
Learning Outcomes
Briefly explain the contents of Part III of TOGAF 9 REFERENCE: F7-005, F7-006
Notes
Briefly explain the need for Architecture Principles and where they are used within TOGAF REFERENCE: F7-008, F7-009
Notes
24
Describe the standard template for Architecture Principles REFERENCE: F7-010, F7-011, F7-012
Notes
Explain what makes a good Architecture Principle REFERENCE: F7-013

Notes
Understand the Business Transformation Readiness program REFERENCE: F7-022

Notes
25
Understand where Business Transformation Readiness is used within the ADM (TOGAF9 CHAPTER 30 SECTION 1) REFERENCE: F7-023
Notes
Understand the characteristics of Risk Management REFERENCE: F7-025, F7-30

Notes
Understand where Risk Management is used within the TOGAF ADM REFERENCE: F7-026, F7-031
Notes
26
Understand Capability-Based Planning REFERENCE: F7-028

Notes
Understand what a Business Scenario is and its purpose REFERENCE: F7-014, F7-015
Notes
Explain where Business Scenarios are used within the ADM cycle REFERENCE: F7-016
Notes
27
Explain the term interoperability REFERENCE: F7-019

Notes
Understand the use of Interoperability Requirements within the TOGAF ADM REFERENCE: F7-020
Notes
Explain the purpose of Gap Analysis REFERENCE: F7-017

Notes
28
Describe the Gap Analysis technique REFERENCE: F7-018

Notes
29
PART IV - Module 7: The concepts of views and viewpoints and their role in communicating with stakeholders
Purpose
The purpose of this Learning Unit is to help the Candidate understand the concepts of views and viewpoints, and their role in communicating with stakeholders as well as applying them to the Architecture Development Cycle.
Learning Outcomes
Discuss the relationship between stakeholders, concerns, views, and viewpoints REFERENCE: M12-010
Notes
Define and explain the following key concepts (TOGAF9 CHAPTER 35 SECTION 1): Stakeholders Concerns Views Viewpoints
REFERENCE: M12-006, M12-007, M12-008, M12-009

Notes
30
Describe the view creation process REFERENCE: M12-018, M12-019, M12-020

Notes
Describe a simple example of a viewpoint and view REFERENCE: M12-013, M12-014

Notes
31
PART IV - Module 8: The concept of building blocks

Purpose
The purpose of this Learning Unit is to help the Candidate understand the concept of building blocks within TOGAF.
Learning Outcomes
Define what a building block is, and explain what makes a good building block REFERENCE: M13-005, M13-006
Notes
Explain the distinction between Architecture Building Blocks and Solution Building Blocks REFERENCE: M13-009, M13-011
Notes
32
Briefly explain the use of building blocks in the ADM cycle REFERENCE: M13-013
Notes
Describe the characteristics of an Architecture Pattern REFERENCE: M13-022

Notes
Briefly explain the approach taken in the Building Blocks Example given in TOGAF REFERENCE: M13-023
Notes
33
PART IV - Module 9: The key deliverables of the ADM cycle

Purpose
The purpose of this Learning Unit is to help the Candidate understand key deliverables of the ADM cycle.
Learning Outcomes
Briefly explain the role of architecture deliverables across the ADM cycle (TOGAF9 CHAPTER 36 SECTION 1) REFERENCE: F11-005
Notes
Briefly explain the purpose of the following deliverables
Architecture Building Blocks Architecture Contract Architecture Definition Document Architecture Principles Architecture Repository Architecture Requirements Architecture Roadmap Architecture Vision Business Principles, Business Goals, and Business Drivers Capability Assessment Change Request Communications Plan Compliance Assessment Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Requirements Impact Assessment Solution Building Blocks Statement of Architecture Work
34
Tailored Architecture Framework Transition Architecture
REFERENCE: F11-006 (Get the complete set of TOGAF deliverables with their descriptions from attachments)
Notes
35
PART V - Module 10: The concept of the Enterprise Continuum; its purpose and constituent parts
Purpose
The purpose of this Learning Unit is to help the Candidate understand the concept of the Enterprise Continuum, its purpose, and constituent parts.
Learning Outcomes
Briefly explain what the Enterprise Continuum is REFERENCE: M4-005

Notes
Explain the purpose of the Enterprise Continuum REFERENCE: M4-007, M4-008, M4-009, M4-010
Notes
36
Explain how it is used in organizing and developing an architecture REFERENCE: M4-008

Notes
Explain how the Enterprise Continuum promotes re-use of architecture artefacts (TOGAF9 CHAPTER 39 SECTION 2) REFERENCE: M4-009
Notes
Describe the constituents of the Enterprise Continuum REFERENCE: M4-010

Notes
37
List the stages of architecture evolution defined in the Architecture Continuum REFERENCE: M4-011
Notes
Explain the purpose of the Solutions Continuum REFERENCE: M4-015

Notes
List the stages of architecture evolution defined in the Solutions Continuum REFERENCE: M4-015
Notes
38
Explain the purpose of the Architecture Continuum REFERENCE: M4-012, M4-013, M4-014
Notes
Explain the relationship between the Enterprise Continuum and the TOGAF ADM REFERENCE: M4-019, M4-020
Notes
Explain the high-level issues with tool standardization REFERENCE: M4-022, M4-024, M4-025
Notes
39
PART V - Module 11: The Architecture Repository

Purpose
The purpose of this Learning Unit is to help the Candidate understand the concept of the Enterprise Continuum, its purpose, and constituent parts.
Learning Outcomes
Describe the Architecture Repository REFERENCE: M5-005, M5-006

Notes
(TOGAF9 CHAPTER 41)
Explain the relationship between the Enterprise Continuum and the Architecture Repository (TOGAF9 CHAPTER 39 SECTION 1, CHAPTER 41 SECTION 1) REFERENCE: M5-015
Notes
40
Describe the classes of information held in the Architecture Repository REFERENCE: M5-006
Notes
List the three levels of the Architecture Landscape REFERENCE: M5-008

Notes
Explain the purpose of the Standards Information Base within the Architecture Repository REFERENCE: M5-010, M5-012, M5-013
Notes
41
PART VI - Module 12: The TOGAF reference models

Purpose
The purpose of this Learning Unit is to introduce the TOGAF Reference Models.
Learning Outcomes
Describe the major characteristics of a Foundation Architecture REFERENCE: F12-005

Notes
Explain the role of the TRM as a Foundation Architecture REFERENCE: F12-008

Notes
(TOGAF9 CHAPTER 43 SECTION 1, SECTION 3)
42
Briefly explain the basic concepts of the III-RM (TOGAF9 CHAPTER 44 SECTION 1)
REFERENCE: F12-016, F12-017 Notes
Briefly explain the relationship of the III-RM to the concept of Boundaryless Information Flow
REFERENCE: F12-009, F12-010 Notes
43
PART VII - Module 13: How Architecture Governance contributes to the Architecture Development Cycle
Purpose
The purpose of this Learning Unit is to help the Candidate understand how Architecture Governance contributes to the Architecture Development Cycle.
Learning Outcomes
Briefly explain the concept of Architecture Governance REFERENCE: M9-004, M9-005, M9-007, M9-008, M9-009, M9-010
Notes
Describe the main concepts that make up an Architecture Governance framework REFERENCE: M9-011, M9-012, M9-014
Notes
44
Explain why Architecture Governance is beneficial REFERENCE: M9-017

Notes
List the reasons for having an Architecture Board REFERENCE: M9-019

Notes
List the responsibilities of an Architecture Board REFERENCE: M9-021, M9-022

Notes
45
Briefly explain the role of Architecture Contracts REFERENCE: M9-023, M9-024, M9-025
Notes
Briefly explain the meaning of Architecture Compliance REFERENCE: M9-026

Notes
Briefly explain the need for Architecture Compliance REFERENCE: M9-027

Notes
46
Briefly explain the purpose of Architecture Compliance Reviews REFERENCE: M9-028

Notes
Briefly describe the Architecture Compliance Review process REFERENCE: M9-029

Notes
Briefly explain how the ADM can be used to establish an Architecture Capability REFERENCE: M9-030
Notes
47
Appendix A: The key terminology of TOGAF 9

Purpose:
The purpose of this Learning Unit is to help the Candidate understand the key terminology of TOGAF. (Also listed as Glossary part of Good eLearning)
TOGAF 9 Learning Outcomes
01 Activity
A task or collection of tasks that support the functions of an organization. For example, user entering data into an IT system or traveling to visit customers.
02 Application
A deployed and operational IT system that supports business functions and services; for example, a payroll. Applications use data and are supported by multiple technology components but are distinct from the technology components that support the application.
03 Application Architecture
A description of the major logical grouping of capabilities that manage the data objects necessary to process the data and support the business.
04 Architecture
1. A formal description of a system, or a detailed plan of the system at component level, to guide its implementation (source: ISO/IEC 42010:2007). 2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution overtime.
05 Architecture Building Block(ABB)

A constituent of the architecture model that describes a single aspect of the overall model.
06 Architecture Development Method (ADM)

The core of TOGAF. A step-by-step approach to develop and use an enterprise architecture.
07 Architecture Domain
The architectural area being considered. There are four architecture domains within TOGAF: business, data, application, and technology.
08 Architecture Framework
A foundational structure, or set of structures, which can be used for developing a broad range of different architectures. It should contain a method for designing an information system in terms of a set
48
of building blocks, and for showing how the building blocks together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.
09 Architecture Principles
A qualitative statement of intent that should be met by the architecture. Has at least a supporting rationale and a measure of importance.
10 Architecture View
See Definition 47.
11 Architecture Vision
1. A high-level, aspirational view of the Target Architecture. 2. A phase in the ADM which delivers understanding and definition of the Architecture Vision. 3. A specific deliverable describing the Architecture Vision.
12 Baseline
A specification that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development or change and that can be changed only through formal change control procedures or a type of procedure such as configuration management.
13 Baseline Architecture
The existing defined system architecture before entering a cycle of architecture review and redesign.
14 Building Block
Represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to ``architectures'' or ``solutions''.
15 Business Architecture
The business strategy, governance, organization, and key business processes information, as well as the interaction between these concepts.
16 Business Governance
Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.
49
17 Capability
An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve. For example, marketing, customer contact, or outbound telemarketing.
18 Concerns
The key interests that are crucially important to the stakeholders in a system, and determine the acceptability of the system. Concerns may pertain to any aspect of the system's functioning, development, or operation, including considerations such as performance, reliability, security, distribution, and evolvability.
19 Constraint
An external factor that prevents an organization from pursuing particular approaches to meet its goals. For example, customer data is not harmonized within the organization, regionally or nationally, constraining the organization's ability to offer effective customer service.
20 Data Architecture
The structure of an organization's logical and physical data assets and data management resources.
21 Deliverable
An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.
22 Enterprise
The highest level(typically) of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.
23 Foundation Architecture
An architecture of generic services and functions that provides a foundation on which more specific architectures and architectural components can be built. The TOGAF Foundation Architecture includes a Technical Reference Model (TRM).
24 Gap
A statement of difference between two states. Used in the context of gap analysis, where the difference between the Baseline and Target Architecture is identified.
25 Governance
50
The discipline of monitoring, managing, and steering a business (or IS/IT landscape) to deliver the business outcome required.
26 Information
Any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms.
27 Information Technology (IT)

1. The lifecycle management of information and related technology used by an organization. 2. An umbrella term that includes all or some of the subject areas relating to the computer industry, such as Business Continuity, Business IT Interface, Business Process Modeling and Management, Communication, Compliance and Legislation, Computers, Content Management, Hardware, Information Management, Internet, Offshoring, Networking, Programming and Software, Professional Issues, Project Management, Security, Standards, Storage, Voice and Data Communications. Various countries and industries employ other umbrella terms to describe this same collection. 3. A term commonly assigned to a department within an organization tasked with provisioning some or all of the domains described in (2) above . 4. Alternate names commonly adopted include Information Services, Information Management, et al.
28 Logical
An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure. For example, the products from infrastructure software vendors can all be logically grouped as Java application server platforms.
29 Metadata
Data about data, of any sort in any media, that describes the characteristics of an entity.
30 Meta model
A model that describes how and with what the architecture will be described in a structured way.
31 Method
A defined, repeatable approach to address a particular type of problem.
32 Methodology
A defined, repeatable series of steps to address a particular type of problem, which typically centers on a defined process, but may also include definition of content.
33 Model
A representation of a subject of interest. A model provides a smaller scale, simpliFIed, and/or abstract representation of the subject matter. A model is constructed as a ``means to an end''. In the context of enterprise architecture, the subject matter is a whole or part of the enterprise and the end is the ability to
51
construct ``views'' that address the concerns of particular stakeholders; i.e., their ``viewpoints'' in relation to the subject matter.
34 Modeling
A technique through construction of models which enables a subject to be represented in a form that enables reasoning, insight, and clarity concerning the essence of the subject matter.
35 Objective
A time-bounded milestone for an organization used to demonstrate progress towards a goal; for example, ``Increase Capacity Utilization by 30% by the end of 2009 to support the planned increase in market share''.
36 Physical
A description of a real-world entity. Physical elements in an enterprise architecture may still be considerably abstracted from Solution Architecture, design, or implementation views.
37 Reference Model (RM)

A reference model is an abstract framework for understanding significant relationships among the entities of [an] environment, and for the development of consistent standards or specifications supporting that environment. A reference model is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. A reference model is not directly tied to any standards, technologies, or other concrete implementation details, but it does seek to provide common semantics that can be used unambiguously across and between different implementations. Note:The source of this definition is OASIS; refer to http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
38 Repository
A system that manages all of the data of an enterprise, including data and process models and other enterprise information. Hence, the data in a repository is much more extensive than that in a data dictionary, which generally defines only the data making up a database.
39 Requirement
A quantitative statement of business need that must be met by a particular architecture or work package.
40 Solution Architecture
A description of a discrete and focused business operation or activity and how IS/IT supports that operation. A Solution Architecture typically applies to a single project or project release, assisting in the translation of requirements into a solution vision, high-level business and/or IT system specifications, and a portfolio of implementation tasks.
52
41 Solution Building Block(SBB)

A candidate physical solution for an Architecture Building Block(ABB); e.g., a Commercial Off-TheShelf (COTS) package, that is a component of the Acquirer view of the architecture.
42 Stakeholder
An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, the outcome of the architecture. Different stakeholders with different roles will have different concerns.
43 Strategic Architecture
A summary formal description of the enterprise, providing an organizing framework for operational and change activity, and an executive-level, long-term view for direction setting.
44 Target Architecture
The description of a future state of the architecture being developed for an organization. There may be several future states developed as a roadmap to show the evolution of the architecture to a target state.
45 Technology Architecture
The logical software and hardware capabilities that are required to support deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, and standards.
46 Transition Architecture
A formal description of the enterprise architecture showing periods of transition and development for particular parts of the enterprise. Transition Architectures are used to provide an overview of current and target capability and allow for individual work packages and projects to be grouped into managed portfolios and programs.
47 View
The representation of a related set of concerns. A view is what is seen from a viewpoint. An architecture view maybe represented by a model to demonstrate to stakeholders their areas of interest in the architecture. A view does not have to be visual or graphical in nature.
48 Viewpoint
A definition of the perspective from which a view is taken. It is a specification of the conventions for constructing and using a view (often by means of an appropriate schema or template). A view is what you see; a viewpoint is where you are looking from the vantage point or perspective that determines what you see.
53

TOGAF 9 Part 1 Foundation Level E-Learning Workbook

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TOGAF 9 Part 1 Foundation Level E-Learning Workbook

Uploaded by

Copyright:

Available Formats

TOGAF 9 Part 1 Foundation Level

PART I - Module 1: The TOGAF 9 certification program

PART 1 - Module 2: The basic concepts of Enterprise Architecture and TOGAF

(TOGAF9 CHAPTER 1.2)

(TOGAF9 CHAPTER 1.1)

REFERENCE: M1-040 (Read Chapter 1 of the TOGAF 9 standard attachment)

(TOGAF9 CHAPTER 5.1)

REFERENCE: M3-007 (Read Chapter 1 of the TOGAF 9 standard attachment)

Describe what an enterprise is

(TOGAF9 CHAPTER 1.2)

REFERENCE: M1-018 (Read Chapter 1 of the TOGAF 9 standard attachment)

Explain the purpose of an enterprise architecture

(TOGAF9 CHAPTER 1.2)

REFERENCE: M1-022 (Read Chapter 1 of the TOGAF 9 standard attachment)

Explain what architecture is in the context of TOGAF REFERENCE: M1-019, M1-084

(TOGAF9 CHAPTER 2.2)

(TOGAF9 CHAPTER 2.3)

Define what an Architecture Framework is REFERENCE: M1-030, M1-080, M1-081, M1-082

(TOGAF9 CHAPTER 1.2)

(TOGAF9 CHAPTER 1.2)

Briefly explain what TOGAF is REFERENCE: M1-042

(TOGAF9 CHAPTER 2.1)

PART I - Module 3: The core concepts

(TOGAF9 CHAPTER 5.1)

The Enterprise Continuum REFERENCE: M2-014

(TOGAF9 CHAPTER 2.6)

The Architecture Repository REFERENCE: M2-015

(TOGAF9 CHAPTER 2.7)

How to establish and maintain an enterprise Architecture Capability REFERENCE: M2-021

(TOGAF9 CHAPTER 2.8)

Establishing the Architecture Capability as an operational entity REFERENCE: M2-022

(TOGAF9 CHAPTER 2.9)

The TOGAF Document Categorization Model REFERENCE: M2-023

(TOGAF9 CHAPTER 2.11)

How to use TOGAF with other frameworks REFERENCE: M3-011

(TOGAF9 CHAPTER 2.10)

(TOGAF9 CHAPTER 5.3)

Explain the need for the ADM process to be governed

(TOGAF9 CHAPTER 5.4)

(TOGAF9 CHAPTER 5.5)

(TOGAF9 CHAPTER 5.5)

(TOGAF9 CHAPTER 5.6)

(TOGAF9 CHAPTER 2.4)

(TOGAF9 CHAPTER 5.2)

Describe a typical set of steps, such as those for Phase D

(TOGAF9 CHAPTER 5.2)

(TOGAF9 CHAPTER 5.2)

(TOGAF9 CHAPTER 2.4)

Describe the objectives of the Preliminary Phase REFERENCE: F6-005, F6-006

(TOGAF9 CHAPTER 6 SECTION 1)

(TOGAF9 CHAPTER 6 SECTION 2):

Describe the main objectives of Phase A REFERENCE: F6-009

(TOGAF9 CHAPTER 7 SECTION 1)

(TOGAF9 CHAPTER 7 SECTION 2):

Describe the main objectives of Phase B REFERENCE: F6-017 - F6-018

(TOGAF9 CHAPTER 8 SECTION 1)

(TOGAF9 CHAPTER 8 SECTION 2):

Describe the main objectives of Phase C REFERENCE: F6-024

(TOGAF9 CHAPTER 9, 10, 11 SECTION 1)

REFERENCE: F6-027 F6-028

Describe the main objectives of Phase D REFERENCE: F6-032

(TOGAF9 CHAPTER 12 SECTION 1)

(TOGAF9 CHAPTER 12 SECTION 2)

Describe the main objectives of Phase E REFERENCE: F6-035