focus on the first of these – the specific set of deliverables – and are relatively silent about the methods to be used to generate them.
Because the TOGAF standard is a generic framework and intended to be used in a wide variety of environments, it provides a flexible and extensible content framework that underpins a set of generic architecture deliverables. As a result, the TOGAF framework may be used either in its own right, with the generic deliverables that it describes; or these deliverables may be replaced or extended by a more specific set, defined in any other framework that the architect considers relevant.
In all cases, it is expected that the architect will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise. This architecture tailoring may include adopting elements from other architecture frameworks, or integrating TOGAF methods with other standard frameworks, such as ITIL®, CMMI®, COBIT®, PRINCE2®, PMBOK®, and MSP®. It may also include adopting elements from reference materials in the TOGAF Library, such as the IT4IT™ Reference Architecture.
As a generic framework and method for Enterprise Architecture, the TOGAF standard also complements other frameworks that are aimed at specific vertical business domains, specific horizontal technology areas (such as security or manageability), or specific application areas (such as e-commerce).
2.7 Summary
This chapter has introduced the basic concepts of Enterprise Architecture and the TOGAF standard.
The TOGAF standard is an architecture framework. It enables you to design, evaluate, and build the right architecture for your organization. An architecture framework can be considered a “toolkit” that can be used for developing a broad range of different architectures. The value of a framework is that it provides a practical starting point for an architecture project. The TOGAF framework is designed to be adapted and used with other frameworks, when appropriate.
The TOGAF Library is a reference library containing guidelines, templates, patterns, and other forms of reference material to accelerate the creation of new architectures for the enterprise.
2.8 Test Yourself Questions
There are no questions for this chapter as this topic is not examinable.
2.9 Recommended Reading
The following are recommended sources of further information for this chapter:
• The Open Group White Paper: Why Does Enterprise Architecture Matter?
• The TOGAF Standard, Version 9.2, Part I: Introduction: Introduction and Core Concepts
4 The TOGAF Library is available online at www.opengroup.org/togaf-library.
5 The full set of TOGAF Series Guides is available in a single download at www.opengroup.org/library/t180.
3.1 Key Learning Points
This chapter will help you understand the key terminology for the TOGAF Business Architecture credential.
Key Points Explained
This chapter will help you to answer the following questions:
• What are the key terms for the TOGAF Business Architecture credential?
The key terms listed and defined here are used in the rest of this Study Guide. Please refer to this chapter when a term is used in other chapters and you need more information on its meaning.
3.2 Key Terms
Architecture
1. The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.
2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time
[Source: The TOGAF Standard, Version 9.2]
Architecture Development Method (ADM)
The core of the TOGAF framework. A multi-phase, iterative approach to develop and use an Enterprise Architecture to shape and govern business transformation and implementation projects.
[Source: The TOGAF Standard, Version 9.2]
Architecture Domain
The architectural area being considered. The TOGAF framework has four primary architecture domains: Business, Data, Application, and Technology. Other domains may also be considered (e.g., Security).
[Source: The TOGAF Standard, Version 9.2]
Architecture Framework
A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.
[Source: The TOGAF Standard, Version 9.2]
Architecture Vision
A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.
[Source: The TOGAF Standard, Version 9.2]
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.
[Source: The TOGAF Standard, Version 9.2]
Business Architecture
A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.
[Source:
