Professional Documents
Culture Documents
Day - 2 - ADM-Introduction
Day - 2 - ADM-Introduction
Day - 2 - ADM-Introduction
Part II
ADM
1
8/09/2020
The ADM
Preliminary
2.Data
G. C.
Requirements I.S
Implementation
Management Architectures
Governance 3.Application
F. D.
Migration Technology
Planning Architecture 4.Technology
E.
Opportunities
&
Solutions
2
8/09/2020
ADM
Preliminary
3
8/09/2020
The enterprise scope will determine those stakeholders who will derive most
benefit from the new or enhanced enterprise architecture.
It is important to appoint a sponsor at this stage.
The enterprise may include many organizations and the duty of the sponsor is
to ensure that all stakeholders are included in some part of the architecture
work.
4
8/09/2020
Objectives
Determine the Architecture Capability desired by the Organization:
Review the organizational context for conducting enterprise architecture
Identify and scope the elements of the enterprise organizations affected by
the Architecture Capability
Identify the established frameworks, methods, and processes that intersect
with the Architecture Capability
Establish a Capability Maturity target
Approach
Define the Enterprise
Identify key drivers and elements in the organizational context
Define the requirements for architecture work
Define the architecture principles that will inform any architecture work
Define the framework to be used
Define the relationships between management frameworks
Evaluate the enterprise architecture maturity
10
5
8/09/2020
11
12
6
8/09/2020
13
14
7
8/09/2020
15
15
Who
Developed by the Enterprise Architects
In conjunction with key stakeholders
The Enterprise CIO
Architecture Board
Other key business stakeholders
16
8
8/09/2020
17
17
Example Principle
Statement:
Enterprise operations are maintained in spite of system interruptions.
Rationale:
As system operations become more pervasive, we become more dependent on them;
therefore, we must consider the reliability of such systems throughout their design and
use. Business premises throughout the enterprise must be provided with the capability to
continue their business functions regardless of external events. Hardware failure, natural
disasters, and data corruption should not be allowed to disrupt or stop enterprise
activities. The enterprise business functions must be capable of operating on alternative
information delivery mechanisms.
Implications:
Dependency on shared system applications mandates that the risks of business
interruption must be established in advance and managed.
Management includes but is not limited to periodic reviews, testing for vulnerability
and exposure, or designing mission-critical services to ensure business function
continuity through redundant or alternative capabilities.
Recoverability, redundancy, and maintainability should be addressed at the time of
design.
Applications must be assessed for criticality and impact on the enterprise mission, in
order to determine what level of continuity is required and what corresponding
recovery plan is necessary. 18
18
9
8/09/2020
Architecture Principles
An initial output of the Preliminary Phase
A set of general rules and guidelines for the architecture being developed
TOGAF contains guidelines for developing principles and a detailed set of
generic principles
Principles are generally established in two key domains:
Enterprise principles provide a basis for decision-making throughout an enterprise
and dictate how the organization fulfills its mission
Architecture principles are a set of principles that relate to architecture work.
19
20
10
8/09/2020
21
Template
Should represent the essence of the rule and be
Name easy to remember
22
11
8/09/2020
23
Business Principles:
1. Primacy of Principles
2. Maximize Benefit to the Enterprise
3. Compliance with the Law
4. Availability at Anytime from Anywhere
5. Business Continuity
6. Citizenship
Continued…
24
12
8/09/2020
25
Management Frameworks
26
26
13
8/09/2020
27
27
Summary
Continued…
28
14
8/09/2020
Quick Quiz
Q. Which one of the following is considered during the Preliminary Phase of the
TOGAF ADM?
A. Architecture Principles
B. Gap Analysis
C. Impact Analysis
D. Statement of Architecture Work
29
Quick Quiz
30
15
8/09/2020
31
31
Class Discussion
Examine the Example Set of Architecture Principles in TOGAF Chapter 23 or
the abstract on Page 16 of the Delegate Handout in your Course Workbook
Identify one principle which you think is particularly appropriate for your
business or organisation
Provide an 1 min presentation to the class introducing and explaining your
choice. State:
32
16
8/09/2020
Exercise 5
Exercise 6
33
Architecture
Vision
34
17
8/09/2020
Objective
35
35
36
18
8/09/2020
37
37
Business Scenarios
Identifying, documenting, and ranking the problem driving
1. Problem the scenario.
Identifying the business and technical environment of the
2. Environment scenario and documenting it in scenario models.
Identifying and documenting desired objectives (the results of
3. Objectives handling the problems successfully); get "SMART“.
Specific
Identifying the human actors (participants)
4. Human Actors and their place in the business model
Measureable
Actionable
Identifying computer actors (computing elements)
5. Computer Actors and their place in the technology mode
Realistic
Identifying and documenting
&Time-bound
6. Roles Responsibilities roles, responsibilities
Checking for "fitness-for-purpose"
7. Refine and refining only if necessary
38
38
19
8/09/2020
Statement of
Architecture Work contents
Title
Roles, responsibilities and
Architecture project request and deliverables
background
Acceptance criteria and procedures
Architecture project description
Architecture project plan and
and scope
schedule
Overview of Architecture vision
Approvals
Change of scope procedures
39
40
20
8/09/2020
41
Phase A: Inputs
42
21
8/09/2020
Phase A: Outputs
(Enterprise) Capability Assessment
• Tailored Architecture Framework Architecture Vision
• Architecture principles including Draft Architecture Definition
Document
business principles
Communications Plan
Approved Statement of Architecture
Work including:
Project description and scope
Overview of Architecture Vision
Project plan and Schedule
Refined statements of business
principles, goals, and drivers
Additional content populating the
Architecture Repository
43
Architecture Vision
44
22
8/09/2020
Statement of
Architecture Work contents
Title Roles, responsibilities and
Architecture project request and deliverables
background Acceptance criteria and procedures
Architecture project description Architecture project plan and
and scope schedule
Overview of Architecture vision Approvals
Change of scope procedures
45
46
23
8/09/2020
6. Define Scope
47
Summary
Phase A is about project establishment
It initiates an iteration of the
architecture process
It sets the scope, constraints and
expectations for this iteration
It validates the business context
It performs an Enterprise Capability
assessment and conducts Stakeholder
Analysis
It creates
Statement of Architecture Work
Architecture Vision,
Draft Architecture Definition Document
Communications Plan
48
24
8/09/2020
Phase A
revisit -
49
49
Quick Quiz
Q. Complete the following sentence: Phase A Architecture Vision is
intended to do all the following except:
50
25
8/09/2020
Business
Architecture
Describes the development
of a Business Architecture to
support an agreed
Architecture Vision.
51
51
Objective
52
52
26
8/09/2020
Approach (1)
Knowledge of the Business Architecture is a prerequisite for
architecture work in the other domains (Data, Applications,
Technology)
and so is the first activity that needs to be undertaken.
53
Approach (2)
54
27
8/09/2020
55
Business Modelling
Business models should be logical extensions of the business scenarios from the
Architecture Vision, so that the architecture can be mapped from the high-level
business requirements down to the more detailed ones.
A variety of modelling tools and techniques may be employed:
Activity Models (also called Business Process Models) : describe the functions
associated with the enterprise's business activities, the data and/or information
exchanged between activities.
Use-Case Models: can describe either business processes or systems functions,
depending on the focus of the modelling effort.
Class Models : describes static information and relationships between information.
56
56
28
8/09/2020
Architecture Repository
As part of Phase B, the architecture team will need to consider what relevant
Business Architecture resources are available from the Architecture Repository.
In Particular:
Generic business models relevant to the organization's industry sector.
These are "Industry Architectures", in terms of the Enterprise Continuum.
Business models relevant to common high-level business domains.
Enterprise-specific building blocks (process components, business rules, job
descriptions, etc.).
57
57
The Governance Log provides a record of governance activity across the enterprise.
58
29
8/09/2020
59
59
Phase B Steps
1. Select reference models, viewpoints, and tools
The order of the steps should be adapted to
the situation. In particular you should
determine whether it is appropriate to do the 2. Develop Baseline Business Architecture Description
Baseline Business Architecture or Target
Business Architecture development first
3. Develop Target Business Architecture Description
60
30
8/09/2020
Phase B
Inputs
Tailored Approved Draft
Organizational Architecture Enterprise Architecture Architecture Architecture
Architecture Statement of
Model for EA principles Continuum Repository Vision Definition
Framework Architecture Document
Steps
Select Develop Develop
Perform Define Resolve Impacts Conduct Formal Finalize the Create
Reference Baseline Target
Models, Business Business Gap Candidate Across the Stakeholder Business Architecture
Roadmap Architecture Definition
Viewpoints, & Architecture Architecture Analysis Review Architecture
Components Landscape Document
Tools Description Description
Outputs
Refined and updated versions of the
Draft Architecture Definition Draft Architecture Requirements Business Architecture components
Architecture Vision phase 61
Document Specification of an Architecture Roadmap
deliverables,
61
Part III
ADM Guidelines and Techniques
62
31
8/09/2020
and
63
Business Scenarios
TOGAF defines a method for developing Business Scenarios
A “method within a method”
Documented in Part III, ADM Guidelines and Techniques
64
32
8/09/2020
65
66
33
8/09/2020
67
68
34
8/09/2020
69
SMART
Specific
defines what needs to be done to done in the business;
Measurable
has clear metrics for success;
Actionable
clearly segments the problem, and provides the basis for finding a solution;
Realistic
defines the bounds of technology capability and cost constraints;
Time-bound
gives a clear understanding of when a solution expires
70
35
8/09/2020
71
The creation of a business scenario is not solely the province of the architect
Business line management and other stakeholders for the enterprise must be
involved
It may also involve an organization’s IT vendors
Typically involvement of management is greatest in the early stages whereas
the involvement of the architect is greatest in later stages
72
36
8/09/2020
Continued
73
7 - refine
74
37
8/09/2020
75
Some Reminders
Workshop Follow up
Focus Focus
Slide of 24
76
Business Scenarios Provide Coherence and Consistency
76
38
8/09/2020
Resources
77
Summary
Business scenarios help address one of the most common issues facing
businesses
Aligning the IT with the business
Business scenarios help to identify and understand business needs
And thereby derive business requirements
They are just a technique, not the goal
They are part of the larger process of architecture development
78
39
8/09/2020
Exercise
Write a scenario describing how you would choose a new
car. Include the following in your answer:
Problem description
Detailed objectives
Views of environments and processes
Actors, their roles and responsibilities
Principles and constraints
Requirements
Next steps
79
80
40
8/09/2020
Summary
Phase B is about documenting the
fundamental organization of a
business
Embodied in its business processes
and people
Their relationships to each other
and the environment
The principles governing its design
and evolution
How the organization meets its
business goals
81
Phase B
revisit -
82
82
41
8/09/2020
Quick Quiz
Q. Choose the correct ending for the following phrase:
“Business Architecture is the first architecture activity undertaken because…”
A. It is often necessary to demonstrate the business value of the overall
architecture activity
B. It provides knowledge that is a prerequisite for undertaking architecture
work in the other domains (data, applications, technology)
C. It can be used to demonstrate the return on investment to key
stakeholders
D. It embodies the fundamental organization of a business and shows how an
organization meets its business goals
E. All of the above
83
Information
Systems
Architectures
Describes the development of
Information Systems Architectures
for an architecture project,
including the development of Data
and Application Architectures.
84
84
42
8/09/2020
It is usually necessary to
address both
• Not always the case,
depending on project scope
and constraints
May be developed in either
order, or in parallel
• Theory suggests Data
Architecture comes first
• Practical considerations
may mean that starting
with Application Systems
may be more efficient
There will need to be some
iteration to ensure consistency
85
Approach
86
43
8/09/2020
Objective
87
87
88
88
44
8/09/2020
89
90
90
45
8/09/2020
Structure: This dimension pertains to whether the enterprise has the necessary
organizational structure and the standards bodies to manage data entity aspects of the
transformation.
Management System: Here enterprises should have the necessary management system
and data-related programs to manage the governance aspects of data entities
throughout its lifecycle.
People: This dimension addresses what data-related skills and roles the enterprise
requires for the transformation. If the enterprise lacks such resources and skills, the
enterprise should consider either acquiring those critical skills or training existing
internal resources to meet the requirements through a well-defined learning program.
91
91
92
46
8/09/2020
93
93
Phase C
Draft Architecture Definition
Output
Inputs
Steps
94
47
8/09/2020
Summary
Data Application
• The Data Architecture • This phase defines the
phase defines the types kinds of applications
and sources of data necessary to process
needed to support the
the data and support
business, in a way that
can be understood by the business.
stakeholders. • The goal is to define
• The architecture team what kinds of
should consider existing applications are
relevant data models, relevant and what
such as the ARTS and those applications need
Energistics models. to do.
95
Quick Quiz
A. As computer systems
B. As logical groups of capabilities
C. As schemas
D. As data-flow diagrams
E. As UML diagrams
96
48
8/09/2020
Phase C
revisit -
97
97
Technology
Architecture
Describes the development of the
Technology Architecture for an
architecture project.
98
98
49
8/09/2020
Objectives
Develop the Target Technology Architecture that enables the logical and physical
application and data components and the Architecture Vision, addressing the Request
for Architecture Work and stakeholder concerns.
Identify candidate Architecture Roadmap components based upon gaps between the
Baseline and Target Technology Architectures
99
99
Approach
100
50
8/09/2020
Phase D: Inputs
Request for Architecture Work • Draft Architecture Definition
Document, containing:
Capability Assessment – Baseline Business Architecture
Communications Plan (detailed)
– Target Business Architecture
Organization model for enterprise (detailed)
architecture
– Baseline Data Architecture
Tailored Architecture Framework (detailed)
– Target Data Architecture (detailed)
Technology principles
– Baseline Application Architecture
Statement of Architecture Work (detailed)
Architecture Vision – Target Application Architecture
(detailed)
Architecture Repository – Baseline Technology Architecture
Draft Architecture Requirements (high-level)
Specification, including gap – Target Technology Architecture
analysis results and technical (high-level)
requirements • Business, Data, and Application
Architecture components of an
Architecture Roadmap
101
•Existing IT services as
documented in the IT repository
or IT service catalog
•TOGAF Technical Reference
Model (TRM)
•Generic technology models
relevant to the organization's
industry "vertical" sector
102
102
51
8/09/2020
Phase D Steps
1. Select reference models, viewpoints, and tools
The order of the steps should be adapted to
the situation.
2. Develop Baseline Technology Architecture
Description
103
Phase D: Outputs
Statement of Architecture Work,
updated if necessary
Validated technology principles
or new technology principles
Draft Architecture Definition
Document
Draft Architecture Requirements
Specification
Technology Architecture
components of an Architecture
Roadmap
104
52
8/09/2020
Summary
The purpose of Phase D:
Technology Architecture is to
transform application
components into a set of
technology components
105
Gap Analysis
The Gap analysis technique is widely used in the
ADM to validate an architecture that is being
developed. The basic idea is to spot gaps
between the Baseline Architecture and the
Target Architecture; that is, items that have
been deliberately omitted, accidentally left out,
or not yet defined.
106
53
8/09/2020
107
Continued…
108
54
8/09/2020
Confirm as ‘Eliminated’
Development
Procurement
109
110
55
8/09/2020
Gap Analysis
Exercise #8
111
Phase D
revisit -
112
112
56
8/09/2020
Transition Planning
Phase E
Phase F
113
Opportunities
& Solutions
Opportunities and Solutions
conducts initial implementation
planning and the identification
of delivery vehicles for the
architecture defined in the
previous phases.
114
114
57
8/09/2020
Objective
Generate the initial complete version of the Architecture Roadmap,
based upon the gap analysis and candidate Architecture Roadmap
components from Phases
Stakeholders
Capability-Based B, C, and
Planning D the ADM
and
•• Specific
DeterminePhase E capabilities
whether an targeted for completion
incremental
is a collaborative effort will berequired
approach
with stakeholders the focus
is required, and if so
of the
identify from Architecture
Transition Definition
Architectures
both the business (Phases
that will deliver based
and IT sides. B, C, and D) and, continuous business
value.• upon the identified
It should include work
both packages
those thatPhase E, projects
implement and willthose
be
conceived.
that operate the infrastructure.
To confirm
•• The the enterprise’s
capability
It should alsoincrements capability
will
include those be forfor
the drivers
responsible forundergoing
the Transition change.
strategic
Architectures (Phase E) that will structure the project
planning,
To generate andespecially
increments.
for creating
gain consensus on the
an Transition
outline Implementation and
Architectures.
Migration Strategy.
• The actual delivery will be coordinated through the
Implementation and Migration Plans (Phase F).
115
115
Approach
This is the first phase concerning implementation
It takes into account the complete set of gaps between the Target and
Baseline Architectures in all architecture domains
It logically groups changes into work packages
116
58
8/09/2020
Phase E: Inputs
Product Information Architecture Vision
Request for Architecture Architecture Repository
Work
Draft Architecture Definition
Capability Assessment Document
Communications Plan
Draft Architecture
Planning Methodologies Requirements Specification
Governance models and Change Requests for existing
frameworks programs and projects
Tailored Architecture
Framework Candidate Architecture
Roadmap components from
Statement of Architecture Phases B,C, and D
Work
117
Stakeholders
Phase E is a collaborative effort
Stakeholders required from both the business and IT sides
It should include those that implement and those that operate the
infrastructure
It should also include those responsible for strategic planning
especially for creating the Transition Architectures, if required
118
59
8/09/2020
119
60
8/09/2020
Phase E Outputs
• Statement of Architecture • Enterprise Capability
Work Assessment, including:
• Architecture Vision – Business Capability Assessment
• Draft Architecture Definition – IT Capability Assessment
Document, including: • (Outline) Architecture Roadmap,
– Transition Architectures, if including:
any – Work Package portfolio
• Draft Architecture – Identification of Transition
Requirements Specification, Architectures, if any
including – Implementation
– Consolidated Gaps, Recommendations
Solutions and Dependencies • Implementation & Migration
Assessment Plan (outline)
121
Summary
Phase E is the first phase concerned
with implementation
ABBs are chosen then converted to
SBBs
The Capability of the Enterprise to
implement and accept the new
architecture is assessed
It identifies the parameters of
change, the phases (transitions) and
necessary projects
The output forms the basis of the
Implementation Plan
122
61
8/09/2020
Phase E
revisit -
123
123
Quick Quiz
Q. Which one of the following is a successful strategy for Phase E?
A Focus on the application systems that are relevant to the enterprise
B Focus on projects that will deliver quick wins
C Focus on top-down implementation
D Reverse engineering
E Trial and error
124
62
8/09/2020
Migration
Planning
Addresses the formulation of a
set of detailed sequence of
Transition Architectures with a
supporting Implementation and
Migration Plan.
125
125
Objective
Analyze cost benefits and risk.
Develop detailed Implementation and Migration Plan.
• The focus of Phase F is the creation of an Implementation
Finalize the Architecture
and Migration Roadmap
Plan in co-operation and
with thethe supporting
portfolio and Implementation
and Migration Plan.
project managers.
• Phase E provides an incomplete Architecture Roadmap and
Ensure that the Implementation
Implementation and Migration Planand
thatMigration
address thePlan is coordinated
withRequest
the enterprise's approach
for Architecture Work. IntoPhase
managing and implementing change
F this Roadmap
in the
andenterprise's overalland
the Implementation change
Migrationportfolio.
Plan are integrated
with the enterprise's other change activity.
Ensure
• Thethat the business
Architecture value
Roadmap, and0.1
Version cost
andof work packages and
Transition Architectures
Implementation is understood
and Migration by0.1
Plan, Version keyfrom
stakeholders.
Phase E will form the basis of the final Implementation
and Migration Plan that will include portfolio and project-
level detail.
126
126
63
8/09/2020
Approach
127
Phase F: Inputs
• Request for Architecture Work • Draft Architecture Requirements
• Communications Plan Specification
• Organizational model for • Change Requests for existing
programs and projects
enterprise architecture
• Capability Assessment
• Governance Models and
• (Outline Architecture Roadmap,
Frameworks including:
• Tailored Architecture – Identification of work packages
Framework – Identification of Transition
• Statement of Architecture Work Architectures
– Implementation Factor
• Architecture Vision Assessment and Deduction
• Architecture Repository Matrix
• Draft Architecture Definition • Implementation and Migration
Document, including: Plan (outline)
– Transition Architectures, if any
128
64
8/09/2020
Phase F Steps
The order of the steps should be adapted to 1. Confirm Management Framework Interactions for
the situation. the Implementation and Migration Plan
129
Phase F Outputs
Implementation and Migration Plan
(detailed)
Finalized Architecture Definition
Document, including:
Finalized Transition Architectures, if
any
Finalized Architecture Requirements
Specification
Finalized Architecture Roadmap
Re-Usable ABBs
Requests for Architecture Work for a
new iteration of the ADM (if any)
Implementation Governance Model
Change Requests
Lessons Learned
130
65
8/09/2020
Summary
Phase F addresses migration
planning – how to move from
the Baseline to the Target
It includes creating the finalized
Architecture Definition
Document, Architecture
Roadmap and the detailed
Implementation & Migration
Plan, defining implementation
governance, and recording
lessons
At the completion of this phase
the preparation for
implementation has been
completed
131
Phase F
revisit -
132
132
66
8/09/2020
Quick Quiz
Q. When preparing the detailed Migration Plan, which of the following should
NOT be a consideration?
A Risk Assessment
B Priorities of projects
C Availability of Resources
D Cost/value assessment
E Choice of target platform
133
Governance
Phase G
Phase H
134
67
8/09/2020
Implementation
Governance
135
135
Objective
Provide architectural oversight for the implementation.
Prepare and issue Architecture Contracts (Implementation
Governance Board).
Ensure that the implementation project conforms to the
architecture.
136
136
68
8/09/2020
137
137
Approach
The overall approach in Phase G is to:
Establish an implementation program that will enable the delivery of the Transition
Architectures agreed for implementation during the Migration Planning phase.
Adopt a phased deployment schedule that reflects the business priorities embodied
in the Architecture Roadmap.
Follow the organization's standard for corporate, IT, and architecture governance.
Use the organization's established portfolio/program management approach, where
this exists.
Define an operations framework to ensure the effective long life of the deployed
solution.
138
138
69
8/09/2020
Approach
Phase G establishes the connection between architecture and implementation
organization, through the Architecture Contract.
139
139
Architecture Governance
“the practice and orientation by which enterprise architectures and other
architectures are managed and controlled at an enterprise-wide level..”
Corporate governance
Technology governance Each of these domains of governance may exist
IT governance at multiple geographic levels - global, regional,
and local - within the overall enterprise.
Architecture governance
140
140
70
8/09/2020
Implementing a system of controls over the creation and monitoring of all architectural
components and activities, to ensure the effective introduction, implementation, and
evolution of architectures within the organization.
Implementing a system to ensure compliance with internal and external standards and
regulatory obligations.
Establishing processes that support effective management of the above processes within
agreed parameters.
Developing practices that ensure accountability to a clearly identified stakeholder
community, both inside and outside the organization.
141
141
142
142
71
8/09/2020
143
143
Phase G: Inputs
144
72
8/09/2020
Phase G Steps
The order of the steps should be adapted to
the situation.
145
Phase G: Outputs
Architecture Contract (signed)
Compliance Assessments
Change Requests
Architecture-compliant solutions
deployed, including:
Implemented system
Populated Architecture Repository
Recommendations and
dispensations
Service delivery requirements
Performance metrics
SLAs
Architecture Vision
Business and IT operating models
146
73
8/09/2020
Summary
Phase G defines architecture
constraints on the
implementation projects and
constructs and obtains
signatures on an Architecture
Contract
The contract and
documentation is delivered to
the implementation team
The phase includes governing
the architecture through
implementation by compliance
reviews and by risk monitoring
147
Phase G
revisit -
148
148
74
8/09/2020
Quick Quiz
Q. Which one of the following provides a foundation for governing the
implementation of the recommended projects?
A Impact Analysis
B Principles
C Strategic Plan
D Architecture Contracts
E Risk Assessment
149
Architecture
Change
Management
Establishes procedures for
managing change to the
new architecture.
150
150
75
8/09/2020
Objective
Provide continual monitoring and a change management
process to ensure that the architecture responds to the
needs of the enterprise and maximizes the value of the
architecture to the business.
151
151
Approach
The goal of an architecture change management process is to ensure
that the architecture achieves its original target business value.
152
76
8/09/2020
• The
In Phase
goal Hofitan
is architecture
critical that the
change
governance
management body process
establishis
to ensure
criteria tothat
judge thewhether
architecture
a Change
achieves
Requestits original
warrantstarget
just
business
an architecture
value. Thisupdate
includes
or whether
managing
it warrants
changesstarting
to the a
architecture
new cycle of inthea Architecture
cohesive andDevelopment
architected way.Method (ADM).
• It
This
is especially
process will important
typicallytoprovide
avoid "creeping
for the continual
elegance",
monitoring
and the governance
of such things
body must
as governance
continue torequests,
look fornew
developments
changes that relate
in technology,
directly to
and
business
changes value.
in the business
environment.
• When changes are identified, change management will
determine whether to formally initiate a new architecture
evolution cycle.
153
153
154
154
77
8/09/2020
155
155
If the change:
Impacts 2 stakeholders or more, then it is likely to require an architecture
redesign and re-entry to the ADM
Impacts only 1 stakeholder, then it is likely to be a candidate for change
management
Can be allowed under a dispensation, then it is likely to be a candidate for
change management
156
78
8/09/2020
157
158
158
79
8/09/2020
Phase H Steps
The order of the steps should be adapted to the situation.
3. Manage Risks
159
Phase H: Outputs
Architecture updates
Changes to architecture
framework and principles
New Request for Architecture
Work, to initiate another cycle
of the ADM
Statement of Architecture Work
Architecture Contract
Compliance Assessments
160
80
8/09/2020
Summary
161
Phase H
revisit -
162
162
81
8/09/2020
Quick Quiz
Q. Which of the following is NOT part of an architecture change management
process?
A Ensuring that business continues as usual
B Determining whether a change warrants an update to the architecture
C Determining whether a change requires a new cycle of the ADM
D Managing change properly
E Establishing criteria for judging change requests
163
Handling Change
Exercise #4
164
82
8/09/2020
Requirements
Management
Examines the process of managing
architecture requirements
throughout the ADM.
165
165
Objective
Ensure that the architecture lifecycle is maintained.
Ensure that the Architecture Governance Framework is
executed.
Ensure that the enterprise Architecture Capability meets
current requirements.
Ensure that the Requirements Management process is
sustained and operates for all relevant ADM phases
166
166
83
8/09/2020
Approach
The ability to deal with changes in the requirements is crucial to the ADM
process since architecture deals with uncertainty and change
Architecture bridges the divide between the aspirations of the stakeholders
and a practical solution
The Requirements Management process does not dispose of, address or
prioritize requirements; this is done within the phases of the ADM
It is recommended that a Requirements Repository is used to record and
manage all architecture requirements
167
Requirements-related outputs
from each ADM phase.
The first high-level
requirements are produced as
part of the Architecture Vision.
Each architecture domain then
generates detailed
requirements.
Deliverables in later ADM phases
contain mappings to new types
of requirements
168
84
8/09/2020
Steps Overview
Requirements Management Steps ADM Phase Steps
1. Identify/document requirements
2. Baseline requirements
3. Monitor baseline requirements
4. Identify changed requirement
169
170
85
8/09/2020
Summary
Requirements Management is an
ongoing activity of the ADM.
The Requirements Repository
contains the current requirements
for the Target Architecture.
When new requirements arise, or
existing ones are changed, a
Requirements Impact Assessment
is performed resulting in a
Requirements Impact Statement
being generated. The Statement
identifies the phases of the ADM
to be revisited. This goes through
various iterations until a final
version is produced.
171
Requirements Management
revisit -
172
172
86
8/09/2020
Quick Quiz
173
87