Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Optimal release and patching time of software with warranty
Amity Institute of Information Technology, Amity University.
Amity International Business School, Amity University.
Luleå University of Technology, Department of Civil, Environmental and Natural Resources Engineering, Operation, Maintenance and Acoustics.
Amity Center for Interdisciplinary Research, Amity University, .
Number of Authors: 4
2016 (English)In: International Journal of Systems Assurance Engineering and Management, ISSN 0975-6809, E-ISSN 0976-4348, Vol. 7, no 4, 462-468 p.Article in journal (Refereed) Published
Abstract [en]

As we know in a competitive market, software firms are looking to sell their products at the earliest for maximum gains. Early delivery of a product is beneficial in terms of gaining market potential but may include some defects in it. On the other hand late delivery of a product ensures reliability but may results into disinterest of the customers. Thus, a vendor must focus on the best time for releasing the software. In recent times, early software release and updating it by providing patches in the operational phase is in trend. Also to satisfy customer’s primary concern of reliable software, firms are providing warranty on their products. Warranty period is the time in which firm provide assurance to the customers that under this period product will work properly and if any defect is found, firm will either repair or replace the software without charging the customer. But servicing during warranty period by updating with patches is also not economical from firm’s point of view. Hence it is important to find the optimal patch release time. In this paper we have proposed a generalized framework to find out the optimal release and patching time of software under warranty so that the total cost is minimized. Numerical example is given at the end to validate the proposed cost model.

Place, publisher, year, edition, pages
2016. Vol. 7, no 4, 462-468 p.
National Category
Other Civil Engineering
Research subject
Operation and Maintenance
Identifiers
URN: urn:nbn:se:ltu:diva-60747DOI: 10.1007/s13198-016-0510-7Scopus ID: 2-s2.0-85014032650OAI: oai:DiVA.org:ltu-60747DiVA: diva2:1050313
Note

Validerad; 2016; Nivå 2; 2016-11-28 (andbra)

Available from: 2016-11-28 Created: 2016-11-28 Last updated: 2017-03-10Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Search in DiVA

By author/editor
Kumar, Uday
By organisation
Operation, Maintenance and Acoustics
In the same journal
International Journal of Systems Assurance Engineering and Management
Other Civil Engineering

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

Total: 12 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf