- ADM - A.

Architecture Vision Phase

Initial phase of the arquitecture Development Cycle

Defining the scope (problem e project)
Identify stakeholders e concerns
Create an Architecture Vision (Summary answer to the problem e value)
Obtain approval to proceed

Objectives:

1 - Develop a hith-level aspirational vision of the capabilities and

business value to be delivered as a result of the proposed EA
2 - Obtein approval for a statement of Architecture Works that defines
a program of works to develop and deploy the architecture outlined in the
Architecture Vision.

The phase buids consensus about the Architecture Vision with the sponsors

Approach:

- Receive a Request for Architecture Work.

- Define what is in and what is outside the scope of architecture
effort and constraints.
- Obtain, verify and understand the documented business
principles, business goals, strategic drivers and architecture principles
(preliminary phase) and ensure that existing definitions are current.
- Describe Baselineand Target Architecture for all domains (BDAT)
on a Hith-level.
- Define and document an overview of the architecture Vision in
the Statement of Architecture Work (incl. how new business capabilities will meet
business goals & strategic objectives and address stakeholders concerns.
- Use Architecture Vision to communicate the benefits of the
proposed business capability to stakeholders and decision-makers.
- Get the Statement of Architecture Work signed by the sponsoring
organization.

11 steps: (Not in 1 EXAM Practitioner)

1. Estabilish the architecture project.

This phase begins with the receipt of a "Request for Architecture
Work"
The official document triggers the start of an architecture
development cycle.

Purpose:
- High-level document that is sent from the sponsoring to
the architecture organization triggering the start of an architecture development
cycle.
- Create as output of the preliminary phase, resultsof an
approved architecture Change Request or is generated as terms of reference for
architecture work originating from migration planning.

Content:
- Organization sponsors, mission statements, bugget
information, constraints
- Business goals, strategic plans, changes in environment,
time limits, constraints
- Business system, IT system and architecture description
- Developing organization including resources
 Request for Architecture Work Document* (Live Cycle)

Preliminary => Create as the sponsoring organization as

optional output.
A. Architecture Vision => Received as the architecture
organization & use as input
B. Business Architecture => Use as input
C. Information Systems Architecture(Application) => Use as
input
D. Tecnology Architecture => Use as input
E. Opportunities and solutions => Use as input
F. Migration Planning => Generate as terms of reference for
architecture work
G. Implementation Governance => Use as input
H. Architecture Change Management => Use or generate as
result of Approved architecture change Requests

2. Identify stakeholders, concerns and business requirements (Map

stakeholders, and define the Architecture Requirements specification).

Purpose:
- Allows communication for to be carried out withing a
planned and managed process.
- Ensure Effectives communication of targeted information
to the rigth stakeholders at the right time as critical success factor for EA.

Content:
- Stakeholders (grouping by communication requirements)
- Information (needs, key messages for the vision, risks,
success factors)
- Mechanisms (meethings, newsletters, repositories)
- Timetable(stakeholders <> time <> location)

*Communications Plans Document (Live cycle)

A. Architecture Vision => Create & Show where, how and when
the Enterpise Architects will communicate with the stakeholders
B. Business Architecture => Use as input
C. Information Systems Architecture(Application) => Use as
input
D. Tecnology Architecture => Use as input
E. Opportunities and solutions => Use as input
F. Migration Planning => Use as input

*Business Scenario Document

- Derive the caracteristics of the architecture from the

hith-level requirements of the business to achieve desired business outcomes
- Consider business value, outcomes & Value Streams and the
required resources to understand the requirements in any industry (healthcare,
transformation, oil)
- Can be applied to very large general problems
areas(standards for national lotteries) and very small focused problem areas
(retail point of sale upgrades)

Key elemnets:
- Real business problems
 - Business and technology enviromment in which the
problem occurs
- Desired outcomes of proper execution
- Human actors who provide the capabilities
- Computer actors who support the capabilities

A good Business Scenario contains S.M.A.R.T. outcomes

S => Specific : by defination what needs to be

done in the business
M => Measurable : through clear metrics(must be
defined) for success
A => Actionable : by segmenting the problem and
providing the basis for determining elements & plans for the solution
R => Realistic : if the problem can be solved
withing the bounds of physical reality, time and cost constraints
T => Time-bound : with a clear statement of
when the solution opportunity expires

Each Key element is iteratively refined through

phases, steps e activities

Steps
- Plan
- Gatner Information
- Analyze/Processos
- Document
- Rewiew

1 - Problems
2 - Enviroment
3 - Outcomes
4 - Human Actors
5 - Computer Actors

SPIN

Live cycle:

Preliminary => Business requirements for establishing

an EA capability
A. Architecture Vision => Business requirements and
deriving an Architecture Vision
B. Business Architecture => Business requirements and
iteratively decomposing the Business Architecture at different levels of detail
Requirements Management => Business requirements and
provide them form all phases of ADM lifecicly

Architecture Requirements Specifications Document*

Purpose:
- Defines a set of quantitative statements that
outline what an implementation project must do to comply with the architecture
- Is a major part of an implementation contract or
contract for archive for Architecture Definition
- Acts as companion to the Architecture Definition
Document* ( = qualitative view)
 Content:
- Architecture, Interoperability & IT Service
Management requirements
- Business & Application service contracts
- Implementation guidelines, specification &
standards
- Success measures, Constraints Assumptions

The deliverable is created in Phase A and complemented

during Phase B till D
The deliverable is used in Phase G & H and populated in
Requirements Management

Architecture Requirements Repository Document

3. Confirm and elaborate business goals, business drivers and

constraints.

Business principles, Goals, Drivers Document*

Purpose:
- Describe the needs and ways of working withing the
entreprise.
- May have significant implications for the way that
architecture is developed, althugh being outside the consideration of the
architecture discipline.

Content:
- Business principles, business goals and business
drivers
- Vary considerably from one organization to the next

The concepts are clarified in Phase A and used throughout Phase B

till D

4. Evaluate capabilities (Identify the capabilities).

Capability Assessment Document*

The deliverable is creted in Phase A and used throughout

Phase B till G

Capability Levels:
Enterprise => Architectural focus areas.
IT Function => Design governance, operational governance,
skills and organization structure or style, formatily and detail for the
architecture project.
Architecture function => Architectural assets, standards
and reference models, reusable assets.
Capability gaps => Business readiness, risk to
transformtion, cultural barriers.

The deliverable is a prerequisite for a detailed architecture

definition

- Business Capability Assessment, including baseline state

assessment & future state aspiration regarding performance and realization; impacts
to the organization.
- IT Capability Assessment, including baseline & target
maturity level of change and operational processes; baseline apacity & capability;
impacts to the organizaion.
- Architecture maturity assessment, including Architecture
Governance; re-use potential; Architecture skills; landscape, standarts and
reference model definition.
- Business Transformation Readiness Assessment, including
readiness factors and particular vision; current and target readiness ratings;
readiness risks.

5. Assess readiness for business transformation(TOGAF Business

Transformation Readiness Assessment).

The technique assesses an organizaion's readiness for business

transformation

- Enterprise Architecture will entail considerable change

- Innovative and sound architecture plans could lead to
nowhere, if there is a change-averse culture and a narrowly skilled workforce.
- Need for understanding the readiness of the organizaion
to accept change, identifying the issues and then dealing with them.
- Business Transformation Readiness Assessment as a joint
effort between corporate staff(specially human resources), lines of business and IT
planners.

The ADM technique assesses an organization's readiness through

five activities

1. Determine the readiness factors that will impact the

organization
2. Present the readiness factors using maturity models
3. Assess the readiness factors, including determination of
readiness factor ratings
4. Assess the risks for each readiness factor and identify
mitigation actions
5. Work these actions into Phase E and F Implementation and
migration plan

BTEP Method => Business Transformation Enablement Program

- Canadian Government Businesss Transformation Enablement

Program (BTEP) method provides guidance on how to identify business transformation-
related issues.
- All projects conduct a transformation readiness
assessment based on defined readiness factors to uncover the business
transformation issues.
- Outcome is a deep understanding of the challengs and
opportunities with many of them translating into risks.

The deliverable is created in Phase A and used in Phase E,F and G

6. Define scope, define the four dimensions:

- Enterprise Scope(Breadth(Largura)) => considerations to

specific organizations, business units, departments, or process
- Level of Detail(Depth(profundidade))
 - Architecture Domains (BDAT)
- Time Period (abstratction level, the reusable assets can be
from the architecture repository created in previous ADM iterations or asset)

7. Confirm and elaborate Architecture Principles, including business

principles
8. Develop Architecture Vision:

(good starting point is to use business scenarios to discover and

document business requirements, stakeholders concerns, business capability,
requerements, constraints and principles, common practice is to draw a simple
solution concept diagram that illustrates concisely the major components of the
solution and how the solutions will result in benefit for the enterprise).

The early summary version of the full Architecture Definition

eases communication

Purpose:
- Contains a summary of the changes to the enterprise after
the successful deployment of the target Architecture.
- Provides a stakeholders with a formally agreed outcome
and communication basis early in the ADM Cycle.
- Servers as a basis to develop yhe Domain
Architecture(BDAT).

Content:
- Problem description (stakeholder and concerns, list of
issues/scenarios).
- Objective of the Statement of Architecture Work.
- Summary views( value chain diagram, solution concept
diagram)
- Mapped requirements and reference to draft Architecture
Definition Document*

Architecture Definition Document*:

Purpose:
- Works as deliverable container for the core
architectural artifacts created during a project and importante related information
- Qualitative view of the solution
- Span all architecture domains (BDAT)
- Examines all relevant states of the
architecture(Baseline, transition and Target)
- Aims to communicate the intent of the architects
- Acts a competition to the Architecture Requirements
Specifications(= quantitative view)

Content:
- Scope, Goals, Objectives & Constraints,
Architecture Principals, Baseline & Target Architecture, Gap analysis, impact
assessment
- Architecture Models for all domanis
- Rationale and justifications for architectural
approach
- Mapping to Architecture Repository (Architecture
Landscape, reference models, standarts, re-use assessment)
- Transaction architectures (defination, business,
data, application technology)
 The Document contains complementary artifacts representing
Architecture View on the Building Blocks.

The deliverable is created in Phase A and enriched through

Phase B, C and D
The deliverable is finalized in Phase F and used throughout
Phase G

9. Define the target Architecture value propositions and KPIs(Informe

the performance metrics and measures to be built into the enterprise architecture
to meet the business needs)

KPIs: (https://pagar.me/blog/kpis-de-
vendas/?
utm_source=google&utm_medium=cpc&utm_campaign=Performance_Max&origin=&media=google&
type=pago&campaign=14465604185&ad_group=&ad=&theme=&gad_source=1&gclid=CjwKCAjw6c63
BhAiEiwAF0EH1JTyIEwFPOvACap9MSkrSwmPtWUjc8D8fAvuBzC4TLeJkWCt1hJvfRoCwt8QAvD_BwE)

10. Identify the business transformation risk and mitigation activities

11. Develop Statement of Architecture Work; secure approval

Purpose:
- Defines scope & approch being used for an architecture
development cycle
- May form the basis for a contractual adgreement between
the supplier and consumer of architecture services.

Content:
- Title, approvals, change of scope procedures
- Architecture project request, background, descripiton,
scope, plan & schedule
- Acceptance criteria and procedures, roles,
responsabilities and deliverables
- Overview of Architecture Vision

Statement of Architecture Work Document*:

The deliverable is created in Phase A and used throughout

Phase B till H

Architecture Vision document*

The deliverable is created in Phase A and used throughout Phase B till

D.
The deliverable is refined in Phase E and used in Phase G.