Architecture Content FrameworkFrameworks

The content framework provides a structural model for architectural content that allows the major work products that an architect creates to be consistently defined, structured, and presented.

Purpose

A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.

An artifact is an architectural work product that describes an aspect of the architecture

A building block represents a (potentially re-usable) component

Key Items

Relationships

The content metamodel provides a definition of all the types of building blocks that may exist within an architecture, showing how these building blocks can be described and related to one another

Base is ready

Overview

Core Entities

Interactions

By Phases

Extensions

Governance Extensions Services Extensions Process Modeling Extensions Data Extensions Infrastructure Consolidation Extensions Motivation Extensions

Extended for different needs

Architectural artifacts are created in order to describe a system, solution, or state of the enterprise.

Architectural Artifacts

The choice of which particular architecture views to develop is one of the key decisions that the architect has to make.

Key decision

1. Refer to an existing library of viewpoints 2. Select the appropriate viewpoints (based on the stakeholders and

concerns that need to be covered by views) 3. Generate views of the system by using the selected viewpoints as

templates

Creating Views

Artifacts

Architecture Building Blocks Architecture Contract Architecture Definition Document Architecture Principles Architecture Repository Architecture Requirements Specification Architecture Roadmap Architecture Vision Business Principles, Business Goals, and Business Drivers Capability Assessment Change Request Communications Plan Compliance Assessment Implementation and Migration Plan Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Requirements Impact Assessment Solution Building Blocks Statement of Architecture Work Tailored Architecture Framework

Architecture Deliverables

A building block is a package of functionality defined to meet the business needs across an organization.

A building block has a type that corresponds to the TOGAF content metamodel (such as actor, business service, application, or data entity)

A building block has a defined boundary and is generally recognizable as ‘‘a thing’’ by domain experts.

Building Blocks

Architecture Building Blocks (ABBs) relate to the Architecture Continuum Capture architecture requirements; e.g., business, data, application, and

technology requirements Direct and guide the development of SBBs

ABB

Solution Building Blocks Define what products and components will implement the functionality Define the implementation Fulfill business requirements Are product or vendor-aware

SBB

An architecture need only contain building blocks that are relevant to the business problem that the architecture is attempting to address.

Building blocks may have complex relationships to one another. One building block may support multiple building blocks or may partially support a single building block (for example, the business service of ‘‘complaint handling’’ would be supported by many data entities and possibly multiple application components).

Building blocks should conform to standards relevant to their type, the principles of the enterprise, and the standards of the enterprise.

Principles