Requirement Prioritization: A Study and Proposed Framework

Requirements may be defined as a demand or need. In software engineering, a requirement is a description of what a system should do. Requirement prioritization process is used to determine which candidate requirement of a software project should be included in a certain release, for this purpose different techniques are used. In this paper we have proposed a framework to prioritize the software requirements. The proposed framework will rank the requirements by the relative level of value, cost, efforts and threat associated with each requirement.

[1]  Des Greer,et al.  Prioritisation of system changes using cost-benefit and risk assessments , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[2]  Joachim Karlsson,et al.  Software requirements prioritizing , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[3]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[4]  Mohd. Sadiq,et al.  An Approach for Eliciting Software Requirements and its Prioritization Using Analytic Hierarchy Process , 2009, 2009 International Conference on Advances in Recent Technologies in Communication and Computing.

[5]  Donald Firesmith,et al.  Prioritizing Requirements , 2004, J. Object Technol..

[6]  Claes Wohlin,et al.  An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..

[7]  R. Ramanathan,et al.  Group preference aggregation methods employed in AHP: An evaluation and an intrinsic process for deriving members' weightages , 1994 .

[8]  M. Tech,et al.  Elicitation and Prioritization of Software Requirements , 2009 .

[9]  Alan M. Davis,et al.  Elicitation technique selection: how do experts do it? , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[10]  Randy K. Smith,et al.  Value-Oriented Requirements Prioritization in a Small Development Organization , 2007, IEEE Software.

[11]  Andreas Rausch,et al.  Journal of Object Technology , 2002 .

[12]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

[13]  Mohd. Sadiq,et al.  Elicitation and Prioritization of Software Requirements , 2009 .

[14]  Marjo Kauppinen,et al.  Requirements Prioritization Challenges in Practice , 2004, PROFES.

[15]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[16]  Claes Wohlin,et al.  A product management challenge: Creating software product value through requirements selection , 2008, J. Syst. Archit..

[17]  Des Greer,et al.  Towards an evolutionary software delivery strategy based on soft systems and risk analysis , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.