Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research

In early phases of the software cycle, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper presents results of a systematic review of literature, which investigates how existing methods approach the problem of requirements prioritization based on benefit and cost. From this review, it derives a set of under-researched issues which warrant future efforts and sketches an agenda for future research in this area.

[1]  Miss A.O. Penney.  (b) , 1974, The New Yale Book of Quotations.

[2]  Ralph L. Keeney,et al.  Decisions with multiple objectives: preferences and value tradeoffs , 1976 .

[3]  R. L. Keeney,et al.  Decisions with Multiple Objectives: Preferences and Value Trade-Offs , 1977, IEEE Transactions on Systems, Man, and Cybernetics.

[4]  Alfred V. Aho,et al.  Data Structures and Algorithms , 1983 .

[5]  A. Strauss,et al.  Basics of Qualitative Research , 1992 .

[6]  Jean-Claude Laprie,et al.  The KAT (Knowledge-Action-Transformation) Approach to the Modeling and Evaluation of Reliability and Availability Growth , 1991, IEEE Trans. Software Eng..

[7]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .

[8]  Sarah Brocklehurst,et al.  New Ways to Get Accurate Reliability Measures , 1992, IEEE Softw..

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

[10]  Pamela Jordan.  Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[11]  S French,et al.  Multicriteria Methodology for Decision Aiding , 1996 .

[12]  Jean-Marc Desharnais,et al.  A comparison of software effort estimation techniques: Using function points with neural networks, case-based reasoning and regression models , 1997, J. Syst. Softw..

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

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

[15]  Ralph L. Keeney,et al.  Foundations for making smart decisions , 1999 .

[16]  R.L. Keeney,et al.  Making smart choices in engineering , 1999, IEEE Spectrum.

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

[18]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[19]  Barry W. Boehm.  Safe and Simple Software Cost Analysis , 2000, IEEE Software.

[20]  Barry W. Boehm,et al.  Software development cost estimation approaches — A survey , 2000, Ann. Softw. Eng..

[21]  Roel Wieringa,et al.  The declarative problem frame: designing systems that create and use norms , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[22]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[23]  Mark Klein,et al.  Quantifying the costs and benefits of architectural decisions , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[24]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

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

[26]  Shari Lawrence Pfleeger,et al.  Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..

[27]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[28]  Ian Thomas,et al.  Business-Driven Product Planning Using Feature Vectors and Increments , 2002, IEEE Softw..

[29]  Shawn A. Butler.  Security attribute evaluation method: a cost-benefit approach , 2002, ICSE '02.

[30]  Alan M. Davis,et al.  The Art of Requirements Triage , 2003, Computer.

[31]  Martin S. Feather,et al.  Quantitative risk-based requirements reasoning , 2003, Requirements Engineering.

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

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

[34]  Nancy R. Mead,et al.  SQUARE Project: Cost/Benefit Analysis Framework for Information Security Improvement Projects in Small Companies , 2004 .

[35]  Rahul Telang,et al.  An ounce of prevention vs. a pound of cure: How can we measure the value of IT security solutions? , 2004 .

[36]  Barbara Paech,et al.  Task-Driven Requirements in Object-Oriented Development , 2004 .

[37]  Peter H. N. de With,et al.  Resolving requirement conflicts through non-functional decomposition , 2004, Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004).

[38]  Barry W. Boehm,et al.  The ROI of software dependability: The iDAVE model , 2004, IEEE Software.

[39]  Emilia Mendes,et al.  A systematic review of Web engineering research , 2005, 2005 International Symposium on Empirical Software Engineering, 2005..

[40]  Barbara Paech,et al.  Quality Misuse , 2005 .

[41]  Martin Glinz,et al.  Rethinking the Notion of Non-Functional Requirements , 2005 .

[42]  Rick Kazman,et al.  From requirements negotiation to software architecture decisions , 2005, Inf. Softw. Technol..

[43]  Thomas Olsson,et al.  Non-functional requirements in industry - three case studies adopting an experience-based NFR method , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[44]  Barbara Paech,et al.  Elicitation and Documentation of Non-Functional Requirements for Sociotechnical Systems , 2005 .

[45]  Tom Gilb,et al.  Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, And Software Engineering Using Planguage , 2005 .

[46]  John Mylopoulos,et al.  Goal-Oriented Requirements Engineering, Part II , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[47]  Patrik Berander,et al.  Hierarchical Cumulative Voting (hcv) - Prioritization of Requirements in Hierarchies , 2006, Int. J. Softw. Eng. Knowl. Eng..

[48]  Tim Menzies,et al.  Experiences using Visualization Techniques to Present Requirements, Risks to Them, and Options for Risk Mitigation , 2006, 2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop).

[49]  Camille Salinesi,et al.  Choosing a Prioritization Method-Case of IS Security Improvement , 2006, CAiSE Forum.

[50]  Christof Ebert,et al.  Understanding the product life cycle: four key requirements engineering techniques , 2006, IEEE Software.

[51]  Barbara Paech,et al.  MOQARE: misuse-oriented quality requirements engineering , 2008, Requirements Engineering.

[52]  Martin J. Shepperd,et al.  Software project economics: a roadmap , 2007, Future of Software Engineering (FOSE '07).

[53]  Joachim Karlsson,et al.  Improved practical support for large-scale requirements prioritising , 1997, Requirements Engineering.

[54]  Magne Jørgensen,et al.  A Systematic Review of Software Development Cost Estimation Studies , 2007, IEEE Transactions on Software Engineering.

[55]  Alain Abran,et al.  Non-Functional Requirements: Size Measurement and Testing with COSMIC-FFP , 2007 .

[56]  John Mylopoulos.  Goal-Oriented Requirements Engineering , 2008, CIbSE.

[57]  Andrea Herrmann,et al.  Requirements Prioritization Based on Benefit and Cost Prediction: A Method Classification Framework , 2008, 2008 34th Euromicro Conference Software Engineering and Advanced Applications.

[58]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.