1995
DOI: 10.1109/52.382180
|View full text |Cite
|
Sign up to set email alerts
|

Software testability: the new verification

Abstract: Software veri cation encompasses a wide range of techniques and activities that are geared towards demonstrating that software is reliable. Veri cation techniques such as testing provide a way t o assess the likelihood that software will fail during use. This paper introduces a di erent t y p e o f v eri cation that shows how l i k ely it is that an incorrect program will not fail. Our veri cation applies fault-injection methods to predict where actual faults are more likely to hide. This veri cation can be co… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
116
0
7

Year Published

1999
1999
2014
2014

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 253 publications
(124 citation statements)
references
References 5 publications
1
116
0
7
Order By: Relevance
“…Voas defines testability as the probability that a test case will fail if a program has a fault [26]. Voas and Miller [27] propose a testability metric based on inputs and outputs domains of a software component, and the PIE (Propagation, Infection and Execution) technique to analyze software testability [28]. Binder [29] defines testability as the relative ease and expense of revealing software faults.…”
Section: Software Testabilitymentioning
confidence: 99%
“…Voas defines testability as the probability that a test case will fail if a program has a fault [26]. Voas and Miller [27] propose a testability metric based on inputs and outputs domains of a software component, and the PIE (Propagation, Infection and Execution) technique to analyze software testability [28]. Binder [29] defines testability as the relative ease and expense of revealing software faults.…”
Section: Software Testabilitymentioning
confidence: 99%
“…According to the IEEE Glossary of Software Engineering Terminology [1], testability is defined as "the degree to which a system of components facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met". Voas and Miller [9], and later Bertolino and Stringini [2] clarify this definitions, arguing that testability is "the probability that the program will fail under test if it contains at least one fault". If LURCH1 quickly reveals many unique reachable nodes in the model quickly and if some of these nodes contain faulty logic, then those faults must be exposed.…”
Section: Testabilitymentioning
confidence: 99%
“…Stakeholders may be interested in other system attributes as well, such as the "-ilities." Examples include survivability , testability (Voas and Miller 1995), modularity (Huang and Kusiak 1998), and scalability (Jogalekar and Woodside 2000). When possible, these other attributes can be translated into utility so that they may be INCOSE Int'l Symposium 2012 Pre-print Version evaluated in tradespace studies, but this conversion to utility can be very difficult to operationalize, particularly if these attributes are poorly defined, are functions of utility themselves, or are not properly understood by the stakeholders (McManus et al 2007).…”
Section: The Impact Of Conops Choices On System Effectivenessmentioning
confidence: 99%