Software Release Planning

Goel proposed generalization of the Goel–Okumoto (G–O) software reliability growth model (SRGM), in
order to model the failure intensity function, i.e. the rate of occurrence of failures (ROCOF) that initially
increases and then decreases (I/D), which occurs in many projects due to the learning phenomenon of the
testing team and a few other causes. The ROCOF of the generalized non-homogenous poisson process
(NHPP) model can be expressed in the same mathematical form as that of a two-parameterWeibull function.
However, this SRGM is susceptible to wide fluctuations in time between failures and sometimes it seems
unable to recognize the I/Dpattern ofROCOFpresent in the datasets and hence does not adequately describe
such data. The authors therefore propose a shifted Weibull function ROCOF instead for the generalized
NHPP model. This modification to the Goel-generalized NHPP model results in an SRGM that seems to
perform better consistently, as confirmed by the goodness of fit statistic and predictive validity metrics,
when applied to failure datasets of 11 software projects with widely varying characteristics. A case study
on software release time determination using the proposed SRGM is also given.

Abstract: Software reliability modeling is challenging since no single Software
Reliability Growth Model (SRGM) is considered suitable in all situations owing to poor
goodness of fit, lack of predictive validity of the models and their sensitivity to
fluctuations in the number of failures in the data sets. In this paper, we propose a Non-
Homogenous Poisson Process Model whose failure intensity function has the same
Mathematical form as that of the probability density function (pdf) of a generalized
exponential distribution. The performance of the proposed model was verified and also
compared with six chosen SRGMs using failure data from 18 software systems and the
model is found to be adequate in terms of goodness

Testability is an important software quality factor
that is ineffective if it is not available at an early stage in the development life-cycle. It becomes more essential in the case of object oriented design. Flexibility is an important key factor to testability analysis and me
asurement for delivering high class testable and
maintainable software. Flexibility is a criterion o
f crucial significance to software developers, designers
and the quality controllers. It constantly guides a
nd supports to avoid wastage of resources as well as
enable the designers for continuous improvement in
the development process. Flexibility is concerned with
building high quality and reliable software within
the constraints of cost and time. It greatly influences
cost, quality and reliability at software evolution
process. Despite the fact flexibility is vital and
highly significant aspect for software development process
es, it is poorly managed. This paper focuses the need
and importance of flexibility early at design phase
. A model has been proposed for flexibility measurement
of object oriented design by establishing multiple
linear regression. Finally the proposed model has been
validated using experimental tryout.

"Context: Strategic release planning (sometimes referred to as road-mapping) is an important phase of the
requirements engineering process performed at product level. It is concerned with selection and assignment
of requirements in sequences of releases such that important technical and resource constraints are
fulfilled.
Objectives: In this study we investigate which strategic release planning models have been proposed,
their degree of empirical validation, their factors for requirements selection, and whether they are
intended for a bespoke or market-driven requirements engineering context.
Methods: In this systematic review a number of article sources are used, including Compendex, Inspec,
IEEE Xplore, ACM Digital Library, and Springer Link. Studies are selected after reading titles and abstracts
to decide whether the articles are peer reviewed, and relevant to the subject.
Results: Twenty four strategic release planning models are found and mapped in relation to each other,
and a taxonomy of requirements selection factors is constructed.
Conclusions: We conclude that many models are related to each other and use similar techniques to
address the release planning problem. We also conclude that several requirement selection factors are
covered in the different models, but that many methods fail to address factors such as stakeholder value
or internal value. Moreover, we conclude that there is a need for further empirical validation of the models
in full scale industry trials."

Strategic release planning (road-mapping) is an important phase of requirements engineering process performed at product level. It is concerned with selection and assignment of requirements in sequences of releases such that important technical and resource constraints are fulfilled. It is always considered difficult to form a strategic release plan due to varying constraints and uncertainties. In this regard, different strategic release planning models have been presented in academia and different methods are being used in Industry. In this thesis, strategic release planning models presented in academia and some methods of strategic release planning being used in Industry are identified. The contributions of these models are also provided in the thesis. A systematic review has been performed to know strategic release planning models in academia. The aim of systematic review is to present fair evaluation of research concerning strategic release planning models. Through systematic re...

Strategic release planning (road-mapping) is an important phase of requirements engineering process performed at product level. It is concerned with selection and assignment of requirements in sequences of releases such that important technical and resource constraints are fulfilled. It is always considered difficult to form a strategic release plan due to varying constraints and uncertainties. In this regard, different strategic release planning models have been presented in academia and different methods are being used in Industry. In this thesis, strategic release planning models presented in academia and some methods of strategic release planning being used in Industry are identified. The contributions of these models are also provided in the thesis. A systematic review has been performed to know strategic release planning models in academia. The aim of systematic review is to present fair evaluation of research concerning strategic release planning models. Through systematic review, requirements selection factors considered by a model, validation details of model and a model‟s usefulness for bespoke and market-driven development are summarized. Moreover two organizations have been interviewed to know strategic release planning models being used in Industry in addition to the ones presented in academia. Similarly contribution of models being used in Industry is provided by logging details of requirements selection factors, validation details and usefulness for bespoke and market-driven software development of each model / process of Industry. Based on systematic review and industrial interviews‟ results, a list of common requirements selection factors (considered by models of academia and Industry) is provided. Some general recommendations have been given for research in academia on strategic release planning models after analysis of systematic review and industrial interviews‟ results.

Reliability is one of the most relevant software quality attributes. The literature offers a variety of mathematical models - namely, software reliability growth models (SRGMs) - to estimate the reliability of a software product at a given time, as well as to predict the reliability that will be achieved as testing activities progress. One of the typical assumptions of SRGMs is the immediate debugging of detected faults. In reality, the impact of the debugging process cannot be neglected at all. This paper reports the results of a real-world case-study in which we analyze the debugging process of a Customer Relationship Management (CRM) system, and study its impact on SRGM-based reliability estimation and prediction.