Architecture Board

Architecture Review Coordinator

CIO

Lead Enterprise Architect

Project Leader

Building blocks at a functional level are known as Solutions Building Blocks

Solutions Building Blocks are selected in Phases A, B, C and D

The specification of a building block should be loosely coupled to its implementation

The gap analysis technique should be used to identify building blocks for re-use

To guide decision making throughput the enterprise

To catch errors in a project architecture early

To identify and understand requirements

To identify risk when implementing an architecture project

To highlight shortfalls between the baseline and target architectures

Develop a vision of the proposed enterprise architecture

Document the baseline architecture

Obtain approval for the Statement of Architecture Work

Operate the governance framework

Select and implement tools

Application Architecture should be developed first, then Data Architecture

Application Architecture should be developed concurrently with Data Architecture

Data Architecture should be developed first, then Application Architecture

Application Architecture and Data Architecture may be developed in either sequence

To determine service levels for the architecture

To establish quality metrics for the architecture

To identify commercial building blocks to be purchased

To identify missing functionality

To validate nonfunctional requirements

To act as a deliverable container for artifacts created during a project

To ensure that architecture information is communicated to the right stakeholders at the right time

To govern the architecture throughout its implementation process

To provide a high-level view of the end architecture product

To show progression of change from the Baseline Architecture to the Target Architecture

An implementation specific solution building block

A work product describing an aspect of an architecture

A detailed description of the interfaces between building blocks

A package of functionality defined to meet the business needs of the organization.

A way to identify combinations of building blocks that have been proven to deliver solutions

is used to store different classes of architectural output created by the ADM

is a categorization mechanism for classifying architecture and solution artifacts

is a detailed model of architectural work products, including deliverables and artifacts

is an architecture of generic functions and services

is a set of resources to help establish an architecture capability within an organization

Implications

Name

Rationale

Statement

To allocate the resources needed to implement the architecture project

To define the framework that is going to be used to develop the enterprise architecture

To define an IT Strategy that maps out the technology infrastructure

To prepare a Solution Architecture for the enterprise

To secure formal approval to proceed

Develop a vision of the proposed Enterprise Architecture

Define the process for architecture governance

Create the initial version of the Architecture Roadmap

Document the baseline architecture

Obtain approval for the Statement of Architecture Work

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Gap Analysis

ADM Guidelines and Techniques

Architecture Capability Framework

Architecture Development Method

Enterprise Continuum & Tools

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Interview the project principals to obtain background information

Prepare the Architecture Compliance Review report

Schedule the Architecture Review meeting

Send the assessment report to the Architecture Review coordinator

Tailor the checklists to address business requirements

It contains an assessment of the current architecture requirements

It defines the scope and approach to complete an architecture project

It is sent from the sponsor and triggers the start of an architecture development cycle

It provides a high-level aspirational view of the end architecture project

It provides a schedule for implementation of the target architecture

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Quality Function Deployment

Application

Capability

Segment

Transition

Vision

Architecture Capability

Architecture Continuum

Architecture Landscape

Architecture Metamodel

Architecture Repository

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Enabling the vision of an integrated information infrastructure

Getting information to the right people at the right time in a secure, reliable and timely manner

Enabling effective global communications between countries

Enabling the flow of information to all stakeholders

Providing a visual representation of information provider, consumer and brokering applications

A description of individual change increments showing progression from the baseline to target architecture

A detailed schedule for implementation of the target architecture

A high level description of the baseline and target architectures

A joint agreement between the development team and sponsor on the deliverables and quality of an architecture

A set of rules and guidelines to support fulfilling the mission of the organization

It contains only solution building blocks

It contains business functions and processes specific to a particular industry sector

It contains building blocks and their corresponding standards

It includes a model of application components and application services software, including brokering applications

It includes models for common high-level business functions, such as supply chain management

Architecture Maturity Models

Business Scenarios

Gap Analysis

Mind Maps

SWOT Analysis

Preliminary Phase

Phase A

Phase B

Phase H

Requirements Management Phase

A checklist for compliance reviews

An evaluation tool to select vendors to conduct a proof of concept demonstration

A tool for calculating detailed cost estimates

A tool for project planning the implementation activities ActualTests.com

A tool for selling the benefits of the proposed capability to stakeholders

Business requirements

Cultural aspirations

Forecast financial requirements

Strategic Intent

Technical elegance

A business planning technique that focuses on business outcomes

A business planning technique that focuses on horizontal capabilities

A business planning technique that focuses on vertical capabilities

A human resource planning technique that focuses on capable architects

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

You recommend that each project architecture activity is developed using a consistent modeling approach that is uniform across all architecture projects. Each architecture should be defined based on this fixed set of models so that all concerned parties can examine the models to ensure that their issues and concerns have been addressed.

You recommend that a special report be created for those groups that have sufficient power and level of interest. This report should summarize the key features of the architecture with respect to the particular location. Each of these reports should reflect the stakeholders1 requirements.

You recommend that a set of models be created for each project architecture that can be used to ensure that the system will be compliant with the local regulations. Stakeholders should then view the models to verify that their concerns have been properly addressed.

You recommend that a stakeholder map be developed. This will allow the architects to define groups of stakeholders that share common concerns. A set of views should be defined to address the concerns for each group of stakeholders. Architecture models should then be created for each view to address the stakeholders' concerns.

The Capability Maturity Model

The Document Categorization Model

The Integrated Infrastructure Information Model

The Organizational Model for Enterprise Architecture

The Technical Reference Model

In the next iteration of Architecture development, you would describe the Baseline Business Architecture with a Value Chain diagram and a Baseline Business Process catalog. You would describe the Baseline Data Architecture with a Data diagram. You would describe the Baseline Application Architecture with an Environment and Location diagram.

In the next iteration of Architecture development, you would describe the Target Business Architecture with an Organization/Actor catalog, a Business Service/Function catalog and Data Lifecycle diagrams. You would describe the Target Application Architecture with an Application Interaction matrix and Application Communications diagrams.

You would describe the Baseline Business Architecture with a Business Service/Function catalog, an Organization/Actor catalog and a Data Entity/Business Function matrix. You would describe the Baseline Data Architecture using a Data Entity/Data Component catalog. You would describe the Baseline Application Architecture with an Application/Function matrix.

You would describe the Target Business Architecture with a Business Service/Function catalog, and a Business Interaction matrix. You would describe the Target Data Architecture with a Data Entity/Business Function matrix and an Application/Data matrix. You would describe the Target Application Architecture with Application Communication diagrams and an Application Interaction matrix.

Part II: Architecture Development Method

Part III: ADM Guidelines and Techniques

Part IV: Architecture Content Framework

Part VI: TOGAF Reference Models

Part VII: Architecture Capability Framework

Ensure conformance requirements for the target architecture are defined

Develop the Implementation and Migration Plan

Operate the governance framework

Establish the architecture governance processes

Develop the Architecture Vision document

Addressing requirements

Disposal of resolved requirements

Generating requirements

Managing the flow of requirements

Prioritizing requirements

is an example and should be tailored to the needs of an organization

must be used "as is" for developing comprehensive architecture models

contains several industry specific frameworks

is intended to contain the Enterprise Continuum

contains only solution building blocks

ensuring consistency between sub-architectures

approving the strategic business plans proposed by individual organization units within the enterprise

enforcement of architecture compliance

identifying and approving components for reuse

providing the basis for all decision-making with regard to changes to the architecture

You propose that the target architecture is defined first by going through the architecture definition phases (B-D). This is because the initial study identified the need to change. This will ensure that the change can be defined in a structured manner and address the requirements needed to realize the vision.

You propose that the baseline Technology Architecture is defined first in order to assess current infrastructure capacity and capability. Then the focus should be on transition planning and architecture deployment. This will identify requirements to ensure that the projects are sequenced in an optimal fashion so as to realize the vision.

You propose that the target architecture is defined first followed by transition planning. This is because the vision is well understood and the strategic architecture agreed. The target first approach will ensure that the current problems and inefficiencies of the baseline architecture are not carried forward, and that the proposed solution addresses the requirements identified in the initial study.

You propose that the focus be placed on architecture definition, with emphasis on understanding the strategic change parameters. The requirements, drivers, issues and constraints for this engagement can then be identified. You would ensure that the target architecture addresses not functional requirements so as to ensure the target architecture is robust and secure.

Business Architecture

Data Architecture

Architecture Vision

Opportunities and Solutions

Technology Architecture

establish quality parameters for the architecture

identify potential missing or overlapping functions

validate nonfunctional requirements

identify commercial building blocks to be purchased

determine the required service levels for the architecture

Authoring the Architecture Definition Document

Ensuring the compliance of individual projects to the enterprise architecture

Controlling the implementation and deployment organizations

Authoring the Communications Plan for a given architecture project

Conducting Business Scenarios

Common Systems Architecture

Foundation Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Architecture Capability Framework

Architecture Continuum

Architecture Development Method

Architecture Landscape

Architecture Repository

It lists work packages on a timeline showing progress towards the Target Architecture

It contains an assessment of the current architecture requirements

It provides for effective communication of the end architecture project to the stakeholders

It forms the basis of a contractual agreement between the sponsor and the architecture organization

It is sent from the sponsor and triggers the start of an architecture development cycle