A Business-Oriented Approach to Requirements Elicitation

Adam Przybyłek


“The hardest single part of building a software system is deciding precisely what to build” (Brooks, 1987). Faulty requirements analysis is a major reason for project failure or unsatisfactory information systems that do not fulfill business needs. Although it has been long recognized that system requirements can only be understood within the context of the business processes and business modeling has become the initial phase of most software processes, the transition between business modeling and requirements gathering is still a challenge for research. Moreover, existing work in this area tends to introduce accidental difficulties. This paper reports the results of an action research conducted for elaborating a Business-Oriented approach to Requirements Elicitation. Our approach integrates Requirements Engineering with Business Process Engineering and derives system requirements based on business process models. This ensures that system requirements meet real business needs. The proposed approach is illustrated by a real-world example.


  1. Aburub, F., 2012. Activity-based approach to derive system models from business process models. In: International Conference on Information Society, London, UK
  2. Bendakir, S., El Hamlaoui, M., Zarour, N., 2013. An agent-oriented approach to support requirements prioritization processes. In: IEEE International Workshop on Requirements Engineering 2013, Constantine.
  3. Bobkowska, A., 2005. A framework for methodologies of visual modeling language evaluation. In: Proc. of the 2005 symposia on Metainformatics, Esbjerg, Denmark.
  4. Brooks, F., 1987. No Silver Bullet: Essence and Accidents of Software Engineering. In: Computer 20, 4 (April 1987), pp. 10-19.
  5. Bubenko, J. A., Persson, A., Stirna, J., 2001. EKD User Guide, Royal Institute of Technology (KTH) and Stockholm University, Stockholm, Sweden.
  6. Dijkman, R. M., Joosten, S. M. M., 2002. An Algorithm to Derive Use Cases from Business Processes. In: 6th IASTED International Conference on Software Engineering and Applications, Cambridge, MA.
  7. Eriksson, H., Penker, M., 2000. Business Modeling with UML: Business Patterns at Work. John Wiley & Sons.
  8. Faulk, S., 1997. Software Requirements: A Tutorial. In: Thayer, R., Dorfman, M. (Eds.): Software Requirements Engineering. IEEE Computer Society press.
  9. Frost, S., Allen, P., 1996. Business Process Modeling, SELECT Software Tools plc, Cheltenham
  10. Gawin, B., Marcinkowski, B., 2013. Simulating Business Processes. BPMS and BPMN Standards Applied (in Polish). Helion.
  11. Gotel, O., Finkelstein, A., 1994. An Analysis of the Requirements Traceability Problem. In: 1st International Conference on Requirements Engineering, Colorado Springs, CO.
  12. Górski, J., 2000. Inzynieria oprogramowania: w projekcie informatycznym (in Polish). MIKOM.
  13. Hammer, M., 1990. Reengineering work: don't automate, obliterate. Harvard Business Review, July-August 1990, pp. 104-112.
  14. Harmon, P., Wolf, C., 2011. Business Process Modeling Survey. Business Process Trends.
  15. Jacobson, I., 1987. Object-Oriented Development in an Industrial Environment. In: SIGPLAN Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA'87), Orlando, FL.
  16. Jacobson, I., 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley.
  17. Jacobson, I., Booch, G., Rumbaugh, J., 1999. The Unified Software Development Process. Addison-Wesley.
  18. Leffingwell, D., Widrig, D., 1999. Managing Software Requirements. Addison Wesley.
  19. Lehtola, L., Kauppinen, M., Vähäniitty, J., Komssi, M., 2009. Linking business and requirements engineering: is solution planning a missing activity in software product companies?. In: Requirements Engineering vol. 14(2), April 2009, pp. 113-128.
  20. Maciaszek, L., 2005. Requirements analysis and system design. Addison-Wesley.
  21. Monsalve, C., April, A., Abran, A., 2010. Representing Unique Stakeholder Perspectives in BPM Notations. In: 8th ACIS International Conference on Software Engineering Research, Management and Applications, Montreal, Canada.
  22. Marcinkowski, B., 2010. Applying Business Process Modeling Techniques: Case Study. Journal of Internet Banking and Commerce 15, Array Development.
  23. Odeh, M., Kamm, R., 2003. Bridging the gap between business models and system models. In: Information and Software Technology, (45)15, pp. 1053-1060.
  24. Przybylek, A., 2007. The Integration of Functional Decomposition with UML Notation in Business Process Modelling. In: Advances in Information Systems Development, Vol 1, pp. 85-99.
  25. Przybylek, M., 2013. Skeletal Algorithms in Process Mining. In: Studies in Computational Intelligence, vol. 465, pp. 119-134.
  26. Przybylek, M., 2013. Process mining through tree automata. In: 5th International Conference on Evolutionary Computation Theory and Applications, Vilamoura, Portugal.
  27. Przybylek, M., 2013. Dynamic data discovery. In: 8th International Conference on Knowledge, Information and Creativity Support Systems, Cracow, Poland.
  28. Ravichandar, R., Arthur, J. D., Perez-Quinones, M., 2007. Pre-requirement specification traceability: Bridging the complexity gap through capabilities.
  29. Regnell, B., Andersson, M., Bergstrand, J., 1996. A Hierarchical Use Case Model with Graphical Representation. In: IEEE International Symposium and Workshop on Engineering of Computer-Based Systems, Friedrichshafen, Germany.
  30. Robertson, S., Robertson, J., 2013. Mastering the Requirements Process. Addison Wesley.
  31. Sjoberg, D., Dyba, T., Jorgensen, M., 2007. The future of empirical methods in software engineering research. In: 2007 Future of Software Engineering (FOSE'07), Minneapolis, MN.
  32. Štolfa, S., Vondrák, I., 2004. A Description of Business Process Modeling as a Tool for Definition of Requirements Specification. In: 12th International Conf. on Systems Integration, Prague, Czech Republic.
  33. Taylor-Cummings, A., 1998. Bridging the user-IS gap: a study of major information systems projects. Journal of Information Technology 13, pp. 29-54.
  34. Torkar, R., Gorschek, T., Feldt, R., Svahnberg, M., Raja, U., Kamran, K., 2012. Requirements Traceability: a Systematic Review and Industry Case Study. International Journal of Software Engineering and Knowledge Engineering 22(3), pp. 385-434
  35. Vara González, J. L., 2011. Business process-based requirements specification and object-oriented conceptual modelling of information systems. PhD thesis, Universidad Politecnica de Valencia.
  36. Vara, J.L., Sánchez, J., Pastor, Ó., 2008. Business Process Modelling and Purpose Analysis for Requirements Analysis of Information Systems. In: 20th international conference on Advanced Information Systems Engineering, Montpellier, France.
  37. Weerakkody, V., Currie, W., 2003. Integrating business process reengineering with information systems development: issues & implications. In: 2003 international conference on Business process management (BPM'03), Eindhoven, Netherlands.
  38. Wolf, C., Harmon, P., 2012. The State of Business Process Management. Business Process Trends.
  39. Wrycza, S., Marcinkowski, B., Wyrzykowski, K., 2005. UML 2.0 in Information Systems Modeling (in Polish). Helion.

Paper Citation

in Harvard Style

Przybyłek A. (2014). A Business-Oriented Approach to Requirements Elicitation . In Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE, ISBN 978-989-758-030-7, pages 152-163. DOI: 10.5220/0004887701520163

in Bibtex Style

author={Adam Przybyłek},
title={A Business-Oriented Approach to Requirements Elicitation},
booktitle={Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,},

in EndNote Style

JO - Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,
TI - A Business-Oriented Approach to Requirements Elicitation
SN - 978-989-758-030-7
AU - Przybyłek A.
PY - 2014
SP - 152
EP - 163
DO - 10.5220/0004887701520163