The How? When? and What? for the Process of Re-planning for Product Releases
Volatility of features and dynamic change in stakeholders’ needs often requires re-planning of an existing release plan to accommodate changes. H2W is a re-planning method that answers the questions of how, when, and what to re-plan of an existing product release strategy. For HOW, a greedy heuristic based on prioritization of candidate features is applied. A value-based re-planning approach is proposed for the WHEN question. For WHAT, a trade-off analysis between the degree of change related to the originally announced release plan and the improvement achievable by replacing existing features with more attractive ones is suggested. At each of the re-planning iterations, H2W either provides a new improved plan or states that an improvement does not exist. As a proof-of-concept, a case study is conducted.
KeywordsRelease planning Re-planning process Change request Volatile requirements Decision support Trade-off analysis
Unable to display preview. Download preview PDF.
- 1.AlBourae, T., Ruhe, G., Moussavi, M.: Lightweight Re-planning of Software Product Releases. In: 14th IEEE International Requirements Engineering Conference Minneapolis/St. Paul, Minnesota, USA (2006)Google Scholar
- 2.Al-Emran, A., Jadallah, A., Moussavi, M., Paikari, E., Pfahl, D., Ruhe, G.: Functionality versus Quality: Application of Predictive Models for Re-planning of Product Releases. Submission for International Conference on Predictor Models PROMISE 2009, Vancouver (2009)Google Scholar
- 6.Jadallah, A.: http://www.ucalgary.ca/~agjadall/ICSP2009
- 8.Kontonya, G., Sommerville, I.: Requirements Engineering: Processes and Techniques. Wiley, Chichester (1998)Google Scholar
- 9.Loconsole, A.: Empirical Studies on Requirement Management Measures. In: Proceedings - 26th International Conference on Software Engineering, ICSE 2004, Edinburgh, United Kingdom (2004)Google Scholar
- 11.Nurmuliani, N., Zowghi, D., Fowell, S.: Analysis of Requirements Volatility During Software Development Life Cycle, Melbourne, Australia (2004)Google Scholar
- 12.Ramil, J.F.: Continual Resource Estimation for Evolving Software. In: Proceedings Conference on Software Maintenance, pp. 289–292 (2003)Google Scholar
- 14.ReleasePlanner, Expert Decisions Inc., http://www.releaseplanner.com
- 16.Stark, G., Skillicorn, A., Ameele, R.: An Examination of the Effects of Requirements Changes on Software Maintenance Releases. Journal of Software Maintenance: Research and Practice (1999)Google Scholar
- 18.Strens, M.R., Sugden, R.C.: Change Analysis: A Step towards Meeting the Challenge of Changing Requirements. In: Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based Systems, pp. 278–283 (1996)Google Scholar
- 20.Van Lamsweerde, A.: Requirements Engineering in the Year 2000: a research perspective. In: Proceedings of the 22nd International Conference on Software Engineering (ICSE 2000), Limerick, Ireland (2000)Google Scholar
- 21.Wiegers, K.E.: Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle, 2nd edn. Microsoft Press (2003)Google Scholar