Towards an Approach for Stakeholder-Oriented Elicitation and Identification of Concerns in EA

The concept of concern is used in Enterprise Architecture (EA) to express a stakeholder’s area of interest in a system whose architecture is to be described. Many EA-related problems are rooted in weak stakeholder orientation. We propose an approach to explicitly model stakeholders’ concerns as part of an architecture description. Our contribution is a modeling notation for concern elicitation and a method for concern identification. Our approach is based on goal-oriented requirements engineering and is compatible to the conceptual framework of the ISO 42010 international standard. We claim that our approach allows for a more thorough understanding of stakeholders’ concerns and facilitates a stronger stakeholder orientation in EA.

[1]  Eetu I. Niemi,et al.  Enterprise Architecture Stakeholders - a Holistic View , 2007, AMCIS.

[2]  J. Bortz,et al.  Forschungsmethoden und Evaluation , 1995 .

[3]  Jaap Schekkerman,et al.  How to Survive in the Jungle of Enterprise Architecture Framework: Creating or Choosing an Enterprise Architecture Framework , 2003 .

[4]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[5]  Sabine Buckl,et al.  Enterprise Architecture Management Pattern Catalog Glossary Version 1 . 0 April 2008 , 2008 .

[6]  Markus Strohmaier,et al.  Exploring Intentional Modeling and Analysis for Enterprise Architecture , 2006, 2006 10th IEEE International Enterprise Distributed Object Computing Conference Workshops (EDOCW'06).

[7]  Jaejoon Lee,et al.  Software Product Lines: Going Beyond - 14th International Conference, SPLC 2010, Jeju Island, South Korea, September 13-17, 2010. Proceedings , 2010, SPLC.

[8]  Sabine Buckl,et al.  A Formal Approach to Architectural Descriptions - Refining the ISO Standard 42010 , 2010, CIAO!@DESRIST.

[9]  Donald Sannella,et al.  Toward Component-Oriented Formal Software Development: An Algebraic Approach , 2002, RISSEF.

[10]  Ronald K. Mitchell,et al.  Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of who and What Really Counts , 1997 .

[11]  Leonard J. Bass,et al.  Using Business Goals to Inform a Software Architecture , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[12]  Stephan Kurpjuweit,et al.  Stakeholder-orientierte Modellierung und Analyse der Unternehmensarchitektur: unter besonderer Berücksichtigung der Geschäfts- und IT-Architektur , 2009 .

[13]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[14]  Ulrike Lechner,et al.  Goal-oriented requirements modeling as a means to address stakeholder-related issues in EA , 2011, Wirtschaftsinformatik.

[15]  Marc M. Lankhorst,et al.  Architecture-Based IT Valuation Supporting portfolio management and investment decisions , 2010 .

[16]  Ulrike Lechner,et al.  Critical Issues in Enterprise Architecting - A Literature Review , 2010, AMCIS.

[17]  Egon Berghout,et al.  The Goal/Question/Metric method: a practical guide for quality improvement of software development , 1999 .

[18]  Axel van Lamsweerde,et al.  From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering , 2002, RISSEF.

[19]  Rich Hilliard,et al.  Every architecture description needs a framework: Expressing architecture frameworks using ISO/IEC 42010 , 2009, 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture.

[20]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

[21]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[22]  Leonard J. Bass,et al.  Eliciting and Capturing Business Goals to Inform a Product Line's Business Case and Architecture , 2010, SPLC.

[23]  Florian Matthes,et al.  Architekturbeschreibung von Anwendungslandschaften: Softwarekartographie und IEEE Std 1471-2000 , 2005, Software Engineering.

[24]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[25]  J. Bortz,et al.  Forschungsmethoden und Evaluation für Human- und Sozialwissenschaftler , 2006 .

[26]  Stephan Aier,et al.  Stakeholderorientierte Dokumentation und Analyse der Unternehmensarchitektur , 2008, GI Jahrestagung.

[27]  Marten van Sinderen,et al.  A Goal-Oriented Requirements Modelling Language for Enterprise Architecture , 2009, 2009 IEEE International Enterprise Distributed Object Computing Conference.

[28]  Florian Matthes,et al.  Enterprise Architecture Management Patterns -- Exemplifying the Approach , 2008, 2008 12th International IEEE Enterprise Distributed Object Computing Conference.

[29]  藤崎 繁,et al.  TOGAF Version 9.1 : the Open Group Architecture Framework (TOGAF) : 日本語訳版 , 2012 .

[30]  Martin Op't Land,et al.  Enterprise Architecture - Creating Value by Informed Governance , 2008, The Enterprise Engineering Series.