Can User Stories and Use Cases Be Used in Combination in a Same Project? A Systematic Review

  • Dennis Cohn-MuroyEmail author
  • José Antonio Pow-Sang
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 405)


Requirement elicitation (RE) is one of the main tasks that must be performed in order to guarantee the correct implementation of a software development. Its incorrect specification can cause unnecessary overdue costs for the project and, in some cases, its complete failure. The objective of this paper is to provide a state of the art of the elicitation models that makes simultaneous use of two well-known techniques: the use cases model and user stories. The systematic literature review was chosen as a supportive investigation methodology. From the 45 found publications, the search strategy identified 11 studies and 3 methodological proposals: Athena, K-gileRE and NORMAP. Finally, after having reviewed the literature, it was found that there are a few validated proposals that makes use of the combination of user stories and use cases models. Also, there is not enough information to acknowledge the actual efficacy of combining both techniques.


NFR Non functional requirements Requirement elicitation Requirements engineering Software engineering SLR Systematic literature review Use cases User stories 


  1. 1.
    Boehm, B.W., McClean, R.K., Urfrig, D.B.: Some experience with automated aids to the design of large-scale reliable software. ACM SIGPLAN Not 10, 105–113 (1975)CrossRefGoogle Scholar
  2. 2.
    Standish Group: CHAOS Report (1995)Google Scholar
  3. 3.
    Barbacci, M.R., Ellison, R., Lattanze, A.J., Stafford, J. a., Weinstock, C.B., Wood, W.G.: Quality Attribute Workshops, 3rd edn. (2003)Google Scholar
  4. 4.
    Nord, R.L., Tomayko, J.E.: Software architecture-centric methods and agile development. IEEE Softw. 23, 47–53 (2006)CrossRefGoogle Scholar
  5. 5.
    Alexander, I., Zink, T.: Introduction to systems engineering with use cases. Comput. Control Eng. J. 13, 289–297 (2002)CrossRefGoogle Scholar
  6. 6.
    Gallardo-Valencia, R.E., Olivera, V., Sim, S.E.: Are use cases beneficial for developers using agile requirements? In: 2007 Fifth International Workshop on Comparative Evaluation in Requirements Engineering, pp. 11–22. IEEE (2007)Google Scholar
  7. 7.
    Cockburn, A.: Writing effective use cases (2001)Google Scholar
  8. 8.
    Cohn, M.: User Stories Applied: For Agile Software Development. Addison Wesley Longman Publishing Co., Inc, Redwood City (2004)Google Scholar
  9. 9.
    Winbladh, K., Ziv, H., Richardson, D.J.: Surveying the usability of requirements approaches using a 3-dimensional framework (2008)Google Scholar
  10. 10.
    Kitchenham, B., Charters, S.: Guidelines for performing systematic literature reviews in software engineering. Engineering 2, 1051 (2007)Google Scholar
  11. 11.
    Ahmad, A., Jamshidi, P., Pahl, C.: Protocol for Systematic Literature Review (2012)Google Scholar
  12. 12.
    Wieringa, R., Maiden, N., Mead, N., Rolland, C.: Requirements engineering paper classification and evaluation criteria: a proposal and a discussion. Requir. Eng. 11, 102–107 (2006)CrossRefGoogle Scholar
  13. 13.
    Farid, W.M.: The Normap methodology: lightweight engineering of non-functional requirements for agile processes. In: Proceedings—Asia-Pacific Software Engineering Conference, APSEC, pp. 322–325 (2012)Google Scholar
  14. 14.
    Farid, W.M.: The Normap Methodology: Non-functional Requirements Modeling for Agile Processes (2011)Google Scholar
  15. 15.
    Farid, W.M., Mitropoulos, F.J.: NORMATIC: a visual tool for modeling non-functional requirements in agile processes. In: 2012 Proceedings of IEEE Southeastcon, pp. 1–8. IEEE (2012)Google Scholar
  16. 16.
    Farid, W.M., Mitropoulos, F.J.: Novel lightweight engineering artifacts for modeling non-functional requirements in agile processes. In: 2012 Proceedings of IEEE Southeastcon, pp. 1–7. IEEE (2012)Google Scholar
  17. 17.
    Farid, W.M., Mitropoulos, F.J.: Visualization and scheduling of non-functional requirements for agile processes. In: Conference Proceedings—IEEE SOUTHEASTCON (2013)Google Scholar
  18. 18.
    Gallardo-Valencia, R.E., Olivera, V., Sim, S.E.: Practical experiments are informative, but never perfect. In: Proceedings of the 1st ACM International Workshop on Empirical Assessment of Software Engineering Languages and Technologies Held in Conjunction with the 22nd IEEE/ACM International Conference on Automated Software Engineering (ASE) 2007—WEASELTech ’07, pp. 37–42. ACM Press, New York, NY, USA (2007)Google Scholar
  19. 19.
    Hvalshagen, M., Khatri, V., Venkataraman, R.: Understanding use cases: Harnessing the power of narratives to comprehend application domains. In: 14th Americas Conference on Information Systems, AMCIS 2008, pp. 3328–3335 (2008)Google Scholar
  20. 20.
    Kumar, M., Ajmeri, N., Ghaisas, S.: Towards knowledge assisted agile requirements evolution. In: Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering—RSSE ’10, pp. 16–20. ACM Press, New York, NY, USA (2010)Google Scholar
  21. 21.
    Laporti, V., Borges, M.R.S., Braganholo, V.: Athena: A collaborative approach to requirements elicitation. Comput. Ind. 60, 367–380 (2009)CrossRefGoogle Scholar
  22. 22.
    Liskin, O.: How artifacts support and impede requirements communication. In: 21st International Working Conference, REFSQ 2015, pp. 132–147 (2015)Google Scholar
  23. 23.
    Zarour, M., Abran, A., Desharnais, J.-M., Alarifi, A.: An investigation into the best practices for the successful design and implementation of lightweight software process assessment methods: a systematic literature review. J. Syst. Softw. 101, 180–192 (2015)CrossRefGoogle Scholar
  24. 24.
    Jedlitschka, A., Ciolkowski, M., Pfahl, D.: Reporting experiments in software engineering. In: Guide to Advanced Empirical Software Engineering, pp. 201–228 (2008)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  1. 1.Escuela de PosgradoPontificia Universidad Católica del Perú, PUCPLimaPeru

Personalised recommendations