TOGAF Sections 1 & 2

What are the types of TOGAF Exams?

Enterprice Architecture Part 1 Exam

Enterprise Architecture Part 2 Exam

Enterprise Architecture Combined Part 1 and 2 Exam

Business Architecture Foundation Exam

What is an “Enterprise”?

An “Enterprise” is any collection of organisations that have common goals

May contain: multiple enterprises; may include partners, suppliers, customers

Ex. Corporation vs. division of a corporation, government agency vs. single gov’t department, partnerships and alliances of businesses

True or False: An Enterprise may develop and maintain several independent Enterprise Architectures

True - Enterprise Architectures can be developed for a single entire enterprise, or multiple smaller ones broken down to components of the larger enterprise

What is the definition of “Architecture”?

The structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time.

**The components of the enterprise and their relationships

What are the (4) Architecture Domans of an Enterprise Architecture?

Business, Application, Data, Technology

The BDAT ARchitecture Domains divide an Enterprise Architecture into how many subsets?

4

Business Architecture

Data Architecture

Application Architecture

Technology Architecture

What does “Business Architecture” domain do?

Defines the business strategy, governance, organisation, and key business processes

What does the “Data Architecture” domain do?

Describes the Structure of an organisation’s conceptual, logical, and physical data assets, data management resources

What does the “Application Architecture” domain do?

Provides a blueprint for the individual applications to be deployed, their interactions and their relationships to the core business processes of the organization

What does the “Technology Architecture” do?

Describes the architecture and logical software and hardware infrastructure capabilities and standards that are required to support the deployment of business, data, and applications services

What are the domains that “IT Architecture” is comprised of?

Data Architecture

Application Architecture

Technology Architecture

What are example components of the “Business Architecture” domain?

Business capabilities

Business processes

Value streams

Information concepts

Organisation Units

What are components of “Data Architecture”?

Information Objects

Data Objects

Data management resources

What are the components of the “Application Architecture” domain?

Applications

Interfaces

Application domains

Application functions

Application services

What are the components of the “Technology Architecture” domain?

IT infrastructure

Middleware

Network elements

Technology platforms

Cloud Services Runtime environments

What are the 5 Enterptise Architecture states?

Baseline Architecture

Resting Architecture

Transition Architecture

Candidate Architecture

Target Architecture

What are the two most important states of Enterprise Architecture?

Baseline Architecture (this always exists)

Target Architecture

What is “Baseline Architecture”?

Current state architecture (used for reference for all change)

What is “Resting ARchitecture”?

The state where all the enterprise receives value if all change activity is suspended

Supporting role

What is “Candidate Architecture”?

Future state architecture that has NOT been approved by stakeholders

There may be multiple versions / options of Candidate Architecture

What is “Transition Architecture”?

Fully functional future state that partially realizes targets with a specific time and target conformance

*Used when transitions to the Target Architecture is risky, due to timing, structure, change impact, etc.

**Used for an incremental approach

What is “Target Architecture”?

Future state architecture that has been approved by stakeholders

What are the 4 dminsions to define and limit the scope of an architecture?

Enterprise Scope (breadth) - what is the full extent of the enterprise?

Level of Detail (depth) - how much architecture is “enough”?

Architecture Domains - do I need all 4 BDAT to achieve project goals, or do we only focus on some?

Time period (planning horizon) - what is achievable in the time period we have?

What is the scope of architectual activity often limited by?

people, finance, objectives, stakeholder concerns, organisational authority of the EA team

What are the (3) architecture levels?

Strategic Architecture

Segment Architecture

Capability Architecture

What is “Strategic Archiecture”?

It supports the direction setting at an EXECUTIVE level

Provides operational and change framework

Broader and less detailed than other levels

Most likely to remain valid and accurate for longer

What is “Segment Architecture”?

Segment Architecture supports direction setting and development of architecture ata PROGRAM OR PORTFOLIO level

Medium level of breadth, detail and time period

What is “Capability Architecture”?

Capability architecture supports the development of effective architecture roadmaps realizing capability increments

Most detailed and specific

Why do we do Architecture Partitioning?

To simplify the development and management of the EA

What should the Architecture Partitioning model reflect?

The enterprise’ operating model

What are the steps of Architecture Partitioning?

1. Establish several architecture partitions, providing defined boundaries, governance, and ownership

2. Apply partitioning to architecture until each architecture has one owning team

3. Each team carrying out activity within the enterprise owns one or more partitions and will execute the ADM to define, govern, and realize their architectures

What is the purpose of Architecture Abstraction Levels?

To ask structured questions about an architecture and devide into smaller problem areas easier to model and solve

Why? (contextual)

What? (conceptual)

How? (logical)

With what? (physical)

*They represent the EA from different perspectives

What are the (4) distinct Architecture Abstraction levels?

Contextual Abstraction - understand the environment (highest level)

Conceptual Abstraction - understand the problem

Logical Abstraction - Identify implementation-independent components

Physical Abstraction - Implementation of physical components (most detailed level)

What is “Contextual Abstraction”?

Understanding the environment of an enterprise and the context of architectural work

e.g., scope, motivation, drivers, scope, goals, objectives

What is “Conceptual Abstraction”?

Understand the problem

Requirements and service models

e.g., business service, application service, technology service

What is “Logical Abstraction”?

Indentify implementation-independent components to achieve the services of the conceptual abstraction

e.g., business, data, application, and technology components

What is “Physical Abstraction”?

Find alternatives for allocation and implementation of physical components to meet the logical components

e.g., what assets are we using to implement?

What is a Building Block?

A potentially reusable component that delivers architectures and solutions

• A package of functionality defined to meet the business needs across an organisation

• Has normally a type that corresponds to the Enterprise Metamodel

• Can be defined at various levels of detail

• Can lead to improvements in legacy system integration, interoperability, and flexibility in the creation of new systems and applications

How can building blocks be defined at various levels of detail?

This is dependent on the objectives of the EA and the architecture development stage

Early stage BB could be a name; later on a specification

what are the criteria for a good Building Block?

• Considers implementation and usage and evolves to exploit technology and standards

• Is reusable and replaceable and well specified

• May be assembled from and subassembly of other Building Blocks

• May interoperate with other, interdependent Building Blocks based on a published and stable interface

• Should have defined boundaries and specification which are loosely coupled with its implementation

What are ABBs?

Architecture Building Block

Architectual components

Describe the required capability

Logial or supplier-independent

*Shape the specification

e.g., Video Conferencing Services

What are SBBs?

Solution Building Blocks

Solution components

Realize the required capability

Physical or implementation-specific

*Implement the capability

e.g., specific software solutions for video conferencing like Zoom or Teams

What is TOGAF and what does it do?

Best practice framework for EA

• Used to develop any kind of architecture in any context

• Developed through collaborative efforts of the community

• Can be applied for a range of use-cases

• Describes a standard cycle of change, used to plan, develop, implement, govern, change and sustain architecture

• Describes the Building Blocks in an enterprise to deliver business services and information systems

Using TOGAF results in an EA that is…?

• Consistent

• Reflects the needs of stakeholders

• Employs best practice

• Considers current and future needs of the business

What does TOGAF do to architecture development?

Adds value, standardizes, and de-risks the development

What does TOGAF enable an organization?

Workable and economic solutions

True or False: the TOGAF framework should NOT be tailored?

False

the TOGAF generic framework should be tailored and integrated with other frameworks, processes and organization structures

Can TOGAF adopt elements from other frameworks?

Yes

True or False: TOGAF allows the replacement or extension of its deliverables by a more specific set?

True

Can TOGAF be used as a standalone framework?

Yes

It can be use standalone, or integrated with other frameworks

How many documents cover the TOGAF Fundamental Content?

6

What are the (6) documents that cover the TOGAF Fundamental Content?

• Intro and Core Concepts

• Architecture Development Method (iterative approach to developing and EA)

• ADM Techniques (collection of techniques to apply the TOGAF approach and ADM)

• Applying the ADM (guidelines for adapting the ADM)

• Architecture Content (typical architecture deliverables, how to classify, sotre and re-use them)

• Enterprise Architecture Capability and Governance (org, processes, roles, responsibilities to establish and operate the EA)

What is covered in the “Architecture Content” document of the TOGAF Fundamental docs?

Typical ARchitectural deliverables and how to classify, store, and reuse them

What type of information can you expect in the “Enterprise Architecture Capability and Governance” TOGAF Fundamental Content document?

Organisation, processes, roles and responsibilities to establish an operate EA

Can I use one of the TOGAF Fundamental 6 documents alone?

Yes - all of the docs are freestanding, but closely linked

What is the TOGAF Library?

A portfolio of additional guidance material that support practical application

What is the purpose of EA?

EA is a frameowrk for continuous change that links strategic direction and business value

• manages complexity and risks and supports change

• optimizes processes into an integrated environment that is responsive to change and supportive of the delivery of the business strategy and mission

• Provides enterprises a strategic context for the evolution and reach of digital capability

• Achieves a balance between business transformation and operational efficiencies

• Allows bus. units to innovate for business goals and competitive advantage

• Enables an integrated strategy with synergies across the enterprise

How does EA improve efficiency, innovation, and competitive advantage?

It is a method to align business and IT - it ensures IT initiatives are closely aligned with goals and needs of the business

What are key benefits for an org using EA?

• better return on existing investment and reduced risk on future investment

• More effective and efficient digital transformation and ops

• More effective strategic decision-making by execs

• More effective and efficient business operations

• Faster, simpler, and cheaper procurement

• Right balance across conflicting demands