Michael Felderer
ABSTRACT
Context: Product release decisions are often made ad hoc or not relying on up-to-date information from systematic and analysis-driven process. Often, too much emphasis solely is put into functionality, thereby neglecting the different quality aspects being important for the success of the product. Objective: For a case study project, we quantitatively measure the impact of the analytical and systematic release planning approach Q-EVOLVE II. Method: As an explorative and retrospective case study, we perform optimized planning scenarios and compare them with the actual baseline scenario. Results: For the case study project in an Austrian public health insurance institution, we demonstrate that the analytical and systematic approach Q-EVOLVE II results in a (1) reduced release time, (2) more features implemented in the same time, and (3) better final quality through increased testing activities and less defects slipping through at the time of release. Conclusion: In the context of the studied institution, analytical and systematic planning of product releases considering quality criteria is superior to ad hoc planning ignoring quality.
- G. Ruhe. Product Release Planning. CRC Press, 2010.Google Scholar
Cross Ref
- T. Gorschek, S. Fricker, K. Palm, and S. Kunsman. A lightweight innovation process for software-intensive product development. IEEE Software 27, 37--45, 2010. Google ScholarDigital Library
- B. Boehm and V. R. Basili. Software Defect Reduction Top Top 10 List, 34(1):135--137, 2001. Google ScholarDigital Library
- C. Denger and T. Olsson. Quality assurance in requirements engineering, Engineering and managing software requirements. pp. 163--185, Springer, 2005.Google Scholar
- C. Ebert and S. Brinkkemper. Software product management - An industry evaluation. Journal of Systems and Software 2014 (in press). Google ScholarDigital Library
- ISTQB. Standard glossary of terms used in software testing. Version 2.2. International Software Testing Qualifications Board, Glossary Working Party, 2012.Google Scholar
- E. Bjarnason, P. Runeson, M. Borg, M. Unterkalmsteiner, E. Engström, B. Regnell, G. Sabaliauskaite, A. Loconsole, T. Gorschek, and R. Feldt. Challenges and practices in aligning requirements with verification and validation: a case study of six companies. Empirical Software Engineering, online first, Springer, 2014.Google Scholar
- Z. A. Barmi, A. H. Ebrahimi, and R. Feldt. Alignment of requirements specification and testing: A systematic mapping study. Conference on Software Testing, Verification and Validation Workshops (ICSTW 2011), IEEE, 2011. Google ScholarDigital Library
- M. Svahnberg, T. Gorschek, R. Feldt, R. Torkar, S. B. Saleem, B., and M. U. Shafique. A systematic review on strategic release planning models. Information and Software Technology, 52(3):237--248, 2010. Google ScholarDigital Library
- J. Ho, S. Shawanez, and G. Ruhe. A Prototype Tool Supporting When-to-release Decisions in Iterative Development. 2nd International Workshop on Release Engineering (RELENG), 2014.Google Scholar
- M. Lindgren, R. Land, C. Norström, and A. Wall. Towards a capability model for the software release planning process - Based on a multiple industrial case study. Product-Focused Software Process Improvement. Springer, 2008. Google ScholarDigital Library
- G. Zorn-Pauli, B. Paech, B., T. Beck, H. Karey, and G. Ruhe. Analyzing an Industrial Strategic Release Planning Process--A Case Study at Roche Diagnostics. Requirements Engineering: Foundation for Software Quality, Springer, 2013. Google ScholarDigital Library
- G. Du, J. McElroy, and G. Ruhe. A family of empirical studies to compare informal and optimization-based planning of software releases. Proceedings ESEM 2006, 2006. Google ScholarDigital Library
- R. Berntsson Svensson, P. Lindberg Parker, and B. Regnell. A prototype tool for QUPER to support release planning of quality requirements, Workshop IWSPM 2011, 2011.Google ScholarCross Ref
- P. Runeson, M. Höst, A. Rainer, and B. Regnell. Case Study Research in Software Engineering: Guidelines and Examples. John Wiley & Sons, 2012. Google ScholarDigital Library
- ReleasePlanner, www.releaseplanner.com, last access on July 5, 2014.Google Scholar
- C. Wohlin, P. Runeson, M. Höst, M. C. Ohlsson, B. Regnell, and A. Wesslén. Experimentation in software engineering. Springer, 2012. Google ScholarDigital Library
- A. Wood, Software reliability growth models: assumptions vs. reality, Proceedings International Symposium on Software Reliability Engineering. IEEE, 1997. Google ScholarDigital Library
- M. Nayebi, G. Ruhe. An Open Innovation Approach in Support of Product Release Decisions. CHASE 2014 (Co-located Workshop at ICSE 2014), 2014. Google ScholarDigital Library
Index Terms
- Industrial evaluation of the impact of quality-driven release planning
Recommendations
Strategic Release Planning and Evaluation of Operational Feasibility
HICSS '05: Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 09Strategic planning (or road-mapping) of software releases addresses the assignment of requirements to releases on a strategic level. Effort, finance and risk constraints are considered to determine strategic release plans. The goal is to find an optimal ...
Releasing sooner or later: an optimization approach and its case study evaluation
RELENG '13: Proceedings of the 1st International Workshop on Release EngineeringDecisions about the release date need to balance between the degree of readiness (quality) of the product and the potential competitive advantage and added value of (early) delivery. Based on an existing optimization approach for solving the maximum ...
The Art and Science of Software Release Planning
Release planning is an important and integral part of any incremental product development. It addresses decisions related to selecting and assigning features to a consecutive product releases such that the plan meets important technical, resource, ...
Comments