Suitability of requirements prioritization methods for market-driven software product development

In a company producing off-the-shelf software for mass markets, the future development steps of the products cannot be negotiated with one or few customers. The decisions concerning the priorities of the requirements must be made within the company, the developer bearing all the financial risks included. This means that finding the right priorities for the requirements is important. However, requirements prioritization is recognized as a difficult activity in software product development. The literature offers methods for requirements prioritization, but many authors report that practices in companies are mostly informal. In this study, we evaluated two requirements prioritization methods in industrial product development projects. In the first case, the users of the system evaluated the pair-wise comparison technique for prioritizing user needs. In the second case, practitioners evaluated Wiegers' method for change requests. In addition, we interviewed 11 practitioners from 6 companies about their current requirements prioritization practices and the models that they use as a basis of their prioritization decisions. Our findings indicate that prioritization methods may have limited ability to support decision-making in a complex area like requirements prioritization in market-driven product development. In addition, there are practical difficulties in the usage of methods, and therefore, prioritization results should be taken more as being indicative than as an ultimate truth. Copyright © 2006 John Wiley & Sons, Ltd.

[1]  Ian Sommerville,et al.  Improving Market-Driven RE Processes , 1999 .

[2]  Pete Sawyer,et al.  Packaged Software: Challenges for RE , 2000 .

[3]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

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

[5]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

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

[7]  N. Kano,et al.  Attractive Quality and Must-Be Quality , 1984 .

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

[9]  Björn Regnell,et al.  Challenges in Market-Driven Requirements Engineering - an Industrial Interview Study , 2002 .

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

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

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

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

[14]  Ian Sommerville,et al.  Software engineering (5th ed.) , 1995 .

[15]  Martti Mäntylä,et al.  Studying Users for Developing Usable and Useful Products. , 2000 .

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

[17]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[18]  Mark T True,et al.  Software Requirements , 2005 .

[19]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.

[20]  Ivy Hooks,et al.  What Is A Requirement , 1993 .

[21]  Colin Potts,et al.  Invented requirements and imagined customers: requirements engineering for off-the-shelf software , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[22]  Benjamin L. Kovitz,et al.  Practical Software Requirements: A Manual of Content and Style , 1998 .