Software release planning: an evolutionary and iterative approach

@article{Greer2004SoftwareRP,
  title={Software release planning: an evolutionary and iterative approach},
  author={Des Greer and G{\"u}nther Ruhe},
  journal={Inf. Softw. Technol.},
  year={2004},
  volume={46},
  pages={243-253}
}
  • D. Greer, G. Ruhe
  • Published 15 March 2004
  • Computer Science
  • Inf. Softw. Technol.

Figures and Tables from this paper

Chapter VII Requirements Prioritisation for Incremental and Iterative Development

The problems associated with requirements prioritisation for an incremental and iterative software process are described. Existing approaches to prioritisation are then reviewed, including the

Optimized Resource Allocation for Software Release Planning

TLDR
A two-phased optimization approach that combines the strength of two existing solution methods to provide release plan solutions that achieve a better overall business value by better allocation of resources.

Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

TLDR
This research generates a problem and submit it so that the VDA and SBSE methods try to resolve it, and compares the results obtained through VDA with those of the Search-Based Software Engineering.

Exact Analysis for Next Release Problem

  • Lingbo Li
  • Business
    2016 IEEE 24th International Requirements Engineering Conference (RE)
  • 2016
TLDR
This proposed research aims to provide a decision support framework for analysing uncertainty in requirements selection and optimisation, and introduces a simulation optimisation technique to model requirements uncertainty in requirement optimisation.

What is important when deciding to include a software requirement in a project or release?

  • C. WohlinA. Aurum
  • Computer Science
    2005 International Symposium on Empirical Software Engineering, 2005.
  • 2005
TLDR
An empirical study of the decision criteria focuses on how different perspectives have different influence on the decision-making process and concludes that business-oriented and management-oriented criteria are more important than technical concerns related to software architecture, impact analysis, dependency between requirements and software evolution.

Quantitative studies in software release planning under risk and resource constraints

  • G. RuheD. Greer
  • Computer Science
    2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings.
  • 2003
TLDR
A method called EVOLVE+, based on a genetic algorithm and aimed at the evolutionary planning of incremental software development, which is initially evaluated using a sample project and involves an investigation of the tradeoff relationship between risk and the overall benefit.

Multiobjective Software Release Planning with Dependent Requirements and Undefined Number of Releases

TLDR
The strategy regards on the stakeholders’ satisfaction, business value and risk management, as well as provides ways for handling requirements interdependencies and the feasibility of the proposed approach is shown.

An Adjustable Process of Requirements Prioritizing for Release Plan

TLDR
An adjustable priority process based on a priority model to select a method and aspects for the suitable priority for product and organization and enhances the completeness of a release plan by a definition of static and dynamic dependency types between requirements.

An integrated approach for requirement selection and scheduling in software release planning

TLDR
This paper introduces two integer linear programming models that integrate time scheduling into software release planning and presents a more detailed analysis of requirement dependencies, which indicate that requirement dependency can significantly influence the requirement selection and the corresponding project plan.

EVOLVING PRIORITIZATION FOR SOFTWARE PRODUCT MANAGEMENT

The quality of a product is commonly defined by its ability to satisfy stakeholder needs and expectations. Therefore, it is important to find, select, and plan the content of a software product to
...

References

SHOWING 1-10 OF 33 REFERENCES

An evaluation of methods for prioritizing software requirements

Effecting and measuring risk reduction in software development

This paper describes an application of SERUM (Software Engineering Risk: Understanding and Management), a risk management methodology, to the definition and prioritisation of changes in a network

Challenges in Requirements Engineering

This paper presents a exposition of requirements engineering concepts and challenges, targeted on the research division of a large software company. It is argued that doing requirements is a

Software requirements prioritizing

  • Joachim Karlsson
  • Computer Science
    Proceedings of the Second International Conference on Requirements Engineering
  • 1996
TLDR
The results from the case study indicate that the pairwise comparison technique is an efficient informative and accurate means for finding the candidate requirements importance, and is recommended for software requirements prioritizing.

Requirements management for the incremental development model

  • Qing WangXufang Lai
  • Computer Science
    Proceedings Second Asia-Pacific Conference on Quality Software
  • 2001
TLDR
The paper discusses the method of requirements management for the incremental development model, the goal of the management, the structure of data collection, and the metrics of the capability measurement.

Extreme Programming Explained

Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new

Challenges in requirements engineering

  • J. Bubenko
  • Business, Computer Science
    Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)
  • 1995
We discuss a number of essential problems of software requirements engineering, related to management, organisations, users, stakeholders, methodology, tools, and education. Most of the problems seem

Experimenting with Genetic Algorithms to Devise Optimal Integration Test Orders

TLDR
An improved strategy to devise optimal integration test orders in object-oriented systems in the presence of dependency cycles based on the combined use of inter-class coupling measurement and genetic algorithms is presented.

Principles of software engineering management

  • T. Gilb
  • Engineering, Computer Science
  • 1988

Proceedings of the third international conference on Genetic algorithms

TLDR
The range of scheduling mechanisms presented herein allows this type of exibility during code generation and their use on critical portions of code could create enhanced run-time performance for a wide variety of code.