Release Planning with Feature Trees: Industrial Case

[Context and motivation] Requirements catalogues for software release planning are often not complete and homogeneous. Current release planning approaches, however, assume such commitment to detail --- at least implicitly. [Question/problem] We evaluate how to relax these expectations, while at the same time reducing release planning effort and increasing decision-making flexibility. [Principal ideas/results] Feature trees capture AND, OR, and REQUIRES relationships between requirements. Such requirements structuring can be used to hide incompleteness and to support abstraction. [Contribution] The paper describes how to utilize feature trees for planning the releases of an evolving software solution and evaluates the effects of the approach on effort, decision-making, and trust with an industrial case.

[1]  Samuel Fricker,et al.  Variability-Based Release Planning , 2011, ICSOB.

[2]  Marjo Kauppinen,et al.  Suitability of requirements prioritization methods for market-driven software product development , 2006, Softw. Process. Improv. Pract..

[3]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .

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

[5]  Martin Glinz,et al.  Feature unweaving: Efficient variability extraction and specification for emerging software product lines , 2010, 2010 Fourth International Workshop on Software Product Management.

[6]  Klaus Pohl,et al.  Software Product Line Engineering , 2005 .

[7]  Sjaak Brinkkemper,et al.  An integrated approach for requirement selection and scheduling in software release planning , 2010, Requirements Engineering.

[8]  Björn Regnell,et al.  A market-driven requirements engineering process: Results from an industrial process improvement programme , 1998, Requirements Engineering.

[9]  Günther Ruhe,et al.  The art and science of software release planning , 2005, IEEE Software.

[10]  Björn Regnell,et al.  Supporting Roadmapping of Quality Requirements , 2008, IEEE Software.

[11]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[12]  Al Davis.  Keynote: Just Enough Requirements Management for Web Engineering , 2005, ICWE.

[13]  Jonathan Grudin,et al.  Personas: practice and theory , 2003, DUX '03.

[14]  David Probert,et al.  Strategic Roadmapping: A Workshop-based Approach for Identifying and Exploring Strategic Issues and Opportunities , 2007 .

[15]  Robert Phaal,et al.  Technology roadmapping—A planning framework for evolution and revolution , 2004 .

[16]  I. van de Weerd,et al.  SPM Maturity Matrix , 2010 .

[17]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.

[18]  Ian Sommerville,et al.  Requirements engineering with viewpoints , 1996, Softw. Eng. J..

[19]  Tony Gorschek,et al.  Handshaking with Implementation Proposals: Negotiating Requirements Understanding , 2010, IEEE Software.

[20]  Alan M. Davis,et al.  Just Enough Requirements Management: Where Software Development Meets Marketing , 2005 .

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

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

[23]  Mike Cohn,et al.  Agile Estimating and Planning , 2005 .

[24]  Claes Wohlin,et al.  What is important when deciding to include a software requirement in a project or release? , 2005, 2005 International Symposium on Empirical Software Engineering, 2005..

[25]  Günther Ruhe,et al.  Intelligent Support for Software Release Planning , 2004, PROFES.

[26]  A. Andrews,et al.  4 Requirements Prioritization , .

[27]  Didar Zowghi,et al.  Requirements Elicitation: A Survey of Techniques, Approaches, and Tools , 2005 .

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

[29]  Pierre-Yves Schobbens,et al.  Generic semantics of feature diagrams , 2007, Comput. Networks.

[30]  Slinger Jansen,et al.  The Agile Requirements Refinery: Applying SCRUM Principles to Software Product Management , 2009, 2009 Third International Workshop on Software Product Management.

[31]  Robert M. Davison,et al.  Principles of canonical action research , 2004, Inf. Syst. J..

[32]  Pierre-Yves Schobbens,et al.  What ' s in a Feature ? A Requirements Engineering Perspective , 2008 .

[33]  Björn Regnell,et al.  Post-release analysis of requirements selection quality - an industrial case study , 2003 .

[34]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[35]  Björn Regnell,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007, Inf. Softw. Technol..

[36]  Casper Lassenius,et al.  An Approach to Product Roadmapping in Small Software Product Businesses , 2002 .

[37]  R. Feldt,et al.  A systematic review on strategic release planning models , 2010, Inf. Softw. Technol..

[38]  Klaus Pohl,et al.  Software Product Line Engineering - Foundations, Principles, and Techniques , 2005 .