Search results

In this paper, the authors propose two construction methods to estimate confidence intervals of the time-based optimal software rejuvenation policy and its associated maximum system availability via a parametric bootstrap method. Through simulation experiments the authors investigate their asymptotic behaviors and statistical properties.

The present paper is the first challenge to derive the confidence intervals of the optimal software rejuvenation schedule, which maximizes the system availability in the sense of long run. In other words, the authors concern the statistical software fault management by employing an idea of process control in quality engineering and a parametric bootstrap.

As a remarkably different point from the existing work, the authors carefully take account of a special case where the two-sided confidence interval of the optimal software rejuvenation time does not exist due to that fact that the estimator distribution of the optimal software rejuvenation time is defective. Here the authors propose two useful construction methods of the two-sided confidence interval: conditional confidence interval and heuristic confidence interval.

Although the authors applied a simulation-based bootstrap confidence method in this paper, another re-sampling-based approach can be also applied to the same problem. In addition, the authors just focused on a parametric bootstrap, but a non-parametric bootstrap method can be also applied to the confidence interval estimation of the optimal software rejuvenation time interval, when the complete knowledge on the distribution form is not available.

The statistical software fault management techniques proposed in this paper are useful to control the system availability of operational software systems, by means of the control chart.

Through the online monitoring in operational software systems, it would be possible to estimate the optimal software rejuvenation time and its associated system availability, without applying any approximation. By implementing this function on application programming interface (API), it is possible to realize the low-cost fault-tolerance for software systems with aging.

In the past literature, almost all authors employed parametric and non-parametric inference techniques to estimate the optimal software rejuvenation time but just focused on the point estimation. This may often lead to the miss-judgment based on over-estimation or under-estimation under uncertainty. The authors overcome the problem by introducing the two-sided confidence interval approach.

The software development team reviews the testing phase to assess if the reliability growth of software is as per plan and requirement and gives suggestions for improvement. The objective of this study is to determine the optimal review time such that there is enough time to make judgments about changes required before the scheduled release.

Testing utilizes majority of time and resources, assures reliability and plays a critical role in release and warranty decision-making reviews necessary. A very early review during testing may not give useful information for analyzing or improving project performance, and a very late review may delay product delivery and lead to opportunity loss for developers. Therefore, it is assumed that the optimal time for review is in the later stage of testing when the fault removal rate starts to decline. The expression for this time point is determined using the S-curve 2-D software reliability growth model (SRGM).

The methodology has been illustrated using the real-life fault datasets of Tandem computers and radar systems resulting in optimal review time of 14 weeks and 26 months, respectively, which is neither very early in testing nor very near to the scheduled release. The developer can make changes (more resources or postpone release) to expedite the process.

Most of the literature studies focus on determination of optimal testing or release time to achieve considerable reliability within the budget, but in this study, the authors determine the optimal review time during testing using SRGM to ensure the considerable reliability at release.

The purpose of this paper is to identify and quantify the key components of the overall cost of software development when warranty coverage is given by a developer. Also, the authors have studied the impact of imperfect debugging on the optimal release time, warranty policy and development cost which signifies that it is important for the developers to control the parameters that cause a sharp increase in cost.

An optimization problem is formulated to minimize software development cost by considering imperfect fault removal process, faults generation at a constant rate and an environmental factor to differentiate the operational phase from the testing phase. Another optimization problem under perfect debugging conditions, i.e. without error generation is constructed for comparison. These optimization models are solved in MATLAB, and their solutions provide insights to the degree of impact of imperfect debugging on the optimal policies with respect to software release time and warranty time.

A real-life fault data set of Radar System is used to study the impact of various cost factors via sensitivity analysis on release and warranty policy. If firms tend to provide warranty for a longer period of time, then they may have to bear losses due to increased debugging cost with more number of failures occurring during the warrantied time but if the warranty is not provided for sufficient time it may not act as sufficient hedge during field failures.

Every firm is fighting to remain in the competition and expand market share by offering the latest technology-based products, using innovative marketing strategies. Warranty is one such strategic tool to promote the product among masses and develop a sense of quality in the user’s mind. In this paper, the failures encountered during development and after software release are considered to model the failure process.

Software testing is needed to produce extremely reliable software products. A crucial decision problem that the software developer encounters is to ascertain when to terminate the testing process and when to release the software system in the market. With the growing need to deliver quality software, the critical assessment of reliability, cost of testing and release time strategy is requisite for project managers. This study seeks to examine the reliability of the software system by proposing a generalized testing coverage-based software reliability growth model (SRGM) that incorporates the effect of testing efforts and change point. Moreover, the strategic software time-to-market policy based on costreliability criteria is suggested.

The fault detection process is modeled as a composite function of testing coverage, testing efforts and the continuation time of the testing process. Also, to assimilate factual scenarios, the current research exhibits the influence of software users refer as reporters in the fault detection process. Thus, this study models the reliability growth phenomenon by integrating the number of reporters and the number of instructions executed in the field environment. Besides, it is presumed that the managers release the software early to capture maximum market share and continue the testing process for an added period in the user environment. The multiattribute utility theory (MAUT) is applied to solve the optimization model with release time and testing termination time as two decision variables.

The practical applicability and performance of the proposed methodology are demonstrated through real-life software failure data. The findings of the empirical analysis have shown the superiority of the present study as compared to conventional approaches.

This study is the first attempt to assimilate testing coverage phenomenon in joint optimization of software time to market and testing duration.

The purpose of this paper is to develop a new software reliability growth model considering different fault distribution function before and after the change point.

In this paper, the authors have developed a framework to incorporate change-point in developing a hybrid software reliability growth model by considering different distribution functions before and after the change point.

Numerical illustration suggests that the proposed model gives better results in comparison to the existing models.

The existing literature on change point-based software reliability growth model assumes that the fault correction trend before and after the change is governed by the same distribution. This seems impractical as after the change in the testing environment, the trend of fault detection or correction may not follow the same trend; hence, the assumption of same distribution function may fail to predict the potential number of faults. The modelling framework assumes different distributions before and after change point in developing a software reliability growth model.

The use of “fault‐counting” models with “discrete” data in the case of commercial software has considerable advantages for the vendor. The adapted Littlewood Stochastic Reliability Growth model has the advantage of allowing a variety of fault manifestation rates. The process of inferring the parameters of this model is presented graphically in a way intended to clarify untuitively some of the problems commonly experienced with estimation, particularly where long‐term predictions are required. Based on this, alternative objective functions are suggested for fitting the model to failure data.

Almost everything around us is the output of software-driven machines or working with software. Software firms are working hard to meet the user’s requirements. But developing a fault-free software is not possible. Also due to market competition, firms do not want to delay their software release. But early release software comes with the problem of user reporting more failures during operations due to more number of faults lying in it. To overcome the above situation, software firms these days are releasing software with an adequate amount of testing instead of delaying the release to develop reliable software and releasing software patches post release to make the software more reliable. The paper aims to discuss these issues.

The authors have developed a generalized framework by assuming that testing continues beyond software release to determine the time to release and stop testing of software. As the testing team is always not skilled, hence, the rate of detection correction of faults during testing may change over time. Also, they may commit an error during software development, hence increasing the number of faults. Therefore, the authors have to consider these two factors as well in our proposed model. Further, the authors have done sensitivity analysis based on the cost-modeling parameters to check and analyze their impact on the software testing and release policy.

From the proposed model, the authors found that it is better to release early and continue testing in the post-release phase. By using this model, firms can get the benefits of early release, and at the same time, users get the benefit of post-release software reliability assurance.

The authors are proposing a generalized model for software scheduling.

In the current market scenario, software upgrades and updates have proved to be very handy in improving the reliability of the software in its operational phase. Software upgrades help in reinventing working software through major changes, like functionality addition, feature enhancement, structural changes, etc. In software updates, minor changes are undertaken which help in improving software performance by fixing bugs and security issues in the current version of the software. Through the current proposal, the authors wish to highlight the economic benefits of the combined use of upgrade and update service. A cost analysis model has been proposed for the same.

The article discusses a cost analysis model highlighting the distinction between launch time and time to end the testing process. The number of bugs which have to be catered in each release has been determined which also consists of the count of latent bugs of previous version. Convolution theory has been utilized to incorporate the joint role of tester and user in bug detection into the model. The cost incurred in debugging process was determined. An optimization model was designed which considers the reliability and budget constraints while minimizing the total debugging cost. This optimization was used to determine the release time and testing stop time.

The proposal is backed by real-life software bug dataset consisting of four releases. The model was able to successfully determine the ideal software release time and the testing stop time. An increased profit is generated by releasing the software earlier and continues testing long after its release.

The work contributes positively to the field by providing an effective optimization model, which was able to determine the economic benefit of the combined use of upgrade and update service. The model can be used by management to determine their timelines and cost that will be incurred depending on their product and available resources.

This paper is focused at studying the current state of research involving the four dimensions of defect management strategy, i.e. software defect analysis, software quality, software reliability and software development cost/effort.

The methodology developed by Kitchenham (2007) is followed in planning, conducting and reporting of the systematic review. Out of 625 research papers, nearly 100 primary studies related to our research domain are considered. The study attempted to find the various techniques, metrics, data sets and performance validation measures used by researchers.

The study revealed the need for integrating the four dimensions of defect management and studying its effect on software performance. This integrated approach can lead to optimal use of resources in software development process.

There are many dimensions in defect management studies. The authors have considered only vital few based on the practical experiences of software engineers. Most of the research work cited in this review used public data repositories to validate their methodology and there is a need to apply these research methods on real datasets from industry to realize the actual potential of these techniques.

The authors believe that this paper provides a comprehensive insight into the various aspects of state-of-the-art research in software defect management. The authors feel that this is the only research article that delves into the four facets namely software defect analysis, software quality, software reliability and software development cost/effort.

The determination of the release schedule for a new software product is the most important issue for designing and controlling a software development process. In fact, the optimal software release problem based on some software reliability growth models has been studied by many authors. In this paper, we propose a new method to estimate the optimal software release time under an alternative cost criterion. More precisely, two kinds of artificial neural networks are used to estimate the fault‐detection time observed in both testing and operation phases. As a cost criterion, we adopt the expected cost rate (the expected total software cost per unit testing time). Then, it is shown that the optimization problem to obtain the optimal release time can be reduced to a graphical one to minimize the tangent slope from a point to an (estimated) empirical curve in two‐dimensional space. Through numerical examples using actual fault‐detection time data, it is illustrated that the method proposed is a very useful device to estimate the optimal software release time precisely.