Business Process Model Driven Approach for Automatic Use Case Model Generation

Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 391)


Requirement elicitation is an essential step for establishing software requirements. They define the outcomes upon which software functionality is produced. However, several studies have shown majority of errors found in software functionality are directly linked to requirement elicitation. To address, this paper proposes a structured approach to derive system requirements automatically using business process models. It employs a systematic mechanism to improve business process models and transformation method to generate requirement models. It employs 26 defined heuristics rules that maps and controls transformation. The proposed approach is evaluated using seven case studies. Results show the viability to generate software requirements from business process models, and the automatic generation of rich UML-based use case diagram. The proposed approach achieves more precise and valid requirement specifications and was able to generate additional valid use case model features compared to other competing approaches.


Requirement engineering Business process modelling Use case model 


  1. 1.
    Dijkman, R.M., Joosten, S., Ordina, F.: An algorithm to derive use case diagrams from business process models. In: Proceedings of the 6th International Conference on Software Engineering and Applications, SEA, Anaheim, US‏ (2002)Google Scholar
  2. 2.
    Odeh, M., Richard, K.: Bridging the gap between business models and system models. Inf. Softw. Technol. 45(15), 1053–1060 (2003)CrossRefGoogle Scholar
  3. 3.
    Aburub, F.: Activity-based approach to derive system models from business process models. In: International Conference on Information Society, i-Society. IEEE (2012)Google Scholar
  4. 4.
    Przybylek, A.: A business-oriented approach to requirements elicitation. In: International Conference on Evaluation of Novel Approaches to Software Engineering, ENASE. IEEE (2014)Google Scholar
  5. 5.
    Boehm, B.W.: Software Engineering Economics, vol. 197. Prentice-hall, Englewood Cliffs (1981)zbMATHGoogle Scholar
  6. 6.
    Weerakkody, V., Currie, W.: Integrating business process reengineering with information systems development: issues & implications. In: van der Aalst, Wil M.P., Weske, M. (eds.) BPM 2003. LNCS, vol. 2678, pp. 302–320. Springer, Heidelberg (2003). Scholar
  7. 7.
    Hammer, M.: Reengineering work: don’t automate, obliterate. Harvard Bus. Rev. 68(4), 104–112 (1990)Google Scholar
  8. 8.
    Kaplan, R.B., Murdock, L.: Rethinking the corporation: core process redesign. Mckinsey Q. 22, 27–44 (1991)Google Scholar
  9. 9.
    Eriksson, E., Magnus, P.: Business modeling with UML. Wiley, New York (2000). Business Patterns at WorkGoogle Scholar
  10. 10.
    Dijkman, R., Jorg, H., Jana, K., (eds) Business Process Model and Notation. Springer, Boston (2011).
  11. 11.
    Pressman, R.S.: Software Engineering: A Practitioner’s Approach. Palgrave Macmillan, London (2005)zbMATHGoogle Scholar
  12. 12.
    OMG: Unified modeling language (OMG UML), version 2.5, Technical report, Object Management Group (2012)Google Scholar
  13. 13.
    Bloch, M., Sven. B., Jürgen, L.: Delivering large-scale IT projects on time, on budget, and on value, McKinsey Quarterly (2012)‏Google Scholar
  14. 14.
    Cruz, E.F., Machado, R.J., Santos, M.Y.: From business process models to use case models: a systematic approach. In: Aveiro, D., Tribolet, J., Gouveia, D. (eds.) EEWC 2014. LNBIP, vol. 174, pp. 167–181. Springer, Cham (2014). Scholar
  15. 15.
    Indulska, M., Recker, J., Rosemann, M., Green, P.: Business process modeling: current issues and future challenges. In: van Eck, P., Gordijn, J., Wieringa, R. (eds.) CAiSE 2009. LNCS, vol. 5565, pp. 501–514. Springer, Heidelberg (2009). Scholar
  16. 16.
    Rajagopal, P., Lee, R., Ahlswede, T., Chiang, C.C., Karolak, D.: A new approach for software requirements elicitation. In: 6th International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing and ACIS International Workshop on Self-Assembling Wireless Network, pp. 32–42. IEEE (2005)Google Scholar
  17. 17.
    Brooks, F.P.: No silver bullet: essence and accidents of software engineering. IEEE Comput. 20, 10–19 (1987)CrossRefGoogle Scholar
  18. 18.
    Eriksson, H.-E., Penker, M.: Business Modeling with UML: Business Patterns at Work. Wiley, Hoboken (2000)Google Scholar
  19. 19.
    Kruchten, P.: The Rational Unified Process – An Introduction. Addison-Wesley, Boston (2000)Google Scholar
  20. 20.
    Davis, A., Dieste, O., Hickey, A., Juristo, N., Moreno, A.M.: Effectiveness of requirements elicitation techniques: empirical results derived from a systematic review. In: 14th IEEE International Requirements Engineering Conference, RE 2006,‏ pp. 179–188. IEEE (2006)Google Scholar
  21. 21.
    Neill, C.J., Laplante, P.A.: Requirements engineering: the state of the practice. IEEE Softw. 20(6), 40–45 (2003)CrossRefGoogle Scholar
  22. 22.
    Berry, D.M., Kamsties, E.: Ambiguity in requirements specification. In: do Prado Leite, J.C.S., Doorn, J.H. (eds) Perspectives on Software Requirements. The Springer International Series in Engineering and Computer Science, vol 753. Springer, Boston (2004).
  23. 23.
    Kitchenham, B.A., Pickard, L., Linkman, S., Jones, P.: A framework for evaluating a software bidding model. Inf. Softw. Technol. 47(11), 747–760 (2005)CrossRefGoogle Scholar
  24. 24.
    Jalote, P.A.: Concise Introduction to Software Engineering. Springer, London (2008). Scholar
  25. 25.
    Mili, H., Tremblay, G., Jaoude, G.B., Lefebvre, É., Elabed, L., Boussaidi, G.E.: Business process modeling languages: sorting through the alphabet soup. ACM Comput. Surv. (CSUR) 43(1), 4 (2010)CrossRefGoogle Scholar
  26. 26.
    Bider, I.: State-oriented business process modeling: principles, theory and practice (Doctoral dissertation, Data-och systemvetenskap) (2002)Google Scholar
  27. 27.
    Hove, S.E., Anda, B.: Experiences from conducting semi-structured interviews in empirical software engineering research. In: 11th IEEE International Software Metrics Symposium, METRICS 2005, pp. 10. IEEE (2005)Google Scholar
  28. 28.
    Shishkov, B., Dietz, J.L.: Deriving use cases from business processes, the advantages of demo. In: ICEIS, no. 3, pp. 138–146 (2003).
  29. 29.
    Turkman, S., Taweel, A.: Business process model driven automatic software requirements generation. In: Shishkov, B. (ed.) BMSD 2019. LNBIP, vol. 356, pp. 270–278. Springer, Cham (2019). Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.Computer ScienceBirzeit UniversityBirzeitPalestine

Personalised recommendations