A Comparison among Various Techniques to Prioritize the Requirements

In commercial software system development, software vendors often face the many difficulties to deal with large amount of requirements that enter the company every day. It is not possible to satisfy all the requirements in given constraint like time, cost, etc. hence there is a need to select the requirements that are more important. Requirements prioritization is a way that can play important role in the selection of requirements. Selecting the right order of requirements for product release depends on how successfully the requirements are prioritized. There are different requirement prioritization methods available with different characteristics. In this paper, we take a closer look of 9 different Requirement Prioritization techniques, namedas Fuzzy Analytical hierarchy process(FAHP), Classical Analytical hierarchy process(AHP), Hierarchy Analytical hierarchy process, minimal spanning tree, bubble sort, binary search tree, priority groups, planning game, and 100 point method. The Criteria used that are used for comparison are: required completion time, ease of use, reliability, and required number of comparison.

[1]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[2]  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.

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

[4]  M. Bohanec,et al.  The Analytic Hierarchy Process , 2004 .

[5]  Karl E. Wiegers.  First Things First: Prioritizing Requirements , 1999 .

[6]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[7]  Claes Wohlin,et al.  Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning , 2004, ICSE 2004.

[8]  Sarah Hatton,et al.  Early Prioritisation of Goals , 2007, ER Workshops.

[9]  Brian A. Malloy,et al.  AN APPROACH TO AUTOMATE REQUIREMENTS ELICITATION AND SPECIFICATION , 2003 .

[10]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[11]  Mohammad Shabbir Hasan,et al.  An Evaluation of Software Requirement Prioritization Techniques , 2010 .

[12]  Slinger Jansen,et al.  Customer Involvement in Requirements Management: Lessons from Mass Market Software Development , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[13]  Marjo Kauppinen,et al.  Empirical Evaluation of Two Requirements Prioritization Methods in Product Development Projects , 2004, EuroSPI.

[14]  Jawed I. A. Siddiqi,et al.  Requirements Engineering: The Emerging Wisdom , 1996, IEEE Softw..

[15]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[16]  Dar-Biau Liu,et al.  Metrics for requirements engineering , 1995, J. Syst. Softw..

[17]  Neil A. M. Maiden,et al.  Acquiring COTS Software Selection Requirements , 1998, IEEE Softw..

[18]  John Beidler,et al.  Data Structures and Algorithms , 1996, Wiley Encyclopedia of Computer Science and Engineering.

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