TOGAF is an architecture framework - The Open Group Architecture Framework. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.
What is architecture according to ISO/IEC 42010:2007?
Architecture is the fundamental organization of a system, embodied in its components, their relationships to each other and the environment and the principles governing its design and evolution
In TOGAF, architecture has two meanings, depending on the context. Which meanings?
- A formal description of a system or detailed plan of the system at component level to guide its implementation - The structure of components, their inter-relationship, and the principles and guidelines governing their design and evolution over time
What are the four architecture domains?
The Business Architecture, The Data Architecture, The Application Architecture, The Technology Architecture
What is described in the Business Architecture?
The Business Architecture defines the business strategy, governance, organization, and key business processes.
What is described in the The Data Architecture?
The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources.
What is described in the The Application Architecture?
The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
What is described in the The Technology Architecture?
The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.
The Preliminary Phase describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles.
Describe Phase A: Architecture Vision
Phase A: Architecture Vision describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
Describe Phase B: Business Architecture
Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.
Describe Phase C: Information Systems Architectures
Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
Describe Phase D: Technology Architecture
Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.
Describe Phase E: Opportunities & Solutions
Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.
Describe Phase F: Migration Planning
Phase F: Migration Planning addresses the formulation of a set of detailed sequence of transition architectures with a supporting Implementation and Migration Plan.
Describe Phase G: Implementation Governance
Phase G: Implementation Governance provides an architectural oversight of the implementation.
Describe Phase H: Architecture Change Management
Phase H: Architecture Change Management establishes procedures for managing change to the new architecture.
Describe Requirements Management
Requirements Management examines the process of managing architecture requirements throughout the ADM
The Architecture Content Framework uses the following three categories to describe the type of architectural work product within the context of use
A deliverable, an artifact and a building block
Describe a deliverable
A deliverable is a 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.
Describe an artifact
An artifact is a more granular architectural work product that describes an architecture from a specific viewpoint. Examples include a network diagram, a server specification, a use-case specification, a list of architectural requirements, and a business interaction matrix. Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things). An architectural deliverable may contain many artifacts and artifacts will form the content of the Architecture Repository.
Describe a building block
A 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".
What kind of building blocks are there?
Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs)
Describe Architecture Building Blocks (ABBs)
Architecture Building Blocks (ABBs) typically describe required capability and shape the specification of Solution Building Blocks (SBBs). For example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software.
Describe Solution Building Blocks (SBBs)
Solution Building Blocks (SBBs) represent components that will be used to implement the required capability. For example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise.
Describe the Relationships between Deliverables, Artifacts, and Building Blocks (image)
Describe the Architecture Definition Document (image)
What is the Enterprise Continuum?
The Enterprise Continuum sets the broader context for an architect and explains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization. The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.
Describe the Enterprise Continuum (image)
What is an Architecture Repository?
An Architecture Repository can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, TOGAF facilitates understanding and co-operation between stakeholders and practitioners at different levels. It supports the Enterprise Continuum
Describe the Architecture Repository (image)
How many main components are there in the Architecture Repository?
What are the main components of the Architecture Repository?
- The Architecture Metamodel - The Architecture Capability - The Architecture Landscape - The Standards Information Base (SIB) - The Reference Library - The Governance Log
Describe The Architecture Metamodel
The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content.
Describe The Architecture Capability
The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository.
Describe The Architecture Landscape
The Architecture Landscape shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives.
Describe The Standards Information Base (SIB)
The Standards Information Base (SIB) captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.
Describe The Reference Library
The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise.
Describe The Governance Log
The Governance Log provides a record of governance activity across the enterprise.
Describe the Architecture Capability (image)
What are the benefits of architecture governance?
- Increased transparency of accountability, and informed delegation of authority - Controlled risk management - Protection of the existing asset base through maximizing re-use of existing architectural components - Proactive control, monitoring, and management mechanisms - Process, concept, and component re-use across all organizational business units - Value creation through monitoring, measuring, evaluation, and feedback - Increased visibility supporting internal processes and external parties' requirements; in particular, increased visibility of decision-making at lower levels ensures oversight at an appropriate level within the enterprise of decisions that may have far-reaching strategic consequences for the organization - Greater shareholder value; in particular, enterprise architecture increasingly represents the core intellectual property of the enterprise - studies have demonstrated a correlation between increased shareholder value and well-governed enterprises - Integrates with existing processes and methodologies and complements functionality by adding control capabilities
Pages linking here (main versions and versions by same user)