combined togaf

Enterprise

- any collection of organizations that have common goals

- either an entire enterprise, encompassing all its business activities and capabilities, information, and technology that make up the entire infrastructure and governance of the enterprise, or to one or more specific areas of interest within the enterprise.

- An enterprise may include partners, suppliers, and customers as well as internal business units. In all cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise.

examples of an enterprise

• A whole corporation or a division of a corporation

• A government agency or a single government department

• A chain of geographically distant organizations linked together by common ownership

• Groups of countries, governments, or governmental organizations (such as militaries) working together to create common or shareable deliverables or infrastructures

• Partnerships and alliances of businesses working together, such as a consortium or supply chain

Enterprise Architecture

- developed to guide effective change.

- It provides a framework for change, linked to both strategic direction and business value and a sufficient view of the organization to manage complexity, support continuous change, and manage the risk of unanticipated consequences.

- enables achievement of the right balance between business transformation and continuous operational efficiency

key benefits of enterprise architecture (5) (DBDIP)

- More effective strategic decision-making by C-Level executives and business leaders

- More effective and efficient business operations

- More effective and efficient Digital Transformation and operations

- Better return on existing investment, reduced risk for future investment

- Faster, simpler, and cheaper procurement

TOGAF Standard (definition)

TOGAF Standard is a framework for Enterprise Architecture and provides standardized approach and minimizes risks.

• made up of Fundamental Content and Series Guides

- enables you to design, evaluate, and build the right architecture for your organization

- It is a standard approach for developing, approving, using, and maintaining Enterprise Architectures. It applies to all Enterprise Architecture practices.

- It is based on an iterative process model supported by best practices and a re-usable set of existing architectural assets.

TOGAF Library

• reference library provided to accelerate the creation of new architectures for the enterprise

• made up of TOGAF Standard (fundamentals and series guides) and pocket guides, white papers, reference guides

TOGAF Standard (content and what its made up of)

TOGAF Fundamental Content and the TOGAF Series Guides

Dividing the TOGAF Standard into these separate documents, allows for different areas of specialization to be considered in detail and potentially addressed in isolation.

It also allows for individual documents to be amended without impacting the whole document set.

TOGAF Fundamental Content

universal concepts of Enterprise Architecture

- Introduction and Core Concepts

- ADM

- ADM Techniques

- Applying the ADM

- Architecture Content

- Enterprise Architecture Capability & Governance

TOGAF Series Guides

takes concepts from TOGAF Fundamental Content and makes them actionable.

proven, stable, enduring best practice

4 Architecture domains

Business

Data

Application

Technology

Business Architecture (what does it consist of)

Business Architecture- the business strategy, capabilities, governance, organization, and key business processes.

Data Architecture (what does it consist of)

Data Architecture- the structure of an organization's logical and physical data assets and data management resources.

Application Architecture (what does it consist of)

Application Architecture- a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization.

Technology Architecture (what does it consist of)

Technology Architecture- the digital architecture and the logical software and hardware infrastructure capabilities that are required to support the deployment of business, data, and application services. This includes digital services, Internet of Things (IoT), social media infrastructure, cloud services, IT infrastructure, middleware, networks, communications, processing, and standards

Architecture Abstraction

technique for dividing a problem area into smaller problem areas that are easier to model and therefore easier to solve.

Abstraction levels are layered, moving from high-level models to more detailed models

4 questions about an architecture

(that abstraction can help answer)

Why - why is the architecture needed?

What - what functionality and other requirements need to be met by the architecture?

How - how do we structure the functionality?

With what - with what assets shall we implement this structure?

4 Abstraction Levels (high level to more detailed)

1. Contextual- Understanding the environment in which an enterprise operates and the context in which architecture work is planned and executed. It answers why an enterprise undertakes architecture work, what is the scope of work, and the motivation in terms of goals, drivers, and objectives.

2. Conceptual- Decomposing the requirements to understand the problem, and what is needed to address the problem, without unduly focusing on how the architecture will be realized.

3. Logical- Identifying the kinds of business, data, application, and technology components needed to achieve the services identified in the conceptual level. It is about identifying how an architecture can be organized and structured, in an implementation-independent fashion.

4. Physical- The allocation and implementation of physical components to meet the identified logical components. It is about determining with what physical components the logical-level components can be realized.

Contextual Abstraction Level

1. Contextual- Understanding the environment in which an enterprise operates and the context in which architecture work is planned and executed. It answers why an enterprise undertakes architecture work, what is the scope of work, and the motivation in terms of goals, drivers, and objectives.

Conceptual abstraction level

2. Conceptual- Decomposing the requirements to understand the problem, and what is needed to address the problem, without unduly focusing on how the architecture will be realized.

Logical Abstraction level

3. Logical- Identifying the kinds of business, data, application, and technology components needed to achieve the services identified in the conceptual level. It is about identifying how an architecture can be organized and structured, in an implementation-independent fashion.

Physical abstraction level

4. Physical- The allocation and implementation of physical components to meet the identified logical components. It is about determining with what physical components the logical-level components can be realized.

Enterprise Continuum

provides a classification for architecture and solution artifacts, both internal and external to the Architecture Repository, as they evolve from generic Foundation Architectures to Organization-Specific Architectures

view of the repository of all the architecture assets.

It can contain Architecture Descriptions, models, building blocks, patterns, architecture viewpoints, and other artifacts - that exist both within the enterprise and in the IT industry at large, which the enterprise considers to have available for the development of architectures for the enterprise.

The Enterprise Continuum supports two general ideas which are ____ and ___

re-use where possible, especially the avoidance of re-invention, and an aid to communication

Architecture Repository

a structural framework that allows an enterprise to distinguish between different types of architectural assets that exist at different levels of abstraction in the organization

Architecture Metamodel

organizationally tailored application of an architecture framework, including a metamodel for architecture content

made up of Architecture Method and Enterprise Metamodel

Architecture Capability

defines the parameters, structures, and processes that support governance of the Architecture Repository

made up of

1. skills repository

2. architecture charter

3. organization structure

Architecture Landscape

architectural representation of assets in use, or planned, by the enterprise at particular points in time

made up of Strategic, Segment, Capability Architectures

Standards Library

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. (4 standards based on 4 domains- business, data, app, tech)

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

Governance Repository

provides a record of governance activity across the enterprise

1. decision log

2. compliance assessments

3. calendar

4. capability assessments

5. project portfolio

6. performance measurement

Architecture Requirements Repository

• provides a view of all authorized architecture requirements which have been agreed with the Architecture Board

• composed of Strategic, Segment, Capability requirements

Solutions Landscape

presents an architectural representation of the Solution Building Blocks (SBBs) supporting the Architecture Landscape which have been planned or deployed by the enterprise

Major components within Architecture Repository (8 components)

- Architecture Metamodel

- Architecture Capability

- Architecture Landscape

- Standards Library

- Reference Library

- Governance Repository

- Architecture Requirements Repository

- Solutions Landscape

TOGAF Content Framework and Enterprise Metamodel define a...

define a formal structure and also provide guidance for organizations that wish to implement their architecture within an architecture tool.

The Content Framework defines...

defines a categorization framework to be used to structure the Architecture Description, the work product used to express an architecture, and the collection of models that describe the architecture.

description of the building blocks in an enterprise used to deliver business services and information systems

The Enterprise Metamodel defines...

defines the types of entities to appear in the models that describe the enterprise, together with the relationships between these entities.

Business capability for architecture

Needed in order to carry out architectural activity effectively within an enterprise through organization structures, roles, responsibilities, skills, and processes.

Enterprise Architecture practice should establish capabilities in the following 9 areas

Financial Management

Performance Management

Service Management

Risk and Opportunity Management

Resource Management

Communications and Stakeholder Management

Supplier Management

Configuration Management

Environment Management

Enterprise Architecture Capability

Ability to develop, use, and sustain the architecture of a particular enterprise, and use the architecture to govern change.

Risk

Effect of uncertainty on objectives

Effect of uncertainty

Any deviation from what is expected - positive and negative.

The uncertainty is concerned with predicting future outcomes, given the limited amount of information available when making a decision.

Risk assessment/risk analysis- every decision is based on 4 factors

1. assessing the balance between potential opportunities and threats

2. the likelihood of beneficial outcomes versus damaging outcomes

3. the magnitude of these potential positive or negative events

4. the likelihood associated with each identified outcome.

Risk management

art and science of applying concepts of risk analysis in the decision-making process.

Striking a balance between positive and negative outcomes resulting from the realization of either opportunities or threats.

Mitigation

Ongoing effort and often the risk triggers may be outside the scope of the transformation planners (e.g., merger, acquisition) so planners must monitor the transformation context constantly.

Risks can be identified and mitigated, but it is within the governance framework that risks have to be first accepted and then managed.

2 levels of risk

1. Initial level of risk- risk prior to determining and implementing mitigating actions

2. Residual level of risk- risk after implementation of mitigation actions

Initial level of risk

risk prior to determining and implementing mitigating actions

Residual level of risk

risk after implementation of mitigation actions

Gap analysis

technique used in the ADM to validate an architecture being developed.

The premise is to highlight a shortfall between the Baseline Architecture and the Target Architecture (items that have been deliberately omitted, accidentally left out, or not yet defined)

Steps in gap analysis

1 . Draw up a matrix with all the Architecture Building Blocks (ABBs) of the Baseline Architecture on the vertical axis, and all the ABBs of the Target Architecture on the horizontal axis

2. Add to the Baseline Architecture axis a final row labeled "New", and to the Target Architecture axis a final column labeled "Eliminated"

3. Where an ABB is available in both the Baseline and Target Architectures, record this with "Included" at the intersecting cell

4. Where an ABB from the Baseline Architecture is missing in the Target Architecture, each must be reviewed.

If it was correctly eliminated, mark it as such in the appropriate "Eliminated" cell.

If it was not, you have uncovered an accidental omission in your Target Architecture that must be addressed by reinstating the ABB in the next iteration of the architecture design - mark it as such in the appropriate "Eliminated" cell.

5. Where an ABB from the Target Architecture cannot be found in the Baseline Architecture, mark it at the intersection with the "New" row as a gap that needs to be filled, either by developing or procuring the building block

6. When the exercise is complete, anything under "Eliminated" or "New" is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function.

Architecture Principles

general rules and guidelines that relate to architecture work

Application Architecture

A description of the structure and interaction of the applications that provide key business capabilities and manage the data assets.

Architecture

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

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.

Architecture Domain

The architectural area being considered. The TOGAF framework follows the tradition of dividing Enterprise Architecture into four primary architecture domains: Business, Data, Application, and Technology. Other domains (motivation, security, governance, etc.) may span those four primary domains.

Architecture Framework

A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.

Architecture Landscape

The architectural representation of assets in use, or planned, by the enterprise at particular points in time.

Architecture Model

A representation of a subject of interest.

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.

Artifact

An architectural work product that describes an aspect of the architecture.

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.

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.

Business Model

A model describing the rationale for how an organization creates, delivers, and captures value.

Capability

An ability that an organization, person, or system possesses.

Capability Architecture

An architecture that describes the abilities that an enterprise possesses.

Deliverable

An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.

Data Architecture

A description of the structure of the enterprise's major types and sources of data, logical data assets, physical data assets, and data management resources.

Digital Architecture

The inclusive architecture focused on a combination of Enterprise Architecture, data science, telecommunications and IoT, security, artificial intelligence, cognitive science, neuroscience, robotics, and social medias to deliver operational services.

Enterprise

The highest level (typically) of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.

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.

Metamodel

A model that describes the entities used in building an Architecture Description, their characteristics, and the key relationships between those entities.

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.

Requirement

A statement of need, which is unambiguous, testable or measurable, and necessary for acceptability.

Role

The usual or expected behavior of an actor, or the part somebody or something plays in a particular process or event. An actor may have a number of roles.

The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities.

Segment Architecture

A detailed, formal description of areas within an enterprise, used at the program or portfolio level to organize and align change activity.

Stakeholder

An individual, team, organization, or class thereof, having an interest in a system.

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.

Target Architecture

The description of a future state of the architecture being developed for an organization.

Technology Architecture

A description of the structure and interaction of the technology services and technology components.

Transition Architecture

A formal description of one state of the architecture at an architecturally significant point in time.

Work Package

A set of actions identified to achieve one or more objectives for the business.

Draft

documents which are under development and have not undergone any formal review and approval process

Approved

documents which have been reviewed and approved in accordance with the governance practices of the organization. Approved does not necessarily mean finalized.

Each iteration of the ADM and architecture scope must focus on 3 main things/dimensions (plus one other)

1. Breadth: what is the full extent of the enterprise, and what part of that extent will this architecting effort deal with?

2. Depth: to what level of detail should the architecting effort go?

3. Time Period: what is the time period that needs to be articulated for the Architecture Vision, and does it make sense for the same period to be covered in the detailed Architecture Description?

4. Architecture Domains: a complete Enterprise Architecture Description should contain all four architecture domains (Business, Data, Application, Technology)

Architecture Board

Making the organization act according to the principles laid down in the architecture requires a decision-making framework. TOGAF provides a set of guidelines for establishing and operating framework in the form of an Architecture Board.

Architecture Project

Key concept for governing Target Architecture development and used to direct and control the Enterprise Architecture team to address issues in the enterprise.

- An Architecture Project starts with a Request for Architecture Work.

- The primary control is Architecture Project Management using the Statement of Architecture Work. Preferences are expressed in terms of objective, priority, and specification.

Architecture Contract

used to direct and control the implementation team to work towards a specific target

Architecture Requirements Specification

used to direct and control the creativity of the implementation team

- Every Architecture Requirements Specification enables control of the implementation team.

- Design, implementation, and other change choices can be tested against the Architecture Requirements Specification.

- The implementation team is directed to create changes with intentional value-based outcomes.

- Best practice governance enables the organization to control value realization.

TOGAF Standard provides 2 key concepts to govern Implementation Projects:

1. Architecture Contract

2. Architecture Requirements Specification

3 reasons to constrain (or restrict) the scope of the architectural activity to be undertaken:

1. The organizational authority of the team producing the architecture

2. The objectives and stakeholder concerns to be addressed within the architecture

3. The availability of people, finance, and other resources

architecture partitions

Ensure architects are not working on duplicate or conflicting activities. It also requires the definition of re-use and compliance relationships between architecture partitions.

a subset of architecture resulting from dividing that architecture to facilitate its development and management

ADM Phases

Preliminary Phase

Requirements Management

Phase A: Architecture Vision

Phase B: Business Architecture

Phase C: Information Systems Architecture (Data and Application)

Phase D: Technology Architecture

Phase E: Opportunities & Solutions

Phase F: Migration Planning

Phase G: Implementation Governance

Phase H: Architecture Change Management

Phase A

Architecture Vision

Phase B

Business Architecture

Phase C

Information Systems Architecture (Data and Application)

Phase D

Technology Architecture

Phase E

Opportunities & Solutions

Phase F

Migration Planning

Phase G

Implementation Governance

Phase H

Architecture Change Management

TOGAF standard aligns with Agile development in Phase ___

Phase G (Implementation Governance), where a project is implemented.