EMMSAD Workshop, , Amsterdam

Transcription

1 Enterprise Meta Modeling Methods Combining a Stakeholder-Oriented and a Causality-Based Approach Robert Lagerström, Jan Saat, Ulrik Franke, Stephan Aier, Mathias Ekstedt EMMSAD Workshop, , Amsterdam Mathias Ekstedt Research Associate Industrial Information and Control Systems Royal Institute of Technology, Osquldas väg 12, Stockholm, Sweden Tel: Fax: mathiase@ics.kth.se Jan Saat Research Assistant Chair of Prof. Dr. Robert Winter Institute of Information Management University of St. Gallen Müller-Friedberg-Strasse 8, CH-9000 St. Gallen Tel: Fax: jan.saat@unisg.ch

2 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 2

3 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 3

4 Enterprise Architecture Modelling in Summary Slide 4

5 Arcitecture models, sure! But why? To make things easier..!? Slide 5

6 EA for Decision Making? Decision Maker Current Situation Potential Future Situations Now, make the right decision! Slide 6

7 New System! New (and Old) Management Needs IT Modifiability Interoperability Performance Cost Security Alignment Maintainability Usability Reliability Availability Scalability Transaction quality... Business Flexibility Efficiency Effectiveness Competence Product quality Interoperability Performance Security Availability Productivity Data quality Strategic Alignment... Slide 7

8 Models are everywhere Slide 8

9 The use of models Distance between Paris and Dakar = F(x) Information security level = F(x)? Slide 9

10 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 10

11 Architecture Analysis (No different from other types of analyses ) Scenario Analysis Result Business Flexibility = High Business Flexibility Theory Slide 11

12 Causality in Enterprise Architecture Models Slide 12

13 Calculating causality (At KTH, we use Bayesian Networks/Probabalistic Relational Models) Availability of System High Medium Low Availability of Function High Medium Low Slide 13

14 Causality-based and theory driven EA-approach in summary Theory Slide 14

15 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 15

16 A Stakeholder-Oriented Approach to Meta Model Engineering Process Steps 1 Identification of Relevant Concerns Documents List of Relevant Concerns Viewpoint 1 Viewpoint 2 Viewpoint n 2 Requirements Elicitation Viewpoint Requirements Specification 1 Viewpoint Requirements Specification 2 Viewpoint Requirements Specification n 3 Viewpoint Relationship Overview Viewpoint Relationship Diagram Design Validation Design Validation Design Validation 4 Meta Model Fragment Selection or Design Meta Model Fragment 1 Meta Model Fragment 2 Meta Model Fragment n 5 Meta Model Fragment Integration Integrated Meta Model Kurpjuweit, S., Winter, R.: Viewpoint-based Meta Model Engineering, Reichert, M., Strecker, S., Turowski, K. (Eds.): Enterprise Modelling and Information Systems Architectures - Concepts and Applications, Proceedings of the 2nd Int'l Workshop EMISA 2007, St. Goar/Rhine, Germany, , Gesellschaft für Informatik, Köllen, Bonn, P-119, 2007, pp Slide 16

17 Identification of Relevant Concerns Application Architect Cost of application development Correct implementation of ownership policies IT Audit Process Owner Providing adequate IT for business processes EA Software Architect Cost of application operation and maintenance IT Operations Kurpjuweit, S., Winter, R.: Viewpoint-based Meta Model Engineering, Reichert, M., Strecker, S., Turowski, K. (Eds.): Enterprise Modelling and Information Systems Architectures - Concepts and Applications, Proceedings of the 2nd Int'l Workshop EMISA 2007, St. Goar/Rhine, Germany, , Gesellschaft für Informatik, Köllen, Bonn, P-119, 2007, pp Slide 17

18 Meta Model Fragment Selection or Design Viewpoint IT Consolidation Business IT Alignment Component Reuse Ownership Object Processes Applications Processes, Applications Software Architecture IT-related artifacts Purpose Analysis Analysis Design Documentation Concern Cost of application operation and maintenance Providing adequate IT for business processes Cost of application development Correct implementation of ownership policies Stakeholder Application architect Process owner Software architect IT audit Design Strategies Consolidation of applications that are in use for similar purposes / Consolidation of system software of the same type (e.g., DBMS, WFMS) Providing IT functionalities for each process step / reduction of media breaks Reuse of software components across multiple applications / reuse of system software (e.g,. DBMS, WFMS) Assigning explicit owners to applications and other ITrelated artefacts (like information objects, components, environments, etc.) Questions Which applications are used in the individual processes (sorted by organizational unit, product, distribution channel)? / Which system software of the same type is currenty in use? Which process activities are not IT supported? Which processes include media breaks? / Which applications are supported by multiple applications? Which components are available in existing applications? / Which interfactes are available to use these components? Which system software of different types is currently in use? Are there applications for which no owners have been defined? Are there applications that have not been audited for more than two years? Meta Model Fragment Slide 18

19 Meta Model Fragment Integration Integration Operations Adjusting Terminology Creating generalizations Creating specializations Avoiding redundancies Introducing interface modeling concepts part of Product Process specialization Distribution Channel Org. Unit part of Site Business Information Object Information Flow Application Person Position part of Data Entity Software Component Interface Application Environment System Software Complete Meta Model (simplified) Server User Interface Business Logic Data Container Physical Server Sever Cluster Virtual Server Kurpjuweit, S., Winter, R.: Viewpoint-based Meta Model Engineering, Reichert, M., Strecker, S., Turowski, K. (Eds.): Enterprise Modelling and Information Systems Architectures - Concepts and Applications, Proceedings of the 2nd Int'l Workshop EMISA 2007, St. Goar/Rhine, Germany, , Gesellschaft für Informatik, Köllen, Bonn, P-119, 2007, pp Slide 19

20 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 20

21 Comparison of the two approaches Stakeholder-Oriented Approach Goal Support for stakeholders in concrete application scenarios (e.g. IT consolidation, product planning, and post merger integration in organizations) Focus Entities and relations What does exist? What entities are connected? Who will use what? Scope Entities Entity relations Causality-Based Approach Support assessment of enterprises goal properties (e.g. Business and IT performance, changeability, security) by connecting them to controllable attributes Causal relations between attributes Theoretical structure (metamodel level) Impact of different architecture scenarios (instantiated model level) Entities Entity relations (incl. multiplicity) Entity attributes Causal relationships between attributes Slide 21

22 The Proposed Combined Method 1) Define application scenario 2) Identify stakeholders IT consolidation System owners 3) Elicit concerns and information demand 4) Formalize information demand into metrics 5) Decompose in more tangible sub goals 6) Identify attributes of entities with impact on sub goals 7) Create meta model fragments 8) Integrate fragments Information keep vs. phase out Cost benefit analysis criticality for business process vs. TCO Criticality, availability Entities, relationships, attributes, causalities Meta model to support keep vs. phase out decision. Slide 22

23 Agenda Motivation Causality-based Approach Stakeholder-oriented Approach Best-of-Breed Method Conclusion and Outlook Slide 23

24 Conclusion What did we get in the combined approach? Agility to the situation Modelling and management efficiency (model only what you need) Stakeholder focus Goal orientation Sustainable metamodel evolution for reuse Slide 24

25 Outlook A reference catalogue of types of goals A reference catalogue of, or method for developing types of decisions/scenarios A reference catalogue of stakeholders relation to goals and decisions/scenarios A reference catalogue of theory/attribute causality Slide 25

26 Outlook Slide 26