Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
Software Engineering für betriebliche Informationssysteme (sebis) Fakultät für InformatikTechnische Universität München
wwwmatthes.in.tum.de
Quantitative Models in Enterprise Architecture Management29.06.2016, Prof. Dr. Florian Matthes
1. Quantitative Models in Enterprise Architecture Management
Outline
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 2
Usage Scenarios for Quantitative Models in the Domain of Enterprise Architecture Management
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 3
System Structure (Static)
EA EA
change
EA
EA
EAchange
cons
train
s
𝒕 −𝟏 t = 𝑵𝑶𝑾 𝒕 +𝟏
System Behavior (Dynamic)
cons
train
s
cons
train
s
Identified usage scenarios
1 2
3
Performance 4 Performance Performance1. Assess the Architecture with Metrics
2. Measure architecture changes
3. Plan architecture changes
4. Monitor system performance with KPIs
The usage of metrics is related to several risks and problems
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 4
Defective data Metrics are not properly defined Irrelevant metrics
Missing automation of the measurement process
Metrics are too abstract
Top five risks ranking by the experts
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 5
Application continuity plan availability
1. Title
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 6
Application continuity plan availability
1. Title
Completeness measure of assigned and tested IT continuity plans for critical business applications.
2. Summary
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 7
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. Goals
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 8
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 9
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 10
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. Layers
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 11
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. Layers 7. Information Model
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 12
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. LayersEAM-KPI-0001
8. Code7. Information Model
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 13
General part (GP) is independent from a particular organization
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. LayersEAM-KPI-0001
8. Code7. Information Model
Organization-specific part (OSP) describes the configuration of the metric in a specific organization.
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 14
General part (GP) is independent from a particular organization
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. LayersEAM-KPI-0001
8. Code
Organization-specific part (OSP) describes the configuration of the metric in a specific organization.9. Mapping
Name in model – Business application, isCritical, IT Continuity Plan, isTested, covered by.
Mapped name – Application, criticality, Disaster plan, tested, covers
Data owner – J. Doe, J. Doe, R. Miles, R. Miles, R. Miles
Data Source – EA rep., EA rep., Risk Mgmt. rep., Risk Mgmt. rep., Risk Mgmt. rep.
7. Information Model
Metric Management Fact Sheet Example
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 15
General part (GP) is independent from a particular organization
Application continuity plan availability
1. TitleCompleteness measure of assigned and tested IT continuity plans for critical business applications.
2. SummaryImprove capability provisionIncrease disaster tolerance
3. GoalsThe number of critical applications where tested IT continuity plan available divided by the total number of critical applications.
4. Calculation
CobiT 4.0
5. Source 6. LayersEAM-KPI-0001
8. Code
Organization-specific part (OSP) describes the configuration of the metric in a specific organization.9. Mapping
Name in model – Business application, isCritical, IT Continuity Plan, isTested, covered by.
Mapped name – Application, criticality, Disaster plan, tested, covers
Data owner – J. Doe, J. Doe, R. Miles, R. Miles, R. Miles
Data Source – EA rep., EA rep., Risk Mgmt. rep., Risk Mgmt. rep., Risk Mgmt. rep.
10. Properties
Owner – J. Smith (CIO) Target value – 85% after 01.01.2015
Responsible – J. Doe (Risk Manager)
Measurement frequency – yearly
Interpretation – good if > 80%, normal if between 60% - 80%, bad if < 60%
Planned value(s) – 5% on 31.12.12, 25% on 31.12.2013, 75% on 31.06.14
Tolerance value(s) – 5%
Escalation rule – report directly to Mr. Leo Mueller
7. Information Model
EAM KPI Overview
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 16
§ Contains ten structure elements based on suggestions from literature in the fields of EAM, IT and economics and observations in industry [Ma12e]
§ General structure elements support benchmarking
§ Supports the alignment of measurement and goals
§ Organization-specific structure elements enable actionable KPIs
§ Helps to identify required data and relevant stakeholders in the specific enterprise context
§ Supports organization-specific instantiation of relevant KPI properties
§ Supports multiple instantiation of the same KPI
Metric Management Method (MMM) as Extension of the BEAMS Conceptual Framework
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 17
Stakeholders
Goals + Concerns
Organizational context
Organizational context
Organizational Context
ActorsEnterprise Architects Enterprise Architects
Development method
Characterize situation Configure EAM function Analyze EAM function
Adapt and evolve EAM function
Execute EAM
function
Implementation Guide(Patterns & Building Blocks)
BEAMS , EAM Pattern Catalog and EAM KPI Catalog
EA Metric
VBB
Performance Indicator
VBB VBB
IBB
EA Metric
IBBIBB
+ EAM Metric Catalog
Overview: Integrated Information Model
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 18
Stra
tegi
es &
Pro
ject
s
Prin
cipl
es &
Sta
ndar
ds
Business Capabilities
Business Services
Infrastructure Services
Visi
ons
& G
oals
Que
stio
ns &
KPI
s
Organization & Processes
Application & Information
Infrastructure & Data
Requirements for a calculation engine§ Analysis capability for linked data, e.g. networks and tree structures§ Batch and/or ad-hoc calculations§ Definition of metrics at runtime§ Model independence§ Resistant to model changes§ Reusable results, e.g. for visualizations§ Parameterized metric definitions
Prototype used for metric calculation @ sebis§ Model-based Wiki system with calculation engine (Tricia & TxL)§ Current issues:
§ Improvable performance for large calculations
§ REST interface for metric result export
Tool support for complexity metrics calculation
© sebis160629 Matthes Quantitative Models in Enterprise Architecture Management 19
CALM3
Technische Universität MünchenDepartment of InformaticsChair of Software Engineering for Business Information Systems
Boltzmannstraße 385748 Garching bei München
Tel +49.89.289.Fax +49.89.289.17136
wwwmatthes.in.tum.de
Florian MatthesProf.Dr.rer.nat.
17132
Thank you for your attention. Questions?