Bridging the Requirements Engineering and Business Analysis Toward a Unified Knowledge Framework

  • Mikio AoyamaEmail author
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 9975)


Several similar but different disciplines have evolved in the arena of requirements engineering and business analysis, including business analysis, BPM (Business Process Management), and business architecture. Yet, they are forming bodies of knowledges in each discipline. Each discipline has its raison d’etre. However, such diversity of the bodies of knowledge causes a confusion. This article is intended to review the bodies of knowledge, and proposes a unified knowledge framework of the bodies of knowledge across the disciplines.


Requirements engineering Business analysis Business process management Business architecture Body of knowledge 


  1. 1.
    van der Aalst, W.M.: Business Process Management Demystified: A Tutorial on Models, Systems and Standards for Workflow Management. In: Desel, J., Reisig, W., Rozenberg, G. (eds.) Lectures on Concurrency and Petri Nets. LNCS, vol. 3098, pp. 1–65. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  2. 2.
    Aoyama, M., Nakatani, T., Saito, S., Suzuki, M., Fujita, K., Nakazaki, H., Suzuki, R.: A model and architecture of REBOK(Requirements Engineering Body Of Knowledge) and its evaluation. In: Proceeding of APSEC 2010, IEEE Compute Society, November-December 2010, pp. 50–59 (2010)Google Scholar
  3. 3.
    Benedict, T., et al.: BPM CBOK Version 3.0: guide to the business process management common body of knowledge, In: ABPMP International/Createspace (2013).
  4. 4.
    Bourque, P., Fairley, R.E. (eds.) SWEBOK 3.0: Guide to the Software Engineering Body of Knowledge. IEEE Computer Society (2014)Google Scholar
  5. 5.
    Business Architecture Guild, A Guide to the Business Architecture Body of Knowledge (BIZBOK Guide), V. 4.5 (2015).
  6. 6.
    Darwish, A.: Business Process Analysis versus Business Analysis: Why Most Organizations Confuse Them? August 2015.
  7. 7.
    Davenport, T.H.: Process Innovation: Reengineering Work Through Information Technology. Harvard Business School Press, Boston (1993)Google Scholar
  8. 8.
    Decreus, K., et al.: Bridging requirements engineering and business process management., In: Proceeding of the REBPM 2009, Gesellschaft für Informatik e.V., pp. 215–222, March 2009Google Scholar
  9. 9.
    Dugan, L., et al.: Business Architecture and BPM, Business Architecture Group Whitepaper, September 2014.
  10. 10.
    Dumas, M., et al. (eds.): Fundamentals Business Process Management. Springer, Heidelberg (2013)Google Scholar
  11. 11.
    Foss, N.J., Saebi, T. (eds.): Business Model Innovation. Oxford University Press, Oxford (2015)Google Scholar
  12. 12.
    Haglind, M., Johansson, L.: Experiences integrating requirements engineering and business analysis. In: Proceeding of RE 1998, pp. 108–117. IEEE Computer Society, April 1998Google Scholar
  13. 13.
    Hammer, M., Champy, J.: Reengineering the Corporation. Harper Collins, New York (1993)Google Scholar
  14. 14.
    Hass, K.B.: Professionalizing Business Analysis. Management Concepts Inc, Vienna (2008)Google Scholar
  15. 15.
    Ide, M., et al.: An IT-driven business model design methodology and its evaluation. In: Proceeding of REBPM 2014, pp. 1–10. IEEE Computer Society, August 2014Google Scholar
  16. 16.
    IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3.0, IIBA (2015).
  17. 17.
    ISO/IEC/IEEE 29148:2011 Software and Systems Engineering – Life Cycle Processes – Requirements Engineering, ISO (2011)Google Scholar
  18. 18.
    Jeston, J., Nelis, J.: Business Process Management, 3rd edn. Routledge, Abingdon (2014)Google Scholar
  19. 19.
    Jisa Rebok, W.G (ed.) Requirements Engineering Body Of Knowledge (REBOK), Version 1.0, Kindaikagakusha (2011). (in Japanese).
  20. 20.
    Ko, R.K.L.: A computer scientist’s introductory guide to business process management (BPM). ACM Crossroads 15(4), 11–18 (2009)CrossRefGoogle Scholar
  21. 21.
    van Lamsweerde, A.: Requirements Engineering. Wiley, New York (2009)zbMATHGoogle Scholar
  22. 22.
    Lankhorst, M.: Enterprise Architecture at Work. Springer, Heidelberg (2005)Google Scholar
  23. 23.
    Leffingwell, D.: Agile Requirements. Addison-Wesley, Upper Saddle River (2011)Google Scholar
  24. 24.
    Nuseibeh, B., Easterbrook, S.: Requirements Engineering: a roadmap. In: Proceeding of the Conference on The Future of Software Engineering, ICSE 200, pp. 35–46. ACM, May 2000Google Scholar
  25. 25.
    A. Osterwalder and Y. Pigneur, Business Model Generation, Wiley, 2010Google Scholar
  26. 26.
    Paul, D., et al.: Business Analysis, 2nd edn. British Informatics Society, Chippenham (2010)Google Scholar
  27. 27.
    Penzenstadler, B., et al.: The Requirements Engineering Body of Knowledge (REBoK). In: Proceeding of the RE 2013, pp. 377–379. IEEE Computer Society, July 2013Google Scholar
  28. 28.
    Pohl, K.: Requirements Engineering. Springer, Heidelberg (2010)CrossRefzbMATHGoogle Scholar
  29. 29.
    Reynolds, C.: Introduction to Business Architecture. Course Technology (2010)Google Scholar
  30. 30.
    Regev, G., Favre, J., Hayek, E., Wilson, p., Wegmann, A.: Business/IT alignment in practice: lessons learned from a requirements project at P&G. In: Salinesi, C., Pastor, O. (eds.) BUSITAL 2011. LNBIP, vol. 83, pp. 93–101. Springer, Heidelberg (2011)Google Scholar
  31. 31.
    Rosemann, M., vom Brocke, J.: The six core elements of business process management. In: von Brocke, Rosemann, M. (eds.) Handbook on Business Process Management. International Handbooks on Information Systems, vol. 1, pp. 105–122. Springer, Heidelberg (2010)Google Scholar
  32. 32.
    von Rosing, M., et al. (eds.) The Complete Business Process Handbook: Body of Knowledge from Process Modeling to BPM, vol. 1, Morgan Kaufman (2015)Google Scholar
  33. 33.
    Rubens, J.: Business analysis and requirements engineering: the same, only different? Requirements Eng. J. 12(2), 121–123 (2007)CrossRefGoogle Scholar
  34. 34.
    Saito, S., Iimura, Y., Aoyama, M.: REO: requirements engineering ontology: spectrum analysis of requirements engineering knowledge and its practical application. In: Proceedings of COMPSAC 2015, pp. 62–70. IEEE Computer Society, July 2015Google Scholar
  35. 35.
    Shull, F., et al.: How perspective-based reading can improve requirements inspections. IEEE Comput. 33(7), 73–79 (2000)CrossRefGoogle Scholar
  36. 36.
    Simon, D., Schmidt, C. (eds.): Business Architecture Management: Architecting the Business for Consistency and Alignment. Springer, Switzerland (2015)Google Scholar
  37. 37.
    Ulrich, W., et al.: Business and Dynamic Change: The Arrival of Business Architecture. Future Strategies Inc. (2015)Google Scholar
  38. 38.
    US Office of Management and Budget, Federal Enterprise Architecture Framework, Version 2 (2013).
  39. 39.
    Wiegers, K., Beatty, J.: Software Requirements, 3rd edn. Microsoft Press, New York (2013)Google Scholar
  40. 40.
    Yu, E., et al. (eds.): Social Modeling for Requirements Engineering. MIT Press, Cambridge (2011)Google Scholar

Copyright information

© Springer International Publishing AG 2016

Authors and Affiliations

  1. 1.Department of Software Engineering, School of Science and EngineeringNanzan UniversityNagoyaJapan

Personalised recommendations