john gøtze - towards next generation national enterprise architecture
DESCRIPTION
Fra DANSK IT's konference "Offentlig digitalisering 2014", 19.-20. marts 2014 i Musikhuset Aarhus. www.dit.dk http://www.dit.dk/events/2014/03/19-offentlig-digitalisering-2014.aspxTRANSCRIPT
1
Towards Next-Generation National Enterprise Architecture
John Gøtze
2
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de
Enterprise Architecture Management
Florian Matthes
Apologies
3
Coherency
Consensus Consistency
Elevator-Picture
4
Enterprise Architecture
5
National Enterprise Architecture
6
Next-Generation National Enterprise Architecture
7
Muhammad Farooq
8
9
10
Pallab Saha: Components of GEA
11 11
12
Different Countries’ Approaches
US: Performance focus and legal enforcement
NL: Clear goals, but low adoption and no measurement
Mandated Voluntary
DK: Voluntary approach, some adoption, but limited goal realization
CA: Clear framework, but no measurements and limited adoption
FI: Act on Information Management Governance in Public Administration (634/2011)
13
US Government: Performance Improvement Lifecycle
• Architect, Invest, Implement • Architecture-driven IT investments • Aim: By integrating the disciplines of architecture, investment
management, and project implementation, to provide the foundation for sound IT management practices, end-to-end governance of IT capital assets, and the alignment of IT investments with an agency’s strategic goals.
Clinger-Cohen Act, 1996
14
FEAF-II The Common Approach to Federal Enterprise Architecture
May 2, 2012
15
Common Approach to Federal EA
"The role of an enterprise architect is to help facilitate and support a common understanding of needs, help formulate recommendations to meet those needs, and facilitate the development of a plan of action that is grounded in an integrated view of not just technology planning, but the full spectrum of planning disciplines to include mission/business planning, capital planning, security planning, infrastructure planning, human capital planning, performance planning, and records planning."
16
Common Approach to Federal EA
17
Finland
Act on Information Management Governance in Public Administration (634/2011): To enable and ensure the interoperability of public administration information systems, authorities in public administration must each plan and specify their enterprise architecture and must comply with it once it has been formulated and is maintained…
18
19
Cross-Government Enterprise Architecture (xGEA)
• A fundamental element of the UK Government’s “Transformational Government - Enabled by Technology” strategy (2005).
• In that strategy the first priority of the CTO Council was – to agree and publish a standard
Enterprise Architecture reference model which would help align existing and emerging technical architectures across government with the xGEA.
20
UK
21
CHANNEL DOMAIN
INFRASTRUCTURE DOMAIN
APPLICATION DOMAIN
BUSINESS PROCESS DOMAIN
BUSINESS INFORMATION DOMAIN
STRATEGY DOMAIN
INTE
GR
ATIO
N D
OM
AIN
SEC
UR
ITY
DO
MA
IN
SERVIC
E MA
NA
GEM
ENT D
OM
AIN
UK Cross-Government EA Ref Model (xGEARM)
22
23
Kazakhstan
24 24
25
GrEAnland
26
Flying in Enterprise Architecture
27
First wave: John’s students!
28
v Top-leader seminar v Minister of Finance + department heads v Guest: Lars Frelle-Petersen v Principles
v Ilulissat seminar v Business managers in municipality
v Focus on architecture in projects v ERP-Project v OIOEA Checklist workshop, Niels Terkelsen v Project Model with EA
Second wave: Architecture Awareness
29
Third wave: Competency initiatives!
• EA foundation courses 2011/2012"• Established AEA chapter* in May 2012"• Carnegie Mellon University EA certification in Nuuk"
*: http://aeagc.gl"
Greenland is today the country with the highest percentage of EAs per capita in the world.
30
• Getting an overview of applications and services"• Senior/political management engagement"• Top level principles "• EA in Business Case Standard for ICT projects"• Establishing Digitaliseringsstyrelse!
GrEAnland!
31
Ataqatigiisitsineq: Making coherency"
Enterprise Architecture in Greenlandic: !Ataqatigiisitsineq !
Aqqutigissaarneq "Creating good ways"
32
33
Humans: Employees, Customers, Suppliers, Partners, Markets, Communities, … Laws & Regulations
Resources: Energy, Matter, Information, Technology…
Enterprise
A cybernetic view on the enterprise as a complex adaptive system of systems
Business Capabilities
Information Management
OPTIMIZE TRANSFORM
IM Capabilities
OPTIMIZE TRANSFORM
Goals, Strategy
Vision, Goals, Strategy
34
The Future of Enterprise Architecture"
• EA at a tipping point?"• ”New Normal”?"• Balkanization and Empire
Building"• AaaS …""New challenges …"The Alignment Trap!
BeyondAlignment.com"
35
Business-IT Alignment"
The degree of fit and integration among business strategy, IT strategy, business infrastructure, and IT infrastructure. Henderson and Venkatraman (1989)!
CBS Library Apr 2013:"21.199 peer-reviewed articles about “business-IT alignment”. "
(Ross, Weill and Robertson, 2006)"
36
=! 0!”Remember Your Vector Math!”!
Enterprise Alignment"
Alignment = “the ability of the organization to operate as ONE by working towards a common shared vision supported by a well orchestrated set of strategies and actions”. (Doucet et al, 2009)"
37
Get your ducks in a row! Governments of Canada Strategic Reference Model
Story Alignment
38
An enterprise architecture provides a common language for business and IT
• Common language for business and IT – Technical, social, economic and legal aspects – Layers and crosscutting concerns – Static and dynamic relationships more important than element
details
Stra
tegi
es &
Pro
ject
s
Prin
cipl
es &
S
tand
ards
Business Capabilities Organization & Processes
Business Services Applications & Databases
Infrastructure Services Infrastructure Elements
Visi
ons
& G
oals
Que
stio
ns &
KP
Is
Lega
l Asp
ects
Sec
urity
+ Evolution
39
An enterprise architecture has to be visualized to make it accessible to different stakeholders.
EAVIST 2014 and EAM Pattern Catalog
40 40
41
Architecture management has to be integrated with other management functions.
Architectural changes are performed through a coherent set of projects.
Architecture Management
Multi-Project Management
Project Portfolio Management Strategy Management
Project Lifecycle
Define Measure
Plan Measure
Prioritize & Commit
Implement Measure
Deploy & Migrate
Requirements Management
Identify Measure
Application Lifecycle Management
Innovation Management
Example of a mature IT organization
42
Federated enterprise architecture model management Modeling communities, artifacts, processes and their interactions
E
Metamodel and Model
D EAM
Task
Technology
fit
Metamodel and Model
A PPM
Task
Technology
fit
Team
publish model changes
model and meta-model changes to be
integrated
Metamodel and Model
B BPM
Task
Technology
fit
Team
publish model changes
Metamodel and Model
C ITSM
Task
Technology
fit
Team
publish model changes
publish model changes
Federated EA Model Management
Modeling Experts Modeling Community Metamodel Mappings Instance Mappings
Team
Enterprise
• Importing • Differencing • Conflict detection • Conflict resolution
• Collaboration • Negotiation
43
Agile EA management principles Individuals and interactions over formal processes and tools
IT Project 3 IT Project 2 IT Project 1
Top management
Business stakeholders
Software development
IT operations
Project managers
Software architects
Software developers
Top management
Strategy office
Business owners
Application owners
IT operations
Purchasing
EA Team
44
Agile EA management principles Focus on demands of top stakeholders and speak their languages
IT Project 3 IT Project 2 IT Project 1
Architecture blueprints
Top management
Business stakeholders
Software development
IT operations
Project managers
Software architects
Software developers
communicate
explain
involve
support
get feedback
� �
Top management
Strategy office
Visualizations Business owners
Application owners
IT operations
Purchasing
EA Team
Stakeholder-specific
architecture views Metrics
Reports
Architecture- approval and requirements
Architecture changes
model
collect
motivate
Business and IT strategy
Individual architecture aspects
Business and org. constraints
45
Agile EA management principles Reflect behavior and adapt to changes
IT Project 3 IT Project 2 IT Project 1
Architecture blueprints
Top management
Business stakeholders
Software development
IT operations
Project managers
Software architects
Software developers
�
communicate
explain
involve
support
get feedback reflect
adapt
� �
Top management
Strategy office
Visualizations Business owners
Application owners
IT operations
Purchasing
EA Team
Stakeholder-specific
architecture views Metrics
Reports
Architecture- approval and requirements
Architecture changes
model
collect
motivate
Business and IT strategy
Individual architecture aspects
Business and org. constraints
46
Usage Scenarios for Quantitative Models in the Domain of Enterprise Architecture Management
System Structure (Static)
EA EA
change
EA
EA
EA change
cons
trai
ns
𝒕−𝟏 t = 𝑵𝑶𝑾 𝒕+𝟏
System Behavior (Dynamic)
cons
trai
ns
cons
trai
ns
Identified usage scenarios
1 2
3
Performance 4 Performance
Performance
1. Assess the Architecture with Metrics
2. Measure architecture changes
3. Plan architecture changes
4. Monitor system performance with KPIs
47
Metric Catalog v1.0
§ Organized collection of 52 metrics observed in industry
§ All metrics are documented using the Metric Management Fact Sheet
§ Targeted user group of the catalog is enterprise architects and EA management stakeholders
§ Supports EA metric search by § Related EAM Goals § Related EAM Concerns
§ Download link: http://wwwmatthes.in.tum.de/wikis/sebis/eam-kpi-catalog
Details
48
The EA Program
Target Conceptual Model
Design Principles
1
Model Context
2
Business Domains & Core Services
Enabling Services & Capabilities
Unified Border Concept
3a
3c 4 Operating Model
• Design principles guide the design and future development of the target model against a set of approved criteria and statements of intention
• The model outline frames the key stakeholder groups and the dimensions of the border continuum in which the agency and capabilities reside
• The unified border management concept describes the context, ecosystem and supports Customs lead border agency role by driving optimum decision & response
• The target conceptual model illustrates the overall architectural solution at the highest level and is comprised of business domains & services layers and enterprise services & enabling capability layers
3b
Guidance, Drivers, Priorities & Implications
49
EA Trends
Enterprise Investment Chris Potts Enterprise Design Milan Guenther Business Architecture Roger Burlton
QualiWare International Conference
qualiware.com