2021
DOI: 10.1002/qre.2908
|View full text |Cite
|
Sign up to set email alerts
|

Change‐points‐based software scheduling

Abstract: Software reliability literature consists of various change‐point‐based software reliability growth models and related release time problems. The primary assumption of the existing models is the existence of change‐point before software release time only. This does not look practical as the testing team becomes more proficient in detecting the faults due to their continuous involvement in software development by the software release time. Hence the fault detection rate in the pre‐ and postrelease phase is not t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
6
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
1

Relationship

4
1

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 41 publications
0
6
0
Order By: Relevance
“…Choudhary et al 42 developed a change point based software cost model to obtain software release and patching time. Shrivastava and Kapur 3 developed a change point based framework to optimize release time and testing time of the software. Recently Chatterjee et al 43 developed a fuzzy based algorithm for prediction of fault in the early phase of software development.…”
Section: Literature Reviewmentioning
confidence: 99%
See 1 more Smart Citation
“…Choudhary et al 42 developed a change point based software cost model to obtain software release and patching time. Shrivastava and Kapur 3 developed a change point based framework to optimize release time and testing time of the software. Recently Chatterjee et al 43 developed a fuzzy based algorithm for prediction of fault in the early phase of software development.…”
Section: Literature Reviewmentioning
confidence: 99%
“…Another limitation of the existing work is the assumption of one of the following: Either the warranty period is fixed or release time is fixed. 3 In the first case, the optimal software release time is obtained under fixed warranty and in the latter case, optimal warranty time is determined under the assumption of know software release time. Due to the continuous increase in advanced software, firms have also changed their strategy to stop testing of the software after its release.…”
Section: Introductionmentioning
confidence: 99%
“…Various frameworks have been proposed that give reliability assessment of the safety-critical systems using Bayesian update methodology. 47 A modified NHPP model has also been proposed for OSS reliability modelling and analysis and based on this model and multi-attribute utility theory, optimal version updating for OSS has been examined resulting in a new decision model. 44,46 A framework to model the failure occurrence in OSS is developed to check the reliability growth.…”
Section: Literature Reviewmentioning
confidence: 99%
“…This demand has reduced the lifecycle of software; therefore, to be in the market, software firms have to work hard to meet the users’ expectation. To fulfil the need, firms are developing new software with advanced feature and releasing multiple version of the base version by adding functionalities into it (Kapur et al , 2010, Singh et al , 2015; Mishra et al , 2018; Shrivastava and Sachdeva, 2020; Saraf et al ., 2021; Shrivastava and Kapur, 2021). Keeping the base of software same and enhancing the features over regular intervals of time is beneficial for information technology (IT) industry as it avoids the delay in release of product and makes its market life grow long.…”
Section: Literature Reviewmentioning
confidence: 99%
“…Pachauri et al (2019) proposed a framework for developing multi-release of software by incorporating imperfect debugging in fault detection and the correction process and computed the optimal release time using multi-attribute utility theory. Shrivastava et al (2020) and Shrivastava and Kapur (2021) developed a change point-based software cost model to optimize release and testing stop time.…”
Section: Literature Reviewmentioning
confidence: 99%