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

  • Carsten Lucke
  • Ulrike Lechner
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 92)

Abstract

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.

Keywords

Goal-oriented requirements engineering GORE enterprise architecture concern elicitation concern identification stakeholder orientation 

References

  1. 1.
    Aier, S., Kurpjuweit, S., Riege, C., Saat, J.: Stakeholderorientierte Dokumentation und Analyse der Unternehmensarchitektur. In: Hegering, H., Lehmann, A., Ohlbach, H., Scheideler, C. (eds.) INFORMATIK 2008: Beherrschbare Systeme – dank Informatik, vol. 2, pp. 559–565. GI/Köllen, München (2008)Google Scholar
  2. 2.
    Kurpjuweit, S.: Stakeholder-orientierte Modellierung und Analyse der Unternehmensarchitektur unter besonderer Berücksichtigung der Geschäfts- und IT-Architektur. Inst. für Wirtschaftsinformatik, doctoral thesis, Universität St. Gallen, Hochschule für Wirtschafts-, Rechts- und Sozialwissenschaften (HSG), St. Gallen, p. 419 (2009)Google Scholar
  3. 3.
    Lucke, C., Krell, S., Lechner, U.: Critical Issues in Enterprise Architecting – A Literature Review. In:16th Americas Conference on Information Systems, Paper 305, Lima, Peru (2010)Google Scholar
  4. 4.
    Lucke, C., Lechner, U.: Goal-oriented requirements modeling as a means to address stakeholder-related issues in EA. In: Bernstein, A., Schwabe, G. (eds.) 10 Internationale Tagung Wirtschaftsinformatik, Zürich, Switzerland, pp. 714–723 (2011)Google Scholar
  5. 5.
    Niemi, E.: Enterprise Architecture Stakeholders - a Holistic View. In: 13th Americas Conference on Information Systems, Paper 41 (2007)Google Scholar
  6. 6.
    The Open Group: TOGAF Version 9 - The Open Group Architecture Framework (TOGAF). The Open Group (2009)Google Scholar
  7. 7.
    International Organization for Standardization: ISO/IEC 42010 (WD4). Systems and Software Engineering — Architecture Description (2007)Google Scholar
  8. 8.
    Cheng, B.H.C., Atlee, J.M.: Research Directions in Requirements Engineering. In: 2007 Future of Software Engineering, pp. 285–303. IEEE Computer Society, Los Alamitos (2007)CrossRefGoogle Scholar
  9. 9.
    Nuseibeh, B., Easterbrook, S.: Requirements engineering: a roadmap. In: Conference on The Future of Software Engineering, pp. 35–46. ACM, Limerick (2000)CrossRefGoogle Scholar
  10. 10.
    Lamsweerde, A.v.: Goal-Oriented Requirements Engineering: A Guided Tour. In: 5th IEEE International Conference on Requirements Engineering, pp. 249–262 (2001)Google Scholar
  11. 11.
    Bender, G.: Designing a Stakeholder-Specific Enterprise Architecture Management based on Patterns. sebis, master’s thesis, p. 136. TU München (2009)Google Scholar
  12. 12.
    Chief Information Officer Council: A Practical Guide to Federal Enterprise Architecture (2001)Google Scholar
  13. 13.
    Lankhorst, M., Quartel, D.: Architecture-Based IT Valuation - Supporting portfolio management and investment decisions. Via Nova Architectura (2010)Google Scholar
  14. 14.
    Op’t Land, M., Proper, E., Waage, M., Cloo, J., Steghuis, C.: Enterprise Architecture: Creating Value by Informed Governance. Springer, Berlin (2009)Google Scholar
  15. 15.
    Quartel, D., Engelsman, W., Jonkers, H., van Sinderen, M.: A Goal-Oriented Requirements Modelling Language for Enterprise Architecture. In: IEEE International Enterprise Distributed Object Computing Conference, pp. 3–13 (2009)Google Scholar
  16. 16.
    Schekkerman, J.: How to survive in the jungle of enterprise architecture frameworks: creating or choosing an Enterprise Architecture Framework. Trafford Publishing (2004)Google Scholar
  17. 17.
    Buckl, S., Ernst, A., Lankes, J., Matthes, F.: Enterprise Architecture Management Pattern Catalog (Version 1.0, February 2008). Technical Report TB0801, Chair for Informatics 19 (sebis), Technische Universität München (2008)Google Scholar
  18. 18.
    Chair for Informatics 19 (sebis). EAM Pattern Catalog, http://wwwmatthes.in.tum.de/wikis/eam-pattern-catalog/home (accessed June 6, 2011)
  19. 19.
    Clements, P., Bass, L.: Using Business Goals to Inform a Software Architecture. In: 18th IEEE International Requirements Engineering Conference (RE), pp. 69–78 (2010)Google Scholar
  20. 20.
    Clements, P., McGregor, J.D., Bass, L.: Eliciting and capturing business goals to inform a product line’s business case and architecture. In: Bosch, J., Lee, J. (eds.) SPLC 2010. LNCS, vol. 6287, pp. 393–405. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  21. 21.
    Bortz, J., Döring, N.: Forschungsmethoden und Evaluation für Human- und Sozialwissenschaftler. Springer, Berlin (2006)Google Scholar
  22. 22.
    Mitchell, R.K., Agle, B.R., Wood, D.J.: Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts. The Academy of Management Review 22, 853–886 (1997)Google Scholar
  23. 23.
    Spewak, S., Hill, S.C.: Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology. QED Publishing Group (1993)Google Scholar
  24. 24.
    Solingen, R.v., Berghout, E.: The Goal/Question/Metric Method: A Practical Guide for Quality Improvement of Software Development. McGraw-Hill, New York (1999)Google Scholar
  25. 25.
    van Lamsweerde, A.: Handling Obstacles in Goal-Oriented Requirements Engineering. IEEE Transactions on Software Engineering 26, 978–1005 (2000)CrossRefGoogle Scholar
  26. 26.
    Yu, E.: Modelling Strategic Relationships for Process Reengineering. Graduate Department of Computer Science. Doctor of Philosophy, p. 178. University of Toronto (1995)Google Scholar
  27. 27.
    Yu, E.S.K.: Towards modelling and reasoning support for early-phase requirements engineering. In: 3rd IEEE Int’l Symposium on Requirements Engineering, pp. 226–235 (1997)Google Scholar
  28. 28.
    i* Wiki, http://istar.rwth-aachen.de (accessed August 7, 2010)
  29. 29.
    Free Merriam-Webster Dictionary. Assessment, http://www.merriam-webster.com/dictionary/assessment (accessed February 9, 2011)
  30. 30.
    Free Merriam-Webster Dictionary. Appraisal, http://www.merriam-webster.com/dictionary/appraisal (accessed February 9, 2011)
  31. 31.
    International Telecommunication Union: Z.151: User requirements notation (URN) - Language definition (2008)Google Scholar
  32. 32.
    Lamsweerde, A. v., Letier, E.: From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering. In: Wirsing, M., Knapp, A., Balsamo, S. (eds.) RISSEF 2002. LNCS, vol. 2941, pp. 325–340. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  33. 33.
    Free Merriam-Webster Dictionary. Task, http://www.merriam-webster.com/dictionary/task (accessed February 9, 2011)
  34. 34.
    Lankes, J., Matthes, F., Wittenburg, A.: Architekturbeschreibung von Anwendungslandschaften: Softwarekartographie und IEEE Std 1471-2000. Software Engineering, 43–54 (2005)Google Scholar
  35. 35.
    Yu, E., Strohmaier, M., Xiaoxue, D.: Exploring Intentional Modeling and Analysis for Enterprise Architecture. In: 10th IEEE International Enterprise Distributed Object Computing Conference Workshops (2006)Google Scholar
  36. 36.
    Emery, D., Hilliard, R.: Every Architecture Description Needs a Framework: Expressing Architecture Frameworks Using ISO/IEC 42010. In: European Conference on Software Architecture, pp. 31–40 (2009)Google Scholar
  37. 37.
    Buckl, S., Krell, S., Schweda, C.M.: A formal approach to architectural descriptions – refining the ISO standard 42010. In: Albani, A., Dietz, J.L.G. (eds.) CIAO! 2010. LNBIP, vol. 49, pp. 77–91. Springer, Heidelberg (2010)CrossRefGoogle Scholar

Copyright information

© IFIP International Federation for Information Processing 2011

Authors and Affiliations

  • Carsten Lucke
    • 1
  • Ulrike Lechner
    • 1
  1. 1.WirtschaftsinformatikUniversität der Bundeswehr MünchenNeubibergGermany

Personalised recommendations