A change driven by a requirement to derive additional value from the existing investment

A change driven by a requirement to increase investment in order to create new value for
exploitation

A change driven by a requirement to reduce investment

A change driven by a requirement to re-align with the business strategy

A change driven by a requirement to simplify communication between stakeholders

It highlights areas of stakeholder concern

It highlights the impacts of change

It highlights services that are yet to be developed

It highlights services that are available

It highlights different viewpoints

Defining architecture principles

Defining relationships between management frameworks

 Defining the enterprise

Evaluating the enterprise architecture maturity

Identifying stakeholders and their concerns

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

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

In the next iteration of Architecture development, 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 Application Architecture with an
Application/Function matrix.

 In the next iteration of Architecture development, you would describe the Baseline Business
Architecture with a Baseline Business Process catalog, and an Object lifecycle catalog. You would
describe the Baseline Application Architecture with a Technology Portfolio catalog.

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

 It contains a high level description of the business strategy for the organization

It is the key document describing how the new architecture capability will meet the business
goals

It provides prerequisite knowledge for undertaking work in the other architecture domains

It mobilizes operations to support the ongoing business architecture development

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

To evangelize the architecture to the end user community

To govern the architecture through to implementation

To keep the Architecture Review Board informed of changes to the architecture

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

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