ABSTRACT
Efficient consideration of all stakeholders' needs and perspectives in a software project is a key challenge, especially when prioritizing the software requirements to be developed in the next software release. This paper presents a new requirements prioritization approach that aims to collectively prioritize software requirements based on their ratings expressed from different stakeholders. The proposed approach follows the steps of a value-oriented process in which multiple and possibly distributed stakeholders assess the values of candidate requirements with respect to various prioritization criteria. The approach applies a group-based, fuzzy multi-criteria technique requiring from involved stakeholders to evaluate requirements using linguistic terms. Stakeholders' linguistic evaluations are aggregated to collectively derive more objective and reasonable assessments on the final requirements' priorities1.
- N.R. Mead. 2006. Requirements Prioritization Introduction. Software Engineering Institute Web Publication, Carnegie Mellon University, Pittsburgh.Google Scholar
- P. Achimugu, A. Selamat, R. Ibrahim, and M. N. Mahrin. 2014. A Systematic Literature Review of Software Requirements Prioritization Research. Information and Software Technology, 56(6), 568--585. Google ScholarDigital Library
- R. B. Svensson, T. Gorschek, B. Regnell, R. Torkar, A. Shahrokni, R. Feldt, and A. Aurum. 2011. Prioritization of Quality Requirements: State of Practice in Eleven Companies. In Proceedings of the 19th IEEE International Requirements Engineering Conference (RE), IEEE, 69--78. Google ScholarDigital Library
- J. Karlsson, C. Wohlin, and B. Regnell. 1998. An Evaluation of Methods for Prioritizing Software Requirements. Information and Software Technology, 39(14), 939--947.Google ScholarCross Ref
- J. Karlsson, and K. Ryan. 1997. A Cost-Value Approach for Prioritizing Requirements. IEEE Software, 14(5), 67--74. Google ScholarDigital Library
- M. Babar, M. Ramzan, and S. Ghayyur. 2011. Challenges and Future Trends in Software Requirements Prioritization. In Proceedings of the Computer Networks and Information Technology (ICCNIT 2011), IEEE, 319--324.Google Scholar
- P. Berander, and A. Andrews. 2005. Requirements Prioritization. In Engineering and Managing Software Requirements, A. Aurum and C. Wohlin (Eds.). Springer, 69--94.Google Scholar
- D. Leffingwell, and D. Widrig. 2003. Managing Software Requirements: A Use Case Approach. 2nd ed. Addison-Wesley, Boston. Google ScholarDigital Library
- L. Lehtola, M. Kauppinen, and S. Kujala. 2004. Requirements Prioritization Challenges in Practice. In Product Focused Software Process Improvement. Springer, 497--508.Google Scholar
- S. L. Lim, and A. Finkelstein. 2012. StakeRare: Using Social Networks and Collaborative Filtering for Large-Scale Requirements Elicitation. IEEE Transactions on Software Engineering, 38(3), 707--735. Google ScholarDigital Library
- A. Ejnioui, C. Otero, and A. Qureshi, 2012. Software Requirement Prioritization Using Fuzzy Multi-Attribute Decision making. In Proceedings of the Open Systems Conference (ICOS), IEEE, 1--6.Google Scholar
- D. Lima, F. Freitas, G. Campos, and J. Souza. 2011. A Fuzzy Approach to Requirements Prioritization. In Search Based Software Engineering, Springer, 64--69. Google ScholarDigital Library
- J. Azar, R. K. Smith, and D. Cordes. 2007. Value-Oriented Requirements Prioritization in a Small Development Organization. IEEE Software, 24(1), 32--27. Google ScholarDigital Library
- F. Herrera, and L. Martinez. 2000. A 2-Tuple Fuzzy Linguistic Representation Model for Computing with Words. IEEE Transactions on Fuzzy Systems, 8(6), 746--752. Google ScholarDigital Library
- L. Martinez, and F. Herrera. 2012. An Overview on the 2-Tuple Linguistic Model for Computing with Words in Decision Making: Extensions, Applications and Challenges. Information Sciences, 207(10), 1--18. Google ScholarDigital Library
- K. Schwaber. 2004. Agile Project Management with Scrum. Microsoft Professional. Google ScholarDigital Library
- T. L. Saaty. 1980. The Analytical Hierarchy Process, McGraw-Hill.Google Scholar
- F. Ackermann, and C. Eden. 2011. Strategic Management of Stakeholders: Theory and Practice. Long Range Planning, 44, 179--196.Google ScholarCross Ref
- K. Pohl. 2010. Requirements Engineering, Fundamentals, Principles, and Techniques. Springer. Google ScholarDigital Library
- F. Herrera, L. Martinez, and P. J. Sanchez. 2005. Managing Non-Homogeneous Information in Group Decision Making. European Journal of Operational Research, 166 (1), 115--132.Google ScholarCross Ref
- X. Liao, Y. Li, and B. Lu. 2007. A Model for Selecting an ERP System based on Linguistic Information Processing. Information Systems, 32(7), 1005--1017. Google ScholarDigital Library
- S. Padmanabhuni, B. Boehm, S. S. Payyavula, and N. Kukreja. 2012. Selecting an Appropriate Framework for Value-based Requirements Prioritization. In Proceedings of the 20th IEEE International Requirements Engineering Conference (RE), IEEE, 303--308. Google ScholarDigital Library
- M. Dabbagh, and S. P. Lee. 2014. An Approach for Integrating the Prioritization of Functional and Nonfunctional Requirements. The Scientific World Journal, article ID 737626, 13 pages.Google Scholar
- J. J., Buckley. 1984. The Multiple Judge, Multiple Criteria Ranking Problem: A Fuzzy Set Approach. Fuzzy Sets and Systems, 13(1), 25--37.Google ScholarCross Ref
- K.E., Wiegers. 1999. First Things First: Prioritizing Requirements. Software Development, 7(9), 48--53. Google ScholarDigital Library
- P. Gruenbacher. 2000. Collaborative Requirements Negotiation with Easy Win Win. In Proceedings of the 2nd International Workshop on the Requirements Engineering Process, IEEE. Google ScholarDigital Library
- R. M. Rodriguez, L. Martinez, and F. Herrera. 2012. Hesitant Fuzzy Linguistic Term Sets. IEEE Transactions on Fuzzy Sets and Systems, 20(1), 109--119. Google ScholarDigital Library
Index Terms
- Using Fuzzy Linguistic 2-Tuples to Collectively Prioritize Software Requirements based on Stakeholders' Evaluations
Recommendations
Model-based prioritization in business-process-driven software development
RE '12: Proceedings of the 2012 IEEE 20th International Requirements Engineering Conference (RE)Requirements engineers in business-process-driven software development are faced with the challenge of letting stakeholders determine which requirements are actually relevant for early business success and should be considered first or even at all ...
Software requirements prioritization and selection using linguistic tools and constraint solvers--a controlled experiment
Implementing the entire set of requirements for a software system is often not feasible owing to time and resource limitations. A key driver for successful delivery of any software system is the ability to prioritize the large number of requirements. ...
Requirements Prioritization Based on Benefit and Cost Prediction: A Method Classification Framework
SEAA '08: Proceedings of the 2008 34th Euromicro Conference Software Engineering and Advanced ApplicationsIn early phases of the software development process, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper induces a conceptual model of requirements ...
Comments