A guide for enterprise-specific design of EA models

Transcription

1 A guide for enterprise-specific design of EA models Master s Thesis Markus Bauer Kickoff Presentation sebis Advanced Seminar

2 Set-Up Organizational issues Title Supervisor Advisors A guide for enterprise-specific design of EA models Ein Leitfaden zur unternehmensspezifischen Ausgestaltung von EA Modellen Prof. Dr. Florian Matthes Dr. Sabine Buckl (iteratec GmbH) Sascha Roth (sebis) Dr. Christian M. Schweda (iteratec GmbH) Start Deadline Industry partner Iteratec GmbH (Unterhaching) 2

3 Iteratec GmbH Industry Partner l Founded in1996 l Located in Munich, Frankfurt, Hamburg, Stuttgart, Vienna and Zurich l ~190 employees l Focus areas è Realization of IT-Projects è Technology-Consulting è IT-Management-Consulting (EAM introduction and consulting projects) l Best Practice EAM l iteraplan 3

4 Content l Set-Up & Context l Problem Description l Goals l Course of action l Status 4

5 Problem EAM frameworks need to be adapted to the enterprise l EAM is enterprise specific è EAM-Goals and -Questions è Visualizations è EA model l BEAMS/EAMPC è Collection of EAM concerns è Link to I- and V-Building-Blocks allows composition of enterprise specific EA-Models l Best-Practice-EAM (by Inge Hanschke) è One big EA model è Maturity-Level model è Model adaptations/selection described abstractly 5

6 Problem Implicit knowledge and consulting experience are crucial l Consulting-Knowledge is è distributed among different sources è only to a certain degree documented explicitly Need for a new Knowledge Management approach è consolidation è knowledge reuse è QS and risk management 6

7 EAM consulting Knowledge sources, used during projects Sample Visualizations Implicit Knowledge Enterprise Consultant(s) Inputs Guidance Knowledge Outputs Experience l l Result EA model EAM governance CIO Stakeholder Question Question Question EAM Books by Inge Power-Point slides Hanschke Information-Need Excel catalogues Wiki, Fileserver,... 7

8 Content l Set-Up & Context l Problem Description l Goals l Course of action l Status 8

9 Goal Deliverables and outcomes of this thesis l Conceptual model è EAM contingency factors (Maturity Level, Stakeholder, ) è Visualizations (V-Patterns) è Model Elements (I-Patterns) l Types l Relationships l Attributes l Knowledge Base with initial data è Collection of all known instances for these entities l Knowledge Management Approach è consolidation è knowledge reuse è QS and risk management 9

10 Content l Set-Up & Context l Problem Description l Goals l Course of action l Status 10

11 Project Plan Course of Action 15/5 today Source Analysis Questionaire... 11/15 Dev Survey Evaluation Conceptual Modelling Knowledge Base (initial Data) Product Vision Workshops Data Collection Describe KM Approach Writing Implementation Survey 11

12 Content l Set-Up & Context l Problem Description l Goals l Course of action l Status 12

13 Online Questionaire Goals l Confirm completeness of identified knowledge sources l Measure information/knowledge quality of sources è Provide possibility to measure success of new approach l Check hypotheses è Project documentation and knowledge reuse not standardized è Demand for explicit documentation is l Present overall l Is negatively correlated to a consultant s experience 13

14 Conceptual Model State of the art Most important entity types 14

15 Conceptual Model Next steps l Relationship Visualisierung-ModelElement l Clarify necessity of additional entity candidates è Industry sector l Products vs. services è Organization form l Divisions, internationality, structure l Customer segmentation è Semantics (e.g. TypeSemantics) è 15

16 ... any questions? 16

17 Literature [Ha12] Hanschke, I.: Enterprise Architecture Management. Einfach und Effektiv. Hanser, München [Ha13] Hanschke, I.: Strategisches Management der IT Landschaft. Hanser, München

18 Iteraplan & Best Practice EAM by Inge Hanschke Additional relationships H Hierarchy (e.g.. Process A is part of Process B) V S Usage (e.g. Tomcat Application Server usesjava Runtime Environment) Specialization (e.g. Customer_UK is a special form of Customer) N Predecessor/Successor (e.g. Version 1.2 is successor of Version 1.1) (Quelle: iteratec GmbH) 18