This paper investigates two integer linear programming models that integrate requirement scheduling into software release planning. The first model can schedule the development of the requirements for the new release exactly in time so that the project span is minimized and the resource and precedence constraints are satisfied. The second model is for combined requirement selection and scheduling, which can not only maximize revenues but also calculates an on-time-delivery project schedule simultaneously. Two simulations are presented to examine the influence of precedence constraints and compare the differences of the traditional prioritization models and the two new ones. The simulation results suggest that requirement dependency can sign...
This chapter provides an overview of techniques for prioritization of requirements for software prod...
In software development, release planning is performed in order to select important features and re...
[Context and motivation] Requirements catalogues for software release planning are often not compl...
Abstract. This paper integrates requirement scheduling issues into software release planning. Two in...
It is essential for product software companies to decide which requirements should be included in th...
Abstract. Selection of the requirements for the next release of a software product is a inherently c...
For software vendors, the process to determine the requirements for the next release of a software p...
Incremental software development replaces monolithic-type development by offering a series of releas...
This paper examines a recurrent software development project in which scheduling had become a critic...
Requirement selection is an essential component of software release planning, which finds, for a giv...
Requirement selection is an essential component of software release planning, which finds, for a giv...
Software maintenance is generally recognized to consume majority of resources in many organizations....
The quality of a product is commonly defined by its ability to satisfy stakeholder needs and expecta...
Decision-making is central to Software Product Management (SPM) and includes deciding on requirement...
Includes bibliographical references (pages 87-90)This study investigates the applicability of intege...
This chapter provides an overview of techniques for prioritization of requirements for software prod...
In software development, release planning is performed in order to select important features and re...
[Context and motivation] Requirements catalogues for software release planning are often not compl...
Abstract. This paper integrates requirement scheduling issues into software release planning. Two in...
It is essential for product software companies to decide which requirements should be included in th...
Abstract. Selection of the requirements for the next release of a software product is a inherently c...
For software vendors, the process to determine the requirements for the next release of a software p...
Incremental software development replaces monolithic-type development by offering a series of releas...
This paper examines a recurrent software development project in which scheduling had become a critic...
Requirement selection is an essential component of software release planning, which finds, for a giv...
Requirement selection is an essential component of software release planning, which finds, for a giv...
Software maintenance is generally recognized to consume majority of resources in many organizations....
The quality of a product is commonly defined by its ability to satisfy stakeholder needs and expecta...
Decision-making is central to Software Product Management (SPM) and includes deciding on requirement...
Includes bibliographical references (pages 87-90)This study investigates the applicability of intege...
This chapter provides an overview of techniques for prioritization of requirements for software prod...
In software development, release planning is performed in order to select important features and re...
[Context and motivation] Requirements catalogues for software release planning are often not compl...