2016
DOI: 10.1007/s13198-016-0510-7
|View full text |Cite
|
Sign up to set email alerts
|

Optimal release and patching time of software with warranty

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
5
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
7
2

Relationship

0
9

Authors

Journals

citations
Cited by 26 publications
(6 citation statements)
references
References 18 publications
0
5
0
Order By: Relevance
“…The asset owner should try to minimise the resources spent dealing with patch testing and installation processes. For this purpose, an optimised patch release and installation strategies are required [ 60 , 61 , 62 , 63 ]. In these cost and risk models, operational downtime periods should be considered.…”
Section: Software Updates Managementmentioning
confidence: 99%
“…The asset owner should try to minimise the resources spent dealing with patch testing and installation processes. For this purpose, an optimised patch release and installation strategies are required [ 60 , 61 , 62 , 63 ]. In these cost and risk models, operational downtime periods should be considered.…”
Section: Software Updates Managementmentioning
confidence: 99%
“…To satisfy customers concern of reliable software, manufacturers may provide warranty on the embedded software. Within the warranty period, the manufacturer provides assurance to the customers that the software may work properly and if any defect is found, the manufacturer may either repair or replace the software without charging the customer (Kansal, Singh, Kumar, & Kapur, 2016;Singh, Kapur, Shrivastava, & Kumar, 2015).…”
Section: Warranty Claims Due To Software Failurementioning
confidence: 99%
“…Tickoo et al [34] have proposed a testing effort based cost model to determine the optimal release time and patch time of a software. Kansal et al [20] have proposed a generalized framework for finding the optimal release and patch time of a software under warranty. Anand et al [5] have also worked on modeling the software patch/update release and software upgrade release phenomena simultaneously.…”
Section: Introductionmentioning
confidence: 99%