What is important when deciding to include a software requirement in a project or release?

The requirements on software systems are so many that not all requirements may be included in the next development project or the next release. This means that it is necessary to select a set of requirements to implement in the forthcoming project, and hence to postpone the implementation of other requirements to a later point in time. In this selection process different criteria are used. In many cases, the criteria are not officially stated, but rather implicitly used by the decision-makers. However, to be able to support this decision-making process, it is important to know and understand the underlying reasons for the decisions. This paper presents an empirical study of the decision criteria. In particular, the paper focuses on how different perspectives have different influence on the decision-making process. It is concluded that business-oriented and management-oriented criteria are more important than technical concerns related to software architecture, impact analysis, dependency between requirements and software evolution.

[1]  Claes Wohlin,et al.  Applying Decision-Making Models in Requirements Engineering. , 2002 .

[2]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[3]  Des Greer,et al.  Quantitative studies in software release planning under risk and resource constraints , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[4]  Dietmar Pfahl,et al.  Trade-off Analysis for Requirements Selection , 2003, Int. J. Softw. Eng. Knowl. Eng..

[5]  Des Greer,et al.  Software release planning: an evolutionary and iterative approach , 2004, Inf. Softw. Technol..

[6]  J. Favare,et al.  Managing requirements for business value , 2002 .

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

[8]  Björn Regnell,et al.  An industrial survey of requirements interdependencies in software product release planning , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

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

[10]  Claes Wohlin,et al.  Criteria for Selecting Software Requirements to Create Product Value: An Industrial Empirical Study , 2006, Value-Based Software Engineering.

[11]  Barry W. Boehm,et al.  Value-Based Software Engineering: A Case Study , 2003, Computer.

[12]  Claes Wohlin,et al.  Subjective evaluation as a tool for learning from software project success , 2000, Inf. Softw. Technol..

[13]  John M. Favaro.  Managing Requirements for Business Value , 2002, IEEE Softw..

[14]  Claes Wohlin,et al.  The fundamental nature of requirements engineering activities as a decision-making process , 2003, Inf. Softw. Technol..

[15]  Åsa G. Dahlstedt,et al.  Requirements Interdependencies-Moulding the State of Research into a Research Agenda , 2003 .

[16]  Claes Wohlin,et al.  Requirements Mean Decisions! – Research issues for understanding and supporting decision-making in Requirements Engineering , 2001 .

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

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