Advertisement

A Conceptual Foundation of Requirements Engineering for Business Information Systems

  • Sebastian Adam
  • Norman Riegel
  • Anne Gross
  • Oezguer Uenalan
  • Simon Darting
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 113)

Abstract

Requirements engineering (RE) is a crucial discipline when developing software systems. Applying RE activities successfully in the domain of business information systems (BIS) requires a deep and common understanding on how concepts of RE and business analysis are related. We consider this fact as being a challenge as currently no commonly accepted RE process exits that bridges the gap between these two disciplines. This results in unclear mappings and finally makes it difficult to align methods that exist in both areas. To tackle this challenge, we propose a reference issue model that aims to capture definitions and relations of the issues that are typically relevant in BIS development. In this context, we describe our followed research approach, an underlying meta-model as well as an exemplary instantiation and usage of the reference issue model. This contribution shall serve as a foundation for the integration of RE and business analysis as well as for the development of corresponding analysis approaches.

Keywords

Business Process Requirement Engineering Conceptual Foundation Requirement Engineer Business Object 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    The Standish Group International: CHAOS Manifesto (2011), http://blog.standishgroup.com (last visited: January 18, 2011)
  2. 2.
    Gulla, J.A.: Understanding Requirements in Enterprise System Projects. In: RE 2004. IEEE (2004)Google Scholar
  3. 3.
    Etien, A., Rolland, C.: Measuring the fitness relationship. Requirements Engineering Journal, 184–197 (2005)Google Scholar
  4. 4.
    Weske, M.: Business Process Management: Concepts, Languages, Architectures. Springer, Berlin (2007)Google Scholar
  5. 5.
    Robertson, S., Robertson, J.: Mastering the Requirements Process. Addison-Wesley, Reading (1999)Google Scholar
  6. 6.
    Jeusfeld, M.A., Jarke, M., Mylopoulos, J.: Metamodeling for Method Engineering. The MIT Press, Cambridge (2009)Google Scholar
  7. 7.
    IEEE Computer Society: IEEE 830-1998 - IEEE Recommended Practice for Software Requirements Specifications. IEEE (1998)Google Scholar
  8. 8.
    IEEE Computer Society: IEEE 1233-1998 - IEEE Guide for Developing System Requirements Specifications Description. IEEE (1998) Google Scholar
  9. 9.
    IEEE Computer Society: IEEE 1362-1998 - IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document Description. IEEE (1998) Google Scholar
  10. 10.
    BMI: Das V-Modell XT, http://www.v-modell-xt.de/ (last visited: February 14, 2012)
  11. 11.
    Scheer, A.-W.: ARIS - Modellierungsmethoden, Metamodelle, Anwendungen. Springer, Berlin (1998)CrossRefGoogle Scholar
  12. 12.
    Hay, D.C.: Requirements Analysis: From Business Views to Architecture. Prentice Hall Professional, Upper Saddle River (2003)Google Scholar
  13. 13.
    Kruchten, P.: The Rational Unified Process. Addison-Wesley, Boston (2000)Google Scholar
  14. 14.
    Adam, S., Doerr, J., Eisenbarth, M., Gross, A.: Using Task-oriented Requirements Engineering in Different Domains. In: RE 2009, pp. 267–272. IEEE (2009)Google Scholar
  15. 15.
    Adam, S., Naab, M., Trapp, M.: A Service-Oriented View on Business Processes and Supporting Applications. In: CAiSE 2010. Springer, Berlin (2010) Google Scholar
  16. 16.
  17. 17.
    Alexander, I.F.: A Taxonomy of Stakeholders. Int. Journal of Technology and Human Interaction, IJTHI 1, 23–59 (2005)CrossRefGoogle Scholar
  18. 18.
    Adam, S.: Providing Software Product Line Knowledge to Requirements Engineers – A Template for Elicitation Instructions. In: Regnell, B., Damian, D. (eds.) REFSQ 2012. LNCS, vol. 7195, pp. 147–164. Springer, Heidelberg (2012)CrossRefGoogle Scholar
  19. 19.
    Nuseibeh, B., Easterbrook, S.: The Future of Software Engineering. In: ICSE 2000, pp. 35–46. ACM Press, New York (2000)CrossRefGoogle Scholar
  20. 20.
    Wiegers, K.E.: Software Requirements. Microsoft Press (2005)Google Scholar
  21. 21.
    IEEE: Computer Society. Software Engineering Body of Knowledge. IEEE (2004) Google Scholar
  22. 22.
    Lamsweerde, A.: Requirements Engineering: From System Goals to UML Models to Software Specifications. John Wiley & Sons, Chichester (2009)Google Scholar
  23. 23.
    Kotonya, G., Sommerville, I.: Requirements Engineering: Processes and Techniques. John Wiley, New York (1998)Google Scholar
  24. 24.
    The Free Dictionary, http://www.thefreedictionary.com/ (last visited: January 01, 2012)
  25. 25.
    Riegel, N., Adam, S., Gross, A.: Addressing Requirements Engineering Challenges in the Context of Emergent Systems. In: RESS 2011. IEEE (2011)Google Scholar
  26. 26.
    Object Management Group: OMG’s Meta Object Facility (MOF), http://www.omg.org/mof/ (last visited: January 18, 2012)
  27. 27.
    Gross, A.: Perspective-based Specification of Efficiently and Effectively Usable Requirements Documents. In: Doctoral Symposium RE 2010, Sydney (2010) Google Scholar
  28. 28.
    Adam, S., Doerr, J., Ehresmann, M., Wenzel, P.: Incorporating SPL Knowledge into a Requirements Process for Information Systems. In: PLREQ 2010, Essen, pp. 54–66 (2010)Google Scholar
  29. 29.
    Wiegers, K.E.: First Things First: Prioritizing Requirements. Software Development 7, 48–53 (1999)Google Scholar
  30. 30.
    Riegel, N., Adam, S., Gross, A.: Addressing requirements engineering challenges in the context of Emergent Systems. In: RESS, pp. 6–9. IEEE, Trento (2011)Google Scholar
  31. 31.
    Object Management Group: Business Process Model and Notation (BPMN), http://www.omg.org/spec/BPMN/2.0/ (last visited January 18, 2012)
  32. 32.
    Soffer, P., Wand, Y.: Goal-Driven Analysis of Process Model Validity. In: Persson, A., Stirna, J. (eds.) CAiSE 2004. LNCS, vol. 3084, pp. 521–535. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  33. 33.
    Scheer, A.-W.: Wirtschaftsinformatik: Referenzmodelle für industrielle Geschäftsprozesse. Springer, Berlin (1994)Google Scholar
  34. 34.
    Champion, R.E.M., Moores, T.T.: Exploiting an enterprise model during systems’ requirements capture and analysis. In: ICRE 1996, Colorado Springs (1996)Google Scholar
  35. 35.
    Goknil, A., Kurtev, I., van den Berg, K.: A Metamodeling Approach for Reasoning about Requirements. In: Schieferdecker, I., Hartman, A. (eds.) ECMDA-FA 2008. LNCS, vol. 5095, pp. 310–325. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  36. 36.
    von Knethen, A.: Trace model for system requirements changes on embedded systems. In: IWPSE 2001, New York (2001)Google Scholar
  37. 37.
    Bubenko, J.A.J., Persson, A., Stirna, J.: User Guide of Knowledge Management Approach Using Enterprise Knowledge Patterns, deliverable D3, IST Programme project IST-2000-28401 HyperKnowledge, KTH, Schweden (2001)Google Scholar
  38. 38.
    Méndez-Fernández, D., Lochmann, K., Penzenstadler, B., Wagner, S.: A Case Study on the Application of an Artefact-Based Requirements Engineering Approach. In: 15th EASE, IET (2011)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Sebastian Adam
    • 1
  • Norman Riegel
    • 1
  • Anne Gross
    • 1
  • Oezguer Uenalan
    • 1
  • Simon Darting
    • 1
  1. 1.Fraunhofer IESEKaiserslauternGermany

Personalised recommendations