Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Software reliability testing”

Testing for software reliability

Jonathan R. Brown, M. Lipow · 1975

This paper presents a formulation of a novel methodology for evaluation of testing in support of operational reliability assessment and prediction. The methodology features an incremental evaluation of the representativeness of a set of development and validation test cases together with definition of additional test cases to enhance those qualities.

Cited by 59Open access

Software Testing and Reliability

Andrew D. McGettrick · Encyclopedia of Quantitative Risk Analysis and Assessment · 2008

Abstract Software, increasingly, forms an important part of many systems—engineering, medical, administrative, educational, finance, and so on. Achieving high level of reliability of the software is a prerequisite for that system being successful. This article addresses the problem of testing of software and relates it to issues about reliability.

Cited by 1

Study on Software Reliability and Reliability Testing

G Chandrika, A Avizienis, L Chen et al. · Asia-pacific Journal of Convergent Research Interchange · 2015

Software business is on rise today and it has become the half and parcel within the lives of kith and kin. Such software once used as associate application ought to provide the client a feeling of trait that is nothing however technically termed as dependableness. The system should be ready to perform the desired functions in line with the expressed conditions for a selected amount of your time. It is important to take care of the reliability of the software system to stay track on the important data which incorporates resources, capital, details of employees, etc. Software plays associate equal role on with hardware and thus the analysis and measuring area unit done equally. The most challenging task for the business is to develop a reliable software system that consumes a lot of quantity of your time and dear too. The software dependableness will be measured the approaches specifically unit of time between failure and unit of time to failure. In this case we adopt a testing referred to as as dependableness testing whose purpose is to find the potential issues within the phases of development like style as shortly as doable and ultimately give the idea that the system meets its dependableness necessities.

Cited by 8Open access

Software Testing and Reliability Strategies

Norman F. Schneidewind · Journal of Aerospace Computing Information and Communication · 2010

Software testing strategies are developed based on fault removal—deterministic and random. Based on literature search, it is appears that this is the first research that has evaluated these strategies. Deterministic fault removal is determined by the ranking of deviations of the time of fault occurrence from statistical control chart upper limit. Random removal of faults is selected by random number generation. Counterintuitively, random fault removal proved to be the better strategy based on improvement in reliability metrics across a series of tests. Contrariwise, deterministic fault removal was better when the cost effectiveness of fault removal was considered. Fault and failure data from three diverse projects were used to make the strategy assessment: NASA Space Shuttle flight software, Japanese University application, and a database application.

Cited by 0

Software Reliability, Measurement, and Testing Software Reliability and Test Integration

James A. McCall, William Randell, Janet R. Dunham et al. · 1992

Abstract : This effort integrated software reliability, measurement, and test techniques in terms of prediction, estimation, and assessment. Experiments were conducted to compare six testing techniques and to measure the effect of software product and process variables on software reliability. A guidebook was produced to help program managers control and manage software reliability and testing. Error/anomaly and code reviews were the test techniques found to be the most effective at the unit level; branch testing and code reviews were the most effective at the CSC level. Software Reliability, Software Measurement, Software Testing.

Cited by 8

Software Testing, Verification And Reliability

Softw Test Verif, Phong Tran, Jeffrey Gosper et al. · 2007

this paper was originally presented at the First International Workshop on Verification and Validation of Enterprise Information Systems, held in Angers, France on 22 April 2003. It is reproduced here in modified form with the permission of the Workshop organizers and the publishers of the Proceedings, ICEIS

Cited by 0

Software Reliability, Measurement, and Testing. Volume 2. Guidebook for Software Reliability Measurement and Testing

James A. McCall, William Randell, Janet R. Dunham et al. · 1992

Abstract : This effort integrated software reliability, measurement, and test techniques in terms of prediction, estimation, and assessment. Experiments were conducted to compare six testing techniques and to measure the effect of software product and process variables on software reliability. A guidebook was produced to help program managers control and manage software reliability and testing. Error/anomaly and code reviews were the test techniques found to be the most effective at the unit level; branch testing and code reviews were the most effective at the CSC level. Software Reliability, Software Measurement, Software Testing.

Cited by 2

Risk-Driven Software Reliability and Testing

N. Schneidewind, Mike Hinchey · 2008

Classical methods of accepting or rejecting products, which are not generally known by the software reliability community, are used as a baseline for developing test criteria. Testing criteria are designed to estimate the number of tests, and associated fault removal, that would result in reduced risk and increased reliability to the point where the software can be deployed. For the purpose of experimenting with test criteria, which are based on relationships between the producer and the consumer of software, we developed a template for test scenarios, using hypothetical distributions of faults and failures. The template was applied to a release of the Shuttle flight software to determine whether hypothetical and real-world results would be consistent. This was not the case; hence, we recommend that practitioners experiment with more than one test criterion to reduce the risk of deploying their software.

Cited by 0

Accelerated Testing for Software Reliability Assessment

Bojan Cukic · 2007

It is necessary to assess the reliability of safety-critical systems to a high degree of confidence before they can be used in the field. One theoretically sound approach for assessing software reliability is to use statistical sampling according to the operational profile. However, this method requires a prohibitive amount of testing. To make this approach more feasible, it is necessary to reduce the time needed to execute a test case. In this paper, we develop transformation methods that speed up the execution of each test case so that a large number of test cases can be run in a shorter time. 1 Introduction Software reliability is becoming a dominant concern in software development, replacing traditional issues such as cost and schedule overruns. This particularly holds for the development of safety-critical process-control systems for aircrafts and space vehicles, emergency shutdown systems in nuclear power plants, military applications, etc. Any failure of these systems can resu...

Cited by 0

Estimating Software Reliability with Hypothesis Testing

Denise M. Woit · 1996

We present a method for estimating software reliability, based on statistical hypothesis testing. Our estimations are based on the current version of the software only, and our method is applicable when the current version has not yet failed any random tests. Our method is particularly useful when one desires reliability estimates that are practical to calculate, and that are more accurate than estimations obtainable with current models. Acknowledgements I would like to thank my supervisor, David Parnas of McMaster University, for his advice support, and guidance. Thanks also goes to Roman ViverosAguilera of McMaster University for his helpful discussions regarding this work. ii Contents 1 Introduction 1 1.1 Applications of our Method . . . . . . . . . . . . . . . . . . . 1 1.1.1 Module Terminology . . . . . . . . . . . . . . . . . . . 1 1.1.2 Memoryless Program Terminology . . . . . . . . . . . . 2 1.1.3 Modes of Use . . . . . . . . . . . . . . . . . . . . . . . 3 2 Relevant Re...

Cited by 0

Application research of software reliability testing

Fuping Zeng, Minyan Lu · 2012

Firstly, the definition and process about Software Reliability Testing (ab. SRT) are introduced, and the existing questions and the corresponding reasons of the SRT are analyzed. Mainly, through an example of SRT a whole process of SRT is investigated, including testing data generation, reliability testing implementation, failure data collection and reliability evaluation, which would provide reference to the further research on SRT.

Cited by 1

Revisiting Software Reliability Modeling and Testing

W. Eric Wong, Jeffrey Voas · Computer · 2024

The 1980s and 1990s were a “golden age” for deep thinkers on the topic of software reliability models and testing. But today that thought leadership has disappeared. In this virtual roundtable we ask, “What happened?”

Cited by 2

Quantifying software reliability using testing effort

Sunil Kumar Khatri, Sijo A John, Rana Majumdar · 2016

Multiple Software Reliability Growth Models (SRGM) has been illustrated to inspire designers and software developers to develop quality software. These models implicitly assume that expenditure is constant throughout testing effort. Recently importance was given to the testing phase by the development team and it requires controlled screening closely to raise its overall operational efficiency. Software Reliability Growth Models exhibits a precise relation between the failure patterns with time. Considering this as a basic building block a SRGM which is a Non-Homogeneous Poisson Process in nature is i in this work. The various aspects of our proposed model are testing effort function and fault detection rate (FDR). Mainly in Software Reliability Growth Model it was assumed that fault removal process are perfect which is not true in reality as new faults may get introduced during removal or some faults may not get removed due to its complexity. Thus in this model the concept of imperfect debugging was considered and assists us to justify the software reliability more convincingly through the help of testing effort function.

Cited by 5