design science evaluation for enterprise architecture business value assessments by martin meyer and...
DESCRIPTION
TRANSCRIPT
Design Science Evaluation for Enterprise Architecture Business Value Assessments
Martin Meyer, Markus Helfert
BSC 2013Riga
© Business Informatics Group 2013
Agenda
• Motivation and Research Question• Enterprise Architecture Business Value
Assessments• Design Science Research (DSR)
– Focus on Evaluation– MAID
• Further Research• Summary and Conclusion• Discussion
2
© Business Informatics Group 2013
Motivation and Research Question
• Enterprise Architecture Business Value (EABV) not entirely understood
• EABV assessment methods need to be evaluated
• Design Science Research (DSR) evaluation methods not detailed enough
How can we best evaluate an EABV assessment approach in a DSR context?
3
© Business Informatics Group 2013
EABV Assessments - Overview
4
© Business Informatics Group 2013
DSR – IS Research Framework
Adapted from Hevner et al. (2004)5
© Business Informatics Group 2013
DSR – Research Process – Artifact Build Cycle
6
© Business Informatics Group 2013
DSR – Evaluation Phase
• Evaluation– Demonstrate
Artifact
– Evaluate Artifact
Preliminary Results
Evaluation Report
7
© Business Informatics Group 2013
EABV Assessment - Artifacts
8
• IT Artifacts to solve problems and satisfy business needs– EABV Assessment Method (EABV AM)
• EABV Framework (EABV FW)• EA Balanced Scorecard (EA BSC) (based on
Kaplan et al. 1996)• EABV Measurement Process (EABV MP)
(based on ISO/IEC 2007)• EABV Model (EABV M)
© Business Informatics Group 2013
Measurement And Infrastructure Diagnostic (MAID)
• Categories for Criteria– M & A planning– Data collection and storage– Data analysis– M & A reporting
9
© Business Informatics Group 2013
MAID – Example Criteria
10
© Business Informatics Group 2013
Future Research – Case Study
• Continue evaluation in organizational context– Over several periods– Facilitate benchmarking capabilities
• Evolve artifacts– Improve integration, and thereby automation– Adapt to changing business function– Artifact versioning
11
© Business Informatics Group 2013
Summary and Conclusion
• Provided a flexible research process cycle– Clear defined phases, sub phases, and deliverables– Clear roles and responsibilities– Foundation for artifact evolvement– Suitable method for DSR evaluation
• Huge benefit for project management and collaboration– Flexible adaption to changing environment– Phases allow for milestones including deliverables– Easier to collaborate due to common understanding of
research process– Adequate evaluation method for application in
organizational context12
© Business Informatics Group 2013
Discussion
13