Developing a behavior explanation model to assist design of application landscapes Anna Gschwendtner, 03.11.2014, TU München Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Motivation Practical relevance „ „ A major weakness of many current modeling tools is representing system dynamics. Yet, this is essential for estimating the end-to-end performance of an architecture for different business processes. [Kaisler.2005] „ „ Currently, EA is drowning in complexity of the problems „ [Gartner.2013] Dynamic complexity aspects are „currently underrepresented“ in research [Schneider.2014] „ Kaisler.2005] Kaisler, S; Armour, F.; Valivullah, M.: ''Enterprise Architecting: Critical Problems'‘, Proceedings of the 38th Hawaii International Conference on System Sciences, 2005 [IBM.2010] IBM Global CEO Study, 2010 [Schneider.2014] Schneider, Alexander, Marin Zec, and Florian Matthes. "Adopting Notions of Complexity for Enterprise Architecture Management." (2014). Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 2 Foundation: System Dynamics A methodology and mathematical modeling technique for framing, understanding, and discussing complex issues and problems Developed in the 1950s by Prof. Jay Forrester at the MIT to contribute to a better understanding of industrial processes Approach to understand the dynamic behavior of complex systems over time by providing a visual representation of the respective situation Aspect of Systems Theory Today: Applied in various fields, e.g., social science, ecology or economy [Sunkle.2013] Sunkle, S. ; Roychoudhury S., Kulkarni, V.: Using Intentional and System Dynamics Modeling to Address WHYs in Enterprise Architecture, 2013 [Golnam.2010] Golnam, A., Van Ackerel A; Wegmann, A. : Integrating System Dynamics and Enterprise to Address Dynamic and Structural Complexities of Choice Situations, 2010 [Aier.2009] Saat, J. ; Aier, S.; Gleichauf, B.: Assessing the Complexity of Dynamics in Enterprise Architecture Planning – Lessons from Chaos Theory, 2009 Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 3 Research Questions 1. Can system dynamics models (SDM) support enterprise architecture (EA) design? 2. Which methods are appropriate to develop EA SDMs? 3. How does an exemplary EA SDM look like? Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 4 Approach Design Science according to [Pfeffers.2008] [Hevner.2004] Problem identification and research • Complexity increase • Dynamic complexity not considered in EAM Define solution objectives • CLD development method • Requirements from literature • EA challenges and constraints Design & Development • Integration of existing methods • Extention with EA particularities Evaluation • Demonstration: CLD on IT Standardization based on literature Discussion • Can SDM support EA design? • Limitations • Evaluation via expert interviews [Pfeffers.2008] Pfeffers, K. ; Tuunanen, T..; Rothenberger, M.; Chatterjee, S.: “A Design Science Research Methodology for Information Systems Research” [Hevner.2004] Hevner, A.; Ram, S. : “Design Science in Information Systems Research” MIS Quarterly Vol. 28 No. 1, pp. 75-105/March 2004 Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 5 System Dynamics Causal Loop Diagrams Qualitative system analysis System map with components and their interactions The system structure is represented by interactions - as feedback loops Assumption: Understanding the structure of a system enables to ascertain a system’s behavior over a certain time period [Haraldsson.2000] Haraldsson, H. ; Introduction to Systems and Causal Loop Diagrams [Binder.] Binder, T.: Developing System Dynamics Models From Causal Loop Diagrams Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 6 EA Challenges and Constraints TOGAF Stakeholder groups [The Open Group, 2011] The Open Group (2011). TOGA Version 9.1: An Open Group Standard. Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 7 EA Challenges and Constraints EA and CLDs are affected by diverse stakeholder groups High number of involved stakeholders Varying terminologies and language (skills) => need for consolidation Spatial distribution of the employees Working times do not necessarily coincide Tacit knowledge and high information bias risk Easiness of generating misunderstandings Different and eventually opposing mental models EA behavior is organization-specific Current CLD development methods are generic and do not consider these aspects [Hubler .] Hubler, A: Understanding Complex Systems [NQ Logic] http://blogs.msdn.com/blogfiles/mikewalker/WindowsLiveWriter/MappingCurrentStateArchitecturesacrossth_AFD0/image_10.png, 29.10.2014 Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 8 Which Methods are Appropriate to Develop EA SDMs? (Research Question 2) Methods needs to satisfy the EA challenges and constraints New method required which includes: Data gathering methods and dynamic hypothesis development Adjustment and consolidation of the different stakeholder terminologies as well as heterogeneous points of view Content validity checks Perspective labeling Model validity checks Model content tailorability to the particular target groups Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 9 An EA-specific CLD Development Method 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 10 An EA-specific CLD Development Method 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 11 An EA-specific CLD Development Method Information gathering techniques Interviews Focus groups Oral history Observation Delphi groups Deriving from literature [Haraldsson.2000] Haraldsson, H. ; Introduction to Systems and Causal Loop Diagrams, 2000 [Binder.] Binder, T.: Developing System Dynamics Models From Causal Loop Diagrams Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 3.11.2014 © sebis 12 An EA-specific CLD Development Method 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 13 An EA-specific CLD Development Method 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 14 Single-Loop CLD: The Network Effect Perspective IT development and operations Assumptions A person executing a particular activity will increase his or her skill level considerably faster than someone partitioning his focus on executing multiple and diverse activities [Page.2010, Church and Gandal.1992] Solution architects tend to choose IT products for which experts are available Example An enterprise having built a considerable amount of systems based on SAP has several SAP experts in house. Therefore, if an new IT system has to be designed, the architects will tend to use SAP and the residing expertize. [Page, 2010] Page, S. E. (2010). Diversity and complexity. Princeton University Press. [Church and Gandal, 1992] Church, J. and Gandal, N. (1992). Network effects, software provision, and standardization. The Journal of Industrial Economics 3.11.2014 © sebis [SAP.2014] http://www.safenet-inc.com/uploadedImages/Partners/logos/SAP.jpg?n=4818, 29.10.2014 Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 15 Single-Loop CLD: The Network Effect 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 16 How Does an Exemplary EA SDM Look Like? (Research Question 3) An integrated CLD based on literature (and evaluated in practice) 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 17 Evaluation- Approach • • • • • Experts with diverse backgrounds questioned Interviews conducted face-to-face or via video conference tools Purpose: evaluate the modeling method and the model content Durance: 1- 2 hours Conduction time span: between July 2014 and September 2014 ID Role Industry Experience 1 Enterprise Architecture Consultant Insurance 2 years 2 Project Manager (Business) Automotive >10 years 3 Project Manager (IT) Gas 6 years 4 Project Manager (Business) Automotive 3 years 5 Head of Sales and Marketing Analytics Pharma >10 years 6 Enterprise Architect Automotive 2 years 7 IT revision Service Industry 1 year 8 Chief Architect Automotive >10 years 9 Enterprise Architect Software Development >10 years 10 Application Architect Software Development >10 years 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 18 Evaluation results: Can SDM support EA design? (Research Question 1) Model evaluation results Number of interviewees Modeling understanding 10 Explanation required 10 Model content agreement 10 Communication support 10 Role depiction 6 Identifying side effects 5 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 19 Summary, Critical Reflection and Outlook Summary Dynamic complexity not sufficiently covered in EAM literature EA challenges and constraints identified and EA- specific CLD development method designed Exemplary CLD model on the topic of technological standardization developed based on literature Model evaluated via 10 expert interviews 3.11.2014 © sebis Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 20 Summary, Critical Reflection and Outlook Critical reflection Model understanding and content confirmed by the interviewees Limited number of interviews Models have not been tested in practice Outlook Currently insufficient tool support Model testing in practice [IBH.2014] IBH, http://www.bodenseehochschule.org/wp-content/uploads/2010/12/fernrohr.jpg, 29.10.2014 Gschwendtner - Developing a Behavior Explanation Model 3.11.2014 © sebis 3.11.2014 © sebis 21 Thanks for your attention! Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de
© Copyright 2024 ExpyDoc