Intelligent Support for Software Release Planning
One of the most prominent issues involved in incremental software development is to decide upon the most appropriate software release plans taking into account all explicit and implicit objectives and constraints. Such decisions have become even more complicated in the presence of large number of stakeholders such as different groups of users, managers, or developers. However, early involvement of customers and understanding of their real needs is one of the core success factors of software business .
This paper introduces a six step process model for release planning. It is inspired by the Quality Improvement Paradigm , as release planning is a learning and improvement process as well. Emphasis is on proposing the tool support implementing this process. The use of the intelligent decision support tool ReleasePlannerTM is presented by comparing a baseline scenario reflecting current state-of-the practice of release planning with a supposed improvement scenario obtained after usage of the tool. Initial experience from a real-world environment at iGrafx Corel Inc. is used to validate the improvement scenario.
KeywordsProject Manager Release Planning Requirement Engineer Effort Estimate Stakeholder Negotiation
Unable to display preview. Download preview PDF.
- 2.Basili, V., Caldiera, G., Rombach, D.: Experience Factory. In: Marciniak, J. (ed.) Encyclopedia of Software Engineering, vol. 1, pp. 511–519 (2001)Google Scholar
- 3.Boehm, B., Grunbacher, P.: Briggs: Developing Groupware for Requirements Negotiation: Lessons learned. IEEE Software, 46–55 (May/June 2001)Google Scholar
- 5.Greer, D., Ruhe, G.: Software Release Planning: An Evolutionary and Iterative Approach. Accepted for publication in Information and Software Technology (2004)Google Scholar
- 6.Gruenbacher, P.: Collaborative Requirement Negotiation with Easy WinWin. IEEE Software, 954–958 (2000)Google Scholar
- 8.Karlsson, J.: Software requirements prioritizing. In: Proceedings of the Second International Conference on Requirements Engineering, pp. 110–116 (1996)Google Scholar
- 9.Larman, C.: Agile & Iterative Development, A Manager’s Guide. Addison-Wesley, Reading (2003)Google Scholar
- 10.Nuseibeh, B., Easterbrook, S.: Requirements Engineering: a Roadmap. Proceedings of “The Future of Software Engineering”, 35–46 (May 2000)Google Scholar
- 11.Ruhe, G.: Software Engineering Decision Support: Methodology and Applications. In: Tonfoni, Jain (eds.) Innovations in Decision Support Systems. International Series on Advanced Intelligence, vol. 3, pp. 143–174 (2003)Google Scholar
- 12.Ruhe, G.: Learning Software Organizations. In: Chang, S.K. (ed.) Handbook of Software Engineering and Knowledge Engineering, vol. 1, pp. 663–678. World Scientific Publishing, Singapore (2001)Google Scholar
- 13.Ruhe, G., Greer, D.: Quantitative Studies in Software Release Planning under Risk and Resource Constraints. In: Proceedings of the IEEE International Symposium on Empirical Software Engineering (ISESE 2003), pp. 262–271 (2003)Google Scholar
- 14.Ruhe, G., Ngo-The, A.: Hybrid Intelligence in Software Release Planning. Appears in: IJHS 1 (2004)Google Scholar
- 15.Saaty, T.L.: The Analytical Hierarchy Process. Wiley, New York (1980)Google Scholar
- 16.Standish Group Research: What are your requirements?, http://www.standishgroup.com/
- 17.Wang, Q., Lai, X.: Proc. Requirements Management for the Incremental Development Model. In: 2nd Asia-Pacific Conference on Quality Software, pp. 295–301 (2001)Google Scholar