The How? When? and What? for the Process of Re-planning for Product Releases

  • Anas Jadallah
  • Ahmed Al-Emran
  • Mahmoud Moussavi
  • Guenther Ruhe
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5543)


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.


Release planning Re-planning process Change request Volatile requirements Decision support Trade-off analysis 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 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. 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
  3. 3.
    Bagnall, A.J., Rayward-Smith, V.J., Whittley, I.M.: The Next Release Problem. Information and Software Technology 43, 883–890 (2001)CrossRefGoogle Scholar
  4. 4.
    Cormen, T.H., Leiserson, C.E., Rivest, R.L.: Introduction to Algorithms, Clifford Stein. MIT Press, Cambridge (2007)zbMATHGoogle Scholar
  5. 5.
    Greer, D., Ruhe, G.: Software Release Planning: An Evolutionary and Iterative Approach. Information and Software Technology 46, 243–253 (2004)CrossRefGoogle Scholar
  6. 6.
  7. 7.
    Jung, H.W.: Optimizing Value and Cost in Requirements Analysis. IEEE Software 15, 74–78 (1998)CrossRefGoogle Scholar
  8. 8.
    Kontonya, G., Sommerville, I.: Requirements Engineering: Processes and Techniques. Wiley, Chichester (1998)Google Scholar
  9. 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
  10. 10.
    Ngo-The, A., Ruhe, G.: Optimized Resource Allocation for Software Release Planning. IEEE Transactions on Software Engineering 35, 109–123 (2009)CrossRefGoogle Scholar
  11. 11.
    Nurmuliani, N., Zowghi, D., Fowell, S.: Analysis of Requirements Volatility During Software Development Life Cycle, Melbourne, Australia (2004)Google Scholar
  12. 12.
    Ramil, J.F.: Continual Resource Estimation for Evolving Software. In: Proceedings Conference on Software Maintenance, pp. 289–292 (2003)Google Scholar
  13. 13.
    Regnell, B., Svensson, R.B., Olsson, T.: Supporting Road-mapping of Quality Requirements. IEEE Software 25, 42–47 (2008)CrossRefGoogle Scholar
  14. 14.
    ReleasePlanner, Expert Decisions Inc.,
  15. 15.
    Ruhe, G., Saliu, M.O.: The Art and Science of Software Release Planning. IEEE Software 22, 47–53 (2005)CrossRefGoogle Scholar
  16. 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
  17. 17.
    Steuer, R.E.: Multiple Criteria Optimization: Theory, Computation, and Application. John Wiley, New York (1986)zbMATHGoogle Scholar
  18. 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
  19. 19.
    Van den Akker, M., Brinkkemper, S., Diepen, G., Versendaal, J.: Software Product Release Planning through Optimization and What-If Analysis. Information and Software Technology 50, 101–111 (2008)CrossRefGoogle Scholar
  20. 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. 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

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Anas Jadallah
    • 1
  • Ahmed Al-Emran
    • 1
  • Mahmoud Moussavi
    • 1
  • Guenther Ruhe
    • 1
    • 2
    • 3
  1. 1.Department of Electrical & Computer Engineering Schulich School of EngineeringUniversity of CalgaryCanada
  2. 2.Department of Computer ScienceUniversity of CalgaryCanada
  3. 3.Expert Decisions IncCalgaryCanada

Personalised recommendations