An empirical investigation of software reliability indicators

Syed Mohamad, SM

An empirical investigation of software reliability indicators

Syed Mohamad, SM

Permalink

Publication Type:: Thesis
Issue Date:: 2012

Open Access

Copyright Clearance Process

Recently Added
In Progress
Open Access

This item is open access.

Adobe PDF

Download contents and abstractAdobe PDF (5.74 MB)

Adobe PDF

Download thesisAdobe PDF (123.39 MB)

View statistics

Full metadata record

Field	Value	Language
dc.contributor.author	Syed Mohamad, SM
dc.date.accessioned	2015-02-26T01:06:49Z
dc.date.available	2015-02-26T01:06:49Z
dc.date.issued	2012
dc.identifier.uri	http://hdl.handle.net/10453/33885
dc.description	University of Technology, Sydney. Faculty of Engineering and Information Technology.	en_US
dc.description.abstract	This thesis investigates how individuals and organisations, without technical skills, might determine the reliability of open source software given the increased use of such software. Software reliability is normally indicated by the growth and subsequent decline of defects in the software. A notable observation is that reliability growth models require a definitive stabilisation phase during which testing can reveal the growth and decline of defects as the indication of the increase in reliability of software. However, there is not necessarily a definitive stabilisation phase in the open source software development. More importantly, the presence or absence of the stabilisation phase is an attribute of a software development method and is not restricted to open source software. When software is developed without a definitive stabilisation phase, reliability growth models are not applicable because the conditions for their validity have not been achieved. Consequently, this thesis looks for alternative information based on tests to aid decision-making about software acquisition. Data was collected by conducting semi-structured interviews from 29 participants who were currently engaged in software development. The information of tests; coverage, sufficiency and rigours of tests concerns the testing that has been performed on the software product and gives expectations on how well the software product has been tested.	en_US
dc.format	Thesis (PhD)	en_US
dc.language.iso	en	en_US
dc.relation	https://opus.lib.uts.edu.au/bitstream/10453/33885/9/02Whole.pdf
dc.rights	au.edu.uts.lib/ppc
dc.rights	The author owns the copyright in this thesis including all reproduction and reuse rights for the work. The work may not be altered without the permission of the copyright owner. Attribution is essential when quoting or paraphrasing from this thesis.
dc.rights	info:eu-repo/semantics/openAccess
dc.rights	© 2012 Sharifah Mashita Syed Mohamad
dc.title	An empirical investigation of software reliability indicators	en_US
dc.type	Thesis
utslib.copyright.status	open_access

Abstract:

This thesis investigates how individuals and organisations, without technical skills, might determine the reliability of open source software given the increased use of such software. Software reliability is normally indicated by the growth and subsequent decline of defects in the software. A notable observation is that reliability growth models require a definitive stabilisation phase during which testing can reveal the growth and decline of defects as the indication of the increase in reliability of software. However, there is not necessarily a definitive stabilisation phase in the open source software development. More importantly, the presence or absence of the stabilisation phase is an attribute of a software development method and is not restricted to open source software. When software is developed without a definitive stabilisation phase, reliability growth models are not applicable because the conditions for their validity have not been achieved. Consequently, this thesis looks for alternative information based on tests to aid decision-making about software acquisition. Data was collected by conducting semi-structured interviews from 29 participants who were currently engaged in software development. The information of tests; coverage, sufficiency and rigours of tests concerns the testing that has been performed on the software product and gives expectations on how well the software product has been tested.

Please use this identifier to cite or link to this item:

http://hdl.handle.net/10453/33885