Architecture

Artifact

Deliverable

Model

View

develop requirements for Transition Architectures that deliver business value

dispose of, address and prioritize architecture requirements

organize architecture requirements throughout the ADM cycle

review business requirements

validate requirements between ADM phases

robustness

consistency

completeness

stability

understandability

They are used to define the framework and detailed methodologies

They are used to define stakeholders and their concerns

They are used to determine the readiness factors impacting the organization

They are used to guide decision making within the enterprise

They are used to resolve and dispose of requirements

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 costs

A change driven by a requirement to reduce investment

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

Architecture governance

Corporate governance

IT governance

Technology governance

Portfolio governance

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

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

It contains an assessment of the current architecture requirements

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

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

Capability, Segment, Enterprise, Federated

Business, Data, Application, Technology

Application, Data, Information, Knowledge

Process, Organization, Strategic, Requirements

Baseline, Candidate, Transition, Target

It is used to develop requirements for Transition Architectures that deliver business value

It is used to dispose of, address and prioritize architecture requirements

It is used to establish requirements for Phase A

It is used to manage architecture requirements throughout the ADM cycle

It is used to review business requirements

Implications

Name

Rationale

Statement