Understanding requirement prioritization artifacts: a systematic mapping study

Original Article


The importance of prioritizing requirements stems from the fact that not all requirements can usually be met with available time and resource constraints. Efficient and trustworthy methods for prioritizing requirements are therefore in high demand. In this article, we present results of a systematic mapping study in order to appreciate the different considerations that have influenced prioritization of software requirements, identify the various types of artifacts proposed toward prioritizing software requirements, and examine certain characterizations of these artifacts. The results emphasize the heightened attention the domain of requirement prioritization has received in recent years. On the basis of this study, we are able to provide the following inferences regarding possible future research trajectories in software requirement prioritization artifacts: (1) focus on frameworks and tools; (2) emphasis on specialization; and (3) proposition of theory-based artifacts. Additional research possibilities are also pointed out at the end and are expected to stimulate further research on the topic.


Requirement prioritization Content analysis Systematic mapping study Software engineering 


  1. 1.
    Herrmann A, Daneva M (2008) Requirements prioritization based on benefit and cost prediction: an agenda for future research. In: 16th IEEE international requirements engineering (RE’08). IEEE, pp 125–134Google Scholar
  2. 2.
    Kotonya G, Sommerville I (1998) Requirements engineering: processes and techniques. Wiley, ChichesterGoogle Scholar
  3. 3.
    Committee ICSSES, Electronics Engineers I, Board I-SS (1998) IEEE recommended practice for software requirements specifications: approved 25 June 1998, vol 830. IEEEGoogle Scholar
  4. 4.
    Karlsson J, Wohlin C, Regnell B (1998) An evaluation of methods for prioritizing software requirements. Inf Softw Technol 39(14):939–947CrossRefGoogle Scholar
  5. 5.
    Achimugu P, Selamat A, Ibrahim R, Mahrin MNR (2014) A systematic literature review of software requirements prioritization research. Inf Softw Technol 56(6):568–585CrossRefGoogle Scholar
  6. 6.
    Kukreja N, Payyavula SS, Boehm B, Padmanabhuni S (2012) Selecting an appropriate framework for value-based requirements prioritization: a case study. In: 20th IEEE international requirements engineering conference, Chicago, IL, USAGoogle Scholar
  7. 7.
    March ST, Smith GF (1995) Design and natural science research on information technology. Decis Support Syst 15(4):251–266CrossRefGoogle Scholar
  8. 8.
    Khan KA (2006) A systematic review of software requirements prioritization. Blekinge Institute of Technology, RonnebyGoogle Scholar
  9. 9.
    Babar MI, Ramzan M, Ghayyur SAK (2011) Challenges and future trends in software requirements prioritization. In: International conference on computer networks and information technology (ICCNIT). IEEE, pp 319–324Google Scholar
  10. 10.
    Pergher M, Rossi B (2013) Requirements prioritization in software engineering: a systematic mapping study. In: IEEE, pp 40–44Google Scholar
  11. 11.
    Perini A, Susi A, Ricca F, Bazzanella C (2007) An empirical study to compare the accuracy of AHP and CBRanking techniques for requirements prioritization. In: Fifth international workshop on comparative evaluation in requirements engineering. IEEE, pp 23–35Google Scholar
  12. 12.
    Pitangueira AM, Maciel RSP, Barros M (2015) Software requirements selection and prioritization using SBSE approaches: a systematic review and mapping of the literature. J Syst Softw 103(May):267–280CrossRefGoogle Scholar
  13. 13.
    Riegel N, Doerr J (2015) A systematic literature review of requirements prioritization criteria. In: Fricker SA, Schneider K (eds) Requirements engineering: foundation for software quality. Springer, Berlin, pp 300–317Google Scholar
  14. 14.
    Sher F, Jawawi DNA, Mohamad R, Babar MI (2014) Requirements prioritization techniques and different aspects for prioritization a systematic literature review protocol. In: 8th Malaysian software engineering conference. IEEE, pp 31–36Google Scholar
  15. 15.
    Budgen D, Turner M, Brereton P, Kitchenham B (2008) Using mapping studies in software engineering. In: Proceedings of the PPIG. Lancaster University, pp 195–204Google Scholar
  16. 16.
    Petersen K, Feldt R, Mujtaba S, Mattsson M (2008) Systematic mapping studies in software engineering. In: 12th International conference on evaluation and assessment in software engineering (EASE), p 1Google Scholar
  17. 17.
    Downeâ-Wamboldt B (1992) Content analysis: method, applications, and issues. Health Care Women Int 13(3):313–321CrossRefGoogle Scholar
  18. 18.
    Higgins JPT, Green S (2011) Cochrane handbook for systematic reviews of interventions version 5.1. 0 [updated March 2011]. The Cochrane CollaborationGoogle Scholar
  19. 19.
    Kitchenham B, Pretorius R, Budgen D, Pearl Brereton O, Turner M, Niazi M, Linkman S (2010) Systematic literature reviews in software engineering: a tertiary study. Inf Softw Technol 52(8):792–805CrossRefGoogle Scholar
  20. 20.
    Berander P, Andrews A (2005) Requirements prioritization. In: Aurum A, Wohlin C (eds) Engineering and managing software requirements. Springer, Berlin, pp 69–94CrossRefGoogle Scholar
  21. 21.
    Cavanagh S (1997) Content analysis: concepts, methods and applications. Nurse Res 4(3):5–13CrossRefGoogle Scholar
  22. 22.
    Miles MB, Huberman AM (1994) Qualitative data analysis: an expanded sourcebook. Sage Publications, Thousand Oaks, CAGoogle Scholar
  23. 23.
    Hevner AR, March ST, Park J, Ram S (2004) Design science in information systems research. MIS Q 28(1):75–105Google Scholar
  24. 24.
    Offermann P, Blom S, Schönherr M, Bub U (2010) Artifact types in information systems design science—a literature review. In: Winter R, Zhao JL, Aier S (eds) Global perspectives on design science research. Springer, Berlin, pp 77–92CrossRefGoogle Scholar
  25. 25.
    Berge C (1958) La theorie des graphes, vol II. Collection Universitaire de Mathématiques. Dunod, ParisGoogle Scholar
  26. 26.
    Köksalan MM, Wallenius J, Zionts S (2011) Multiple criteria decision making: from early history to the 21st century. World Scientific Publishing Co. Pte. Ltd., SingaporeCrossRefGoogle Scholar
  27. 27.
    Xu D-L, Yang J-B, Wang Y-M (2006) The evidential reasoning approach for multi-attribute decision analysis under interval uncertainty. Eur J Oper Res 174(3):1914–1943CrossRefMATHGoogle Scholar
  28. 28.
    Aasem M, Ramzan M, Jaffar A (2010) Analysis and optimization of software requirements prioritization techniques. In: International conference on information and emerging technologies (ICIET). IEEE, pp 1–6Google Scholar
  29. 29.
    Moisiadis F (2002) The fundamentals of prioritising requirements. In: Proceedings of the systems engineering, test and evaluation conference (SETE’2002). Citeseer, pp 108–119Google Scholar
  30. 30.
    Svensson RB, Gorschek T, Regnell Br, Torkar R, Shahrokni A, Feldt R, Aurum AK (2011) Prioritization of quality requirements: state of practice in eleven companies. In: IEEE, pp 69–78Google Scholar
  31. 31.
    Gregor S (2009) Building theory in the sciences of the artificial. Paper presented at the 4th international conference on design science research in information systems and technology, Philadelphia, PA, USA, May 7–8, 2009Google Scholar
  32. 32.
    Riedl C (2011) Tool-supported innovation management in service ecosystems. Gabler Verlag, WiesbadenCrossRefGoogle Scholar
  33. 33.
    Davis A (2013) Just enough requirements management: where software development meets marketing. Addison-Wesley, New YorkGoogle Scholar

Copyright information

© Springer-Verlag London 2016

Authors and Affiliations

  1. 1.Information Systems DepartmentXavier Institute of Management (XIMB)BhubaneswarIndia

Personalised recommendations