Joint Release and Testing Stop Time Policy with Testing-Effort and Change Point

Kapur, P. K.; Panwar, Saurabh; Singh, Ompal; Kumar, Vivek

doi:10.1007/978-981-13-5796-1_12

Cited by 10 publications

(4 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(i) Testing Cost: This cost refers to per unit testing cost and is associated with the tester's activities such as such as test planning, test case generation, test execution, and analysis of testing results. In software engineering literature, testing cost has been established as a linear function of testing time (Kapur et al, 2019). Therefore, its functional form is given as: 1 ()…”

Section: Proposed Cost Modelmentioning

confidence: 99%

“…In MAUT, utility functions are used to depict goal of each factor. In literature, two functional forms of utility function are commonly used: linear and exponential type (Kapur et al, 2019). The general form of linear function is () u x l mx  and of exponential is ( ) .…”

Section: Evaluate Saufmentioning

confidence: 99%

“…According to the traditional approach, the testing stop time and software release time should coincide, i.e., company should stop the testing process as soon as it delivers the product to its customers (Okumoto and Goel, 1980;Yamada and Osaki, 1987;Dalal and Mallows, 1988;McDaid and Wilson, 2001;Kapur et al, 2014Kapur et al, , 2015. However, according to some researchers, the software engineers should adopt the policy of releasing the software early and continue the testing process even after the software release to attain the desired reliability aspiration level (Arora et al, 2006;Jiang et al, 2012;Majumdar et al, 2017;Kapur et al, 2019). The benefit of releasing software early is that the competitors will be unable to exploit the market.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Determining Software Time-to-Market and Testing Stop Time when Release Time is a Change-Point

Singh¹,

Panwar²,

Kapur³

2020

Int J Math, Eng, Manag Sci

Self Cite

View full text Add to dashboard Cite

In software engineering literature, numerous software reliability growth models have been designed to evaluate and predict the reliability of the software products and to measure the optimal time-to-market of the software systems. Most existing studies on software release time assessment assumes that when software is released, its testing process is terminated. In practice, however, the testing team releases the software product first and continues the testing process for an added period in the operational phase. Therefore, in this study, a coherent reliability growth model is developed to predict the expected reliability of the software product. The debugging process is considered imperfect as new faults can be introduced into the software during each fault removal. The proposed model assumes that the fault observation rate of the testing team modifies after the software release. The release time of the software is therefore regarded as the change-point. It has been established that the veracity of the performance of the growth models escalates by incorporating the change-point theory. A unified approach is utilized to model the debugging process wherein both testers and users simultaneously identify the faults in the post-release testing phase. A joint optimization problem is formulated based on the two decision criteria: cost and reliability. In order to assimilate the manager’s preferences over these two criteria, a multi-criteria decision-making technique known as multi-attribute utility theory is employed. A numerical illustration is further presented by using actual data sets from the software project to determine the optimal software time-to-market and testing termination time.

show abstract

Section: Proposed Cost Modelmentioning

confidence: 99%

Section: Evaluate Saufmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Determining Software Time-to-Market and Testing Stop Time when Release Time is a Change-Point

Singh¹,

Panwar²,

Kapur³

2020

Int J Math, Eng, Manag Sci

Self Cite

View full text Add to dashboard Cite

show abstract

“…Consequently, the software managers are in the opinion of testing the software even after its release. Therefore, companies execute a policy of releasing the software early for commercial use to have a competitive edge and continue the testing process in the field environment to improve the overall reliability of the system (Kapur et al, 2019b). In the past, some studies have been carried out in this area considering software time to market and testing termination time as two different time points (Arora et al, 2006;Jiang et al, 2012, Kapur et al, 2019aSingh et al, 2020;Kumar et al, 2021).…”

mentioning

confidence: 99%

Software reliability prediction and release time management with coverage

Panwar

Kumar

Kapur

et al. 2021

IJQRM

Self Cite

View full text Add to dashboard Cite

PurposeSoftware 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.Design/methodology/approachThe 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.FindingsThe 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.Originality/valueThis study is the first attempt to assimilate testing coverage phenomenon in joint optimization of software time to market and testing duration.

show abstract

Vulnerability Discovery Analysis in Software Reliability and Related Optimization Problems

Kapur

Panwar

2023

Springer Handbook of Engineering Statistics

View full text Add to dashboard Cite

Joint Release and Testing Stop Time Policy with Testing-Effort and Change Point

Cited by 10 publications

References 34 publications

Determining Software Time-to-Market and Testing Stop Time when Release Time is a Change-Point

Determining Software Time-to-Market and Testing Stop Time when Release Time is a Change-Point

Software reliability prediction and release time management with coverage

Vulnerability Discovery Analysis in Software Reliability and Related Optimization Problems

Contact Info

Product

Resources

About