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
Multi up-gradation software reliability growth model with imperfect debugging.
2010 (English)In: International Journal of Systems Assurance Engineering and Management, ISSN 0975-6809, E-ISSN 0976-4348, Vol. 1, no 4, p. 299-306Article in journal (Refereed) Published
Abstract [en]

Due to demand of new features and highly reliable software system, the software industries are speeding their up-gradations/add-ons in the software. The life of software is very short in the environment of perfect competition. Therefore the software developers have to come up with successive up gradations to survive. The reported bugs from the existing software and Features added to the software at frequent time intervals lead to complexity in the software system and add to the number of faults in the software. The developer of the software can lose on market share if it neglects the reported bugs and up gradation in the software and on the other hand a software company can lose its name and goodwill in the market if the reported bugs and functionalities added to the software lead to an increase in the number of faults in the software. To capture the effect of faults due to existing software and generated in the software due to add-ons at various points in time, we develop a multi up-gradation, multi release software reliability model. This model uniquely identifies the faults left in the software when it is in operational phase during the testing of the new code i.e. developed while adding new features to the existing software. Due to complexity and incomplete understanding of the software, the testing team may not be able to remove/correct the fault perfectly on observation/detection of a failure and the original fault may remain resulting in the phenomenon known as imperfect debugging, or get replaced by another fault causing error generation The model developed is validated on real data sets with software which has been released in the market with new features four times.

Place, publisher, year, edition, pages
2010. Vol. 1, no 4, p. 299-306
Identifiers
URN: urn:nbn:se:ltu:diva-11244DOI: 10.1007/s13198-011-0031-3Local ID: a2af0250-e758-4555-aa0d-c484c688a7d7OAI: oai:DiVA.org:ltu-11244DiVA, id: diva2:984193
Note
Upprättat; 2010; 20131105 (amigar)Available from: 2016-09-29 Created: 2016-09-29 Last updated: 2018-05-07Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full text

Authority records BETA

Garmabaki, Amir Soleimani

Search in DiVA

By author/editor
Garmabaki, Amir Soleimani
In the same journal
International Journal of Systems Assurance Engineering and Management

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 79 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