an integrated approach to align an enterprise’s architecture: ea alignment framework attachment to...
TRANSCRIPT
1
An Integrated Approach to Align an Enterprise’s Architecture:
EA Alignment Framework
Attachment to
Enterprise Architecture Management Guide
Chapter 6: EA Designs
(Created on 8/12/2006 Last Updated on 3/14/2010)
2
Table of ContentsSlide #. Outline ##3. 1. Introduction#4. 2. A Generic Enterprise Management Architecture#5. 3. EA Alignment Framework: the Basics#8. 4. EA Alignment Framework: the Overall Structure#11. 5. EA Alignment Framework: Alignment Rules (examples)#12. 6. Integrity Matrix for Management Areas #18. 7. Viewing an Enterprise Architecture from Five Management
Perspectives#24. 8. Various EA Continuums#29. 9. EA Alignment Framework: Other Possible Views#32. 10. EA Alignment Framework: Architectural Optimization#33. 10.1 Architectural Quality Standards - 1#36. 10.3 Architectural Optimization Triple#38. 11.1 Summary of Alignment Dimensions for Architecture Op...#40. 12. Summary
3
1. Introduction•This attachment introduces a multi-dimensional, dynamic framework to align architectural components and achieve architectural quality and optimization.
• The key value of the EA Alignment Framework is to link designs with the end result, i.e., using the designs to improve specific managements, throughout the designing process. •The EA Alignment Framework extracts and implements strengths from multiple frameworks, such as Zachman Framework, GERAM, TOGAF, FEAF, DODAF, NGOSS, and EA Cube, to establish design integrity, to connect designs with their management purposes and outcomes, and to coordinate designs with EA information models.
4
2. A Generic Enterprise Management Architecture
Enterprise Management
Strategic Management
BusinessManagement
ResourceManagement
Risk Management
Electronic Management
Management Areas
Ma
na
ge
me
nt
Do
ma
ins
Goal & Strategy
Mgmt
Organization Mgmt
Result Mgmt
Line of Business
Mgmt
Partner Relationship
Mgmt
Customer Relationship
Mgmt
Financial Mgmt
Infrastructure Mgmt
Asset Mgmt
Security Mgmt
Business Continuity
Mgmt
Legality andCompliance
Mgmt
DigitalProcessing
Mgmt
Cyber Security
Mgmt
Technology Mgmt
Human Resource
Mgmt
Cross-area/domain Interoperation** Each area/domain obtains inputs from all other areas/domains and outputs to all other areas/domains. See the Integrity Matrix in later slides for how to achieve interoperations.
Fluctuation & Uncertainty
Mgmt
Opportunity & Innovation
Mgmt
Digital Asset Mgmt
Last updated: 2/9/2010
ElectronicInfrastructure
Mgmt
Execution and Operation Management
Process Mgmt
Project Mgmt
Communication Mgmt
Change Mgmt
Logistic Mgmt
Information Mgmt
Knowledge Mgmt
Coordination Mgmt
Service Mgmt
Rule Mgmt
5
3. EA Alignment Framework: the Basics
• Architectural components:– Element: the unique unit of things, people,
phenomena, etc., that plays a role(s) in the enterprise. Example: an organization, a policy, a product, a process. The enterprise itself is also an element that plays a role(s) in a bigger context(s).
– Module: A set of related elements that forms a self-contained portion and serves a function(s) in the architecture. Example: an information model, a solution architecture.
– Segment: A combination of elements, modules, and other segments that forms a coordination structure and supports a management domain. Example: a line-of-business architecture, a security architecture.
Representation in the EA Information Model
……………………Entity
.……………Model Entity
…………………Grouping
6
3. EA Alignment Framework: the Basics (cont.)
• Structuring materials
– Relationship: A type of connection between components.
– Interface: The point of interaction or communication between components.
– Exchange package: The content being exchanged between components. Examples: information, control, physical material, influence.
Representation in the EA Information Model
………..Relationship Entity
.…………Model Interface, Interface Entity
……Exchange Entity
7
3. EA Alignment Framework: the Basics (cont.)
• Component’s features:– Has properties.– Has levels – Has relationships.– Has states and conditions over
time.– Has a lifecycle and a life history.
• Views: A presentation of a selected set of components’ instances, with a selected portion of their properties and relationships, in a selected state and condition, to display the characteristics of the architecture in a specific context or for a specific purpose.
Representation in the EA Information Model
……………………………Descriptive Attribute
…………………………………….Level Attribute
…………………………….Relationship instance
………State Attribute, Instance Version, Saved Query Result / Snapshot
…………Life Phase Attribute, Life Event Entity
.…………………Grouping, Query, Formatting, Calculating, Diagramming, Visualizing
8
4. EA Alignment Framework: the Overall Structure
External Environment/Context
Line
of B
usin
ess
/ Ser
vice
/ M
anag
emen
t
Architectural Segments
Level of Cascading / D
ecomposition
Contextual
Conceptual
Logical
Physical
Operational
Direction of Synergization / Aggregation
Range of Summation / Synergization
Transactional*
•The Transactional Level is not in the scope of EA management. But transactional statistics comprise an important portion in an enterprise’s documentation and alignment.
9
4. EA Alignment Framework: the Overall Structure (cont.)Perspectives and Views
The architecture can be viewed from endless perspectives. Below is viewing from 6 management perspectives corresponding to the 6 enterprise management areas:
1. Strategic management perspective
2. Business management perspective
3. Resource management perspective
4. Risk management perspective
5. Electronic management perspective
6. Execution and Operation management perspective
The architecture can also be viewed over time:
- Current state of the architecture
- Target state of the architecture
- Transition states of the architecture
The architecture can be viewed from more viewpoints:
- Technology View, Operations View, Communication View, Control View, …
10
4. EA Alignment Framework: the Overall Structure (cont.) Level of Abstraction / Line of Implementation
The architecture can be decomposed into levels, segments, specialty architectures, and other components.
Level of Abstraction/Decomposition (Implementation):
1. Contextual Level: this level turns external mandates, environmental factors, and internal strengths into strategic goals and plans for the domain in focus.
2. Conceptual Level: this level decomposes strategic goals and plans into objectives and management plans.
3. Logical Level: this level translates management plans into project or implementation plans and processes.
4. Physical Level: this level implements plans and processes.
5. Operational Level: this level contains versions of configurations and manages tasks and activities.
6. Transactional Level: this level conducts individual tasks and activities.
Roles and Viewpoints
1. External Stakeholders / Owner
2. Planner
3. Designer
4. Developer
5. Implementer / Administrator
6. Transaction Operator
11
5. EA Alignment Framework: Integrity Rules for Architecture Designs (examples)
•One enterprise: Regardless how to view, segment, or decompose, the architecture is a whole for an enterprise.
•Framework independency: Architectural components should exist independent of any EA framework and can be viewed in multiple frameworks.
•Vertical and horizontal penetration and coherence:
• Every management group and its corresponding architectural components penetrate to all decomposition levels and involve all segments.
• Each Line-of-Business segment contains components from all management groups and covers all decomposition levels.
•Environment dynamics: Every component of the architecture needs to monitor the enterprise’s environment. Environmental impacts received by every component need to be addressed in the context of the enterprise.
•Synergization: Decomposition and segmenting must support synergization / aggregation to higher levels and summation to the enterprise whole.
•Enterprise optimization: Designs should motivate component owners to pursue those local optima that support enterprise optima.
•Change management: Changes to designs have to address their enterprise impacts before implementing.
12
6. An Integrity Matrix to Align among Management Areas
A Mechanism for Cross-sectional Alignment
The cross-sectional integrity matrix applies the IDEF0 concept and model to align dynamic exchanges between management areas, domains, and line of business segments, as well as each group’s exchanges with external stakeholders.
The cross-sectional integrity model implements bi-directional alignment for a cell in the Architectural Integrity Matrix. The Matrix provides a mechanism to implement the cross-sectional alignment to the entire enterprise.
13
6.1 Integrity Matrix for Management Areas
Figure ??.
External Stakeholders
Management Group
2&8 Inputs/Participating Services
3&9. Enabling Products/Services
1
2
3
4
56
4 Guidance/Requirements
5 Inputs/Participating Services
6 Enabling Products/Services
Pattern 1: Alignment with External Stakeholders and Self
7
89
1&7 Guidance/Requirements
Explanation: Based on IDEF0, a management group (either a management area or a domain) incorporates external stakeholders’ inputs as well as the outputs from the group itself into its alignment process. Each line in the diagram represents a “line of alignment” for EA management.
14
6.2 Integrity Matrix for Management Areas
Figure ??.
Row Mgmt Group
Column Mgmt Group
1 Guidance/Requirements
2 Inputs/Participating Services
3 Enabling Products/Services
1
2
3
4
56
4 Guidance/Requirements
5 Inputs/Participating Services
6 Enabling Products/Services
Pattern 2: Alignment between Two Management Groups
Explanation: A management group in the integrity matrix’ row (either a management area or a domain) incorporates the outputs from the management group in the matrix column into its alignment process.
15
6.3 Integrity Matrix for Management AreasAll Things and Every Thing should be and can be Considered
Strategic Mgmt
Business Mgmt
Resource Mgmt
Risk Mgmt Electronic
Mgmt
Execution Mgmt
Strategic Mgmt
Business Mgmt
Resource Mgmt
Risk Mgmt
Electronic Mgmt
Operation
Mgmt
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
External
Row
External
Row
External
Row
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
Row
Column
123
45
6
16
6.4 Integrity Matrix for Management AreasExplanations
• Among management area alignment: Each cell takes into account of all inputs and outputs between the row management area and the column management area.
• Area alignment with all other management areas: an entire row takes into account of all inputs and outputs from all management areas to a particular management area.
• Enterprise management alignment: The entire matrix takes into account of all inputs and outputs from all management areas to every management area.
• Domain level and segment level alignment: The matrix can be decomposed to allow drilling down. Every level can achieve alignment through this same way of taking every and all things into account for every domain and segment.
• alignment with external requirements: Each management group takes into account of inputs from external stakeholders and needs to deliver output to satisfy external stakeholders .
17
6.5 Integrity Matrix for Management AreasManagement Alignment Dimensions
1. External Alignments
2. Cross Management Alignments
1. External Alignments: First of all, each management group aligns with its external stakeholders (the diagonal cells).2. Cross Management Alignments: Each management group aligns with itself and every other management group.
Electronic Mgmt
Risk Mgmt
Resource Mgmt
Business Mgmt
Strategic Mgmt
Electronic Mgmt
Risk MgmtResource Mgmt
Business Mgmt
Strategic Mgmt
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
ExternalRow
ExternalRow
ExternalRow
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
RowColumn
123456
RowColumn
123 456
RowColumn
123456
RowColumn
123 456
RowColumn
123 456
RowColumn
123456
RowColumn
123 456
RowColumn
123 456
ExternalRow
ExternalRow
Operation Mgmt
RowColumn
123456
RowColumn
123456
RowColumn
123 456
RowColumn
123 456
Execution MgmtRow
Column123 4
56
RowColumn
123 456
RowColumn
123 456
RowColumn
123 456
ExternalRow
ExternalRow4
56
RowColumn
123 456
18
7. Viewing an Enterprise Architecture fromSix Management Perspectives
The designs of architectures need to support 6 enterprise management areas and can be viewed/evaluated from 6 perspectives. Enterprise Management
Strategic Management area
Business Management area
Resource Managementarea
Risk Managementarea
Electronic Managementarea
Enterprise Architecture Views in EA Information Base
Strategic Management Perspective
Resource Management Perspective
Risk Management Perspective
Electronic Management Perspective
supports
determines
Business Management Perspectivesupports
determines
supports
determines
supports
determines
supports
determines
Execution and OperationManagement area
Execution/Operation Mgmt Perspective
takes management perspectives
achieved through management areas
supports
determines
19
7.1 EA Alignment Framework:the Strategic Management Perspective
Environment/Context
e.g. program goals & plan
e.g. project portfolio
e.g. project goals & plans
Strategic Management Domains & architectural components (examples):•Goal management
•Goal mgmt processes•Organization management
•Org structure•Result management
•Quality mgmt•Performance mgmt structure & processes
•Opportunity management•Resources management
•Investment portfolio*•Risk management
•Risk mgmt structure*•Electronic management
•Management information systems*
Business Mgmt
Resources Mgmt
Risk Mgmt
Electronic. Mgmt
Links to other perspectives
Note: Items marked by * indicate cross-group components.
e.g. enterprise strategic plan
e.g. team and individual goals & performance plans
Operation Mgmt
20
7.2 EA Alignment Framework: the Business Management Perspective
Environment/Context
e.g. processes architecture
e.g. process’ implementations
Business Management Domains & architectural components (examples):•Line of business management
•Business plans*•Business processes
•Resources management•Supply chains*•Accounting processes*•Assets & equipment supplies*
•Partner management•Partner channels
•Customer relationship mgmt•Customer relationship types•Customer service processes
•Quality &Performance mgmt•Performance plans & processes*
•Risk management•Business continuity plan & processes*
•Electronic management•Automation & productivity tools*•Information mgmt structure*•Communication patterns*
Strategic Mgmt
Resource Mgmt
Risk Mgmt
Electronic. Mgmt
Links to other perspectives
e.g. task allocation and achievements
e.g. LoB. business plan
e.g. product line goals & plan
Operation Mgmt
21
7.3 EA Alignment Framework: the Resource Management Perspective
Environment/Context
e.g. investment projects
e.g. project financing
Resource Management Domains & architectural components (examples):•Financial management
•Financing processes and controls•Accounting processes and controls
•Assets management•Assets portfolio•Assets allocations
•Materials management•Inventory allocations•Supply chains
•Human resources mgmt•HR reservoir •HR processes
•Technology Advancement mgmt•Research•Development
•Quality &Performance mgmt•Performance plans & processes*
•Risk management•Business continuity plan*•Compliance structure & processes*
•Electronic management•Automation & productivity tools*•Information mgmt structure*•Communication patterns*
Strategic Mgmt
Business Mgmt
Risk Mgmt
Electronic. Mgmt
Links to other perspectives
e.g. activity spending controls
e.g. investment goals
e.g. investment portfolio
Operation Mgmt
22
7.4 EA Alignment Framework: the Risk Management Perspective
Environment/Context
e.g. risk mgmt goals
e.g. business continuity plan
e.g. emergency process coordination
e.g. process implementations
Risk Management Domains & architectural components (examples):•Security management•Legality& Compliance mgmt
•Compliance structure & processes
•Business continuity management•Business continuity processes
•Resources management•Emergency HR processes*•Emergency inventory, assets, & supply chains*
•Electronic management•Security architecture*•Automation tools*•Information mgmt structure*•Communication patterns*
•Quality &Performance mgmt•Performance plans & processes*
•Fluctuation & Uncertainty mgmt
Strategic Mgmt
Business Mgmt
Resource Mgmt
Electronic. Mgmt
Links to other perspectives
e.g. incidents response operations
Operation Mgmt
23
7.5 EA Alignment Framework: the Electronic Management Perspective
Environment/Context
e.g. application architecture
e.g. solution architecture
e.g. development coordination
Electronic Management Domains & architectural components (example):•Digitalization management
•Digitalization landscape•Automation & Productivity mgmt
•Application architecture•Infrastructure management
•Network architecture•Telecommunication architecture
•Cyber security management•Security architecture*
•Technology management•Technology profile•Investment portfolio*•Technical standards
•Quality &Performance mgmt•Performance plans & processes*
•Service management•Line of Service processes
Strategic Mgmt
Business Mgmt
Resource Mgmt
Risk Mgmt
Links to other perspectives
e.g. operations and services
e.g. automation goals
Operation Mgmt
24
7.6 EA Alignment Framework: the Execution & Operation Management Perspective
Environment/Context
e.g. project mgmt lifecycle
e.g. project portfolio
e.g. project plans
Execution Management Domains & architectural components (example):•Process management
•Process mgmt methodology•Service mgmt
•Service mgmt methodology•Logistic management
•Transportation plan•Project management
•Project portfolio•Material management
•Material requirements•Line of Business management
•Production architecture•Result mgmt
•Quality standards•Performance plans & processes*
Strategic Mgmt
Business Mgmt
Resource Mgmt
Risk Mgmt
Links to other perspectives
e.g. project work breakdown schedules
e.g. Management excellence goals
Electronic Mgmt
25
8. Various EA Continuums
An Enterprise’s architecture forms, and can be viewed as, various continuums:
•EA Time Continuum •EA Implementation Continuum•EA Specification Continuum
Implications: •The continuum characteristics represents the changes and connections among states and phases of architectural designs.• The continuums require EA information models to capture continuum characteristics, allow views by state or phase, and display the connections.
26
8.1 EA Continuums: View Over Time
Environment/ ContextLi
ne o
f Bus
ines
s
Contextual
Conceptual
Logical
Physical
Operational
Environment/ Context
Line
of B
usin
ess
Contextual
Conceptual
Logical
Physical
Operational
EA Mgmt & Change Path
Current State Target State
• Strategic Mgmt Perspective• Business Mgmt Perspective• Resource Mgmt Perspective• Risk Mgmt Perspective• Electronic Mgmt Perspective• Operation Mgmt Perspective
Transition States
Enterprise Architecture Time Continuum
27
8.2 EA Continuums: Decomposition of Implementation
Enterprise Overall Architecture
Segment Architecturee.g. Engine Manufacture,
Military Command
Module Architecturee.g. Accounting,
Logistics
Component Architecture
EA
Imp
lemen
tation
Co
ntin
uu
m
Lin
e o
f A
ssem
bli
ng
28
8.3 EA Continuums: Decomposition of Component
Component Lifecycle
Identification
Concept
Requirements
Preliminary Design
Detailed Design
Implementation
Operation
Decommission
Component Aspect Categories Link to EA Requirement*
User Functions
/output
DataPeople
Control
Timing
Location
Infrastructure
Sec
urity
Quality
Technology
Perform
ance
Interfaces
Resources
•A component can be singular (an element) or composite (a module, a segment, or an enterprise).•The aspect categories link the component’s characteristics to enterprise architecture requirements.•All aspect categories are considered at every phase of the component lifecycle but with different emphases and different level of details.•The ring structure reflects order of consideration from core to outer layers, with user required functions being the core, beginning point. “start with the end in mind”.
*
29
8.4 EA Continuums: Generic to Specific
World of Empiria World of Theory
Object: Enterprise architectures
InformativeDescriptive research
Descriptive Theory ofgeneric architectures
Context: People, their values, beliefs, preferences
Design Theory ofGoal-oriented architectures
NormativeGeneral Studies
Enterprise-specific architecture design
Living architecture
Implementation
Architecture development project
NormativeEnterprise-specific
studies
EASpecificationContinuum
Note: The knowledge movement between empiria and theory is a continuous circle that may start at any point.
30
9. EA Alignment Framework:Other Possible Views
An enterprise’s architecture can be viewed in more ways: •Process view •Technology view•Communication view•Control view•Compliance view•…
Implications:• The needs from analytics, design, decision support and management will drive for many views of an architecture. These views reflect a wide range of considerations that shape EA designs.• EA information models need to have the capability, flexibility and extensibility to allow many different views of architecture documentations.
31
9.1 View Example: Implementation Width and Depth
External Environment/Context
Architectural Segments
e.g. Comm. tech. direction
e.g. Comm. tech. plans
e.g. Comm. tech. projects
e.g. Comm. tech. Implemented in hardware
e.g. Comm. Tech in operations
Direction of Aggregation
Range of Summation
A View of Communication Technology Implementations** The stages of implementations at different lines of business are marked by the ovals.
32
9.2 View Example: Process Flows
External Environment/Context
Architectural Segments
A View of a Cross-Segment Operation
33
10. EA Alignment Framework:Architectural Optimization
An enterprise’s architecture should be optimized and evaluated qualitatively and quantitatively:
Implications:• The goal of EA designs is to identify the most suitable and feasible architecture for the enterprise in focus.• EA information models need to provide the ability to measure the quality and performance of an architecture.
• A qualitative evaluating system: Architectural Quality Checklist
• A quantitative measuring system: Architectural Optimization Triple
34
10.1 Architectural Quality Standards - 1• Suitability
– The pattern by which elements are interrelated or arranged fits the type and purpose of the enterprise in focus.
– The functionalities of the structure support the functions and activities of the enterprise effectively.
• Integrity– Elements have compatible interfaces and exchange media to coordinate and interact with each
other.– Elements support and supplement each other so the enterprise whole is better than the sum of
individual elements.– The structure conforms to architectural principles.
• Fosterage– The architecture enables and supports the growth and continuous improvements of the enterprise
and its elements.– The architecture encourages and utilizes opportunity seeking and innovations.
• Strength– The architecture provides sufficient support to the pursuit of the enterprise’s mission.– The structure can endure a normal range of shocks and impacts from internal or external sources.– The architecture has self-discipline and self-adjustment ability to respond to changes.
A Qualitative Evaluating System:
35
10.1 Architectural Quality Standards - 2
• Economy– The architecture optimizes enterprise-wide resource use (including time and space use) that is affected by the
architecture.– The architecture optimizes the enterprise gain that can be obtained through the support of the architecture.– The architecture minimizes the cost to maintain and improve the architecture.
• Sustainability– The architecture remains vital and capable over the life of the enterprise.– The changes designed for and implemented in the architecture can persist as intended.
• Homeostasis– The architecture has embedded-adjustment mechanisms to return to balance, equilibrium, or homeostasis timely,
efficiently, and with minimal loss and pain.
• Harmony– The architecture is acceptable by its elements.
36
Enterprise Overall Architecture
Segment Architecture Module Architecture
Component Architecture
10.2 Architectural Quality Analyses
Quality Analyses should be enabled by an EA model and information base to identify:
• function gaps and duplications• Interface/exchange mismatches• architectural principle violations• structural instability or torpidity• resources mismatches• security loopholes• implementation gaps• operation gaps• change discordance• critical weaknesses• …
37
OpportuEnterpriseCapability
Optimization
Opp
ortu
nity
Opt
imiz
atio
n
Process O
ptimization
Resources Use Optimization
External Environment/
Context
Line
of B
usin
ess
Contextual
Conceptual
Logical
Physical
Operational
Direction of A
ggregation
Range of Summation
A Quantitative Measuring System:
10.3 Architectural Optimization Triple
38
OpportuEnterpriseCapability
Optimization
Opp
ortu
nity
Opt
imiz
atio
n
Process O
ptimization
Resources Use Optimization
Optimization Analyses should be enabled by an EA model and information base:
• goal achievement scorecard• bottleneck identification and quantification• total cost summation and decomposition• inventory summation and decomposition• capability maturity indicator allocation• opportunity identification and quantification• process performance statistics• …
10.3 Architectural Optimization Triple (cont.)
39
11.1 Summary of Alignment Dimensions for Architecture Optimization
Multi-dimensional* Dynamic Alignments to Pursue Total Architecture Optimization
Start Plate**
EnterpriseManagement Group
Alignment
EnterpriseDecomposition Level
Alignment
Element
Lifecycle P
hase
Alignment
Continuum of Architecture Optimization
Strategic mgmt
Business mgmt
Resource mgmt
Risk mgmt
Electronic mgmt
Co
nte
xtu
al
Co
nce
ptu
al
Lo
gic
al
Ph
ysic
al
Op
era
tion
al
Tra
nsa
ctio
na
lIdentification
Concept
Requirements
Detailed Design
ImplementationOperation
Decommission
Element Attributes Alignment: what, why, who, how, when, where * Each dimension has sub-dimensions to align.
** Start can happen anywhere in the cube, ideally in the 2-dimension Start Plate. For example, a business transaction problem may trigger an architectural alignment process.
Legend
Arrowed lineIndicates alignmentdirections
Execution mgmt
Align with the Environment (Signals, Stimulants, Constraints and Changes)
40
11.2 Summary of Alignment DimensionsExplanation - 1
• The need for EA alignment may be triggered or recognized anywhere in the cube. Ideally, the need should be identified first somewhere on the “Start Plate”. Delaying the identification and alignment will cause more discords and cost higher for either fixing or not fixing discords.
• There are 5 dimensions of EA alignments to reach total architecture optimization.
1. Attribute dimension: Align an element with its purpose. 2. Object dimension: Align among components and management areas. 3. Decomposition dimension: Align along decision-to-implementation hierarchy. 4. Time dimension: Align along lifecycles and timelines. 5. Dynamic dimension: Align with the changing environment.
• Below is a preferred initial order of alignment. Note that all dimensions require continuous realigning within and across:
1. Element attribute designation: Identify and designate the attributes and relationships regarding “why, what, who, when, where, and how” aspects of the element.
2. Enterprise Management alignment: Identify and align all aspects across management groups.
3. Enterprise Decomposition level alignment: Identify and align all aspects down the decomposition / implementation levels.
4. Element Lifecycle alignment: Maintain and update alignments when the element moves through its lifecycle.
5. Environment interaction: Monitor and align with environmental opportunities, requirements and constraints.
41
11.2 Summary of Alignment DimensionsExplanation - 2
• Each dimension has its sub-dimensions to further align.
• The EA information base should support all these alignment types.
• Total Architectural optimization is only achieved when all aspects are aligned with all dimensions - the green, upper-right line indicates the continuum of total optimization.
• Due to psychological, managerial, financial, technical barriers as well as the constant changing environment, few element can reach and maintain the Total Optimization State. Nevertheless, reducing gaps to the Total Optimization State indicates architectural improvement. Also the gap between the actual alignment state and the total optimization state presents opportunities to improve the architecture and obtain gain.
42
12. SummaryThe EA Alignment Framework serves these purposes:
• Organizes architectural designs;• Implements architectural integrity in designs; • Links designs with the end result of improving specific and overall managements; • Incorporates architectural and design principles into EA information models; and• Identifies means to evaluate and optimize designs and architectures.