Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Steven J. Zeil

dblp:52/5436 · DBLP profile ↗
← Back
13ranked-venue papers
7as first author
0since 2021 · last 1998
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 13 · 7 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
11 papers
Software testing · 90% Program analysis · 5% Programming languages and type systems · 3%

Topics — the 19 heaviest of 21, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › software reliability
order statistic model
0.011998
An Experiment in Estimating Reliability Growth Under Both Representative and Directed Testing · ISSTA 1998
Software testing › software reliability › software reliability modeling
software reliability growth model
0.011998
An Experiment in Estimating Reliability Growth Under Both Representative and Directed Testing · ISSTA 1998
Software testing › automated testing
directed testing
0.011996
A Reliability Model Combining Representative and Directed Testing · ICSE 1996
Software testing
software reliability
0.011996
A Reliability Model Combining Representative and Directed Testing · ICSE 1996
Software testing › software reliability
software reliability modeling
0.011996
A Reliability Model Combining Representative and Directed Testing · ICSE 1996
Software testing
test input generation
0.021992
Testing for Linear Errors in Nonlinear Computer Programs · ICSE 1992
Perturbation Techniques for Detecting Domain Errors · IEEE Trans. Software Eng. 1989
Program analysis
data flow analysis
0.021989
A Formal Evaluation of Data Flow Path Selection Criteria · IEEE Trans. Software Eng. 1989
A Comparison of Data Flow Path Selection Criteria · ICSE 1985
Software testing › specification-based testing
boundary value testing
0.011992
Detection of Linear Errors via Domain Testing · ACM Trans. Softw. Eng. Methodol. 1992
Software testing › specification-based testing
domain testing
0.011992
Detection of Linear Errors via Domain Testing · ACM Trans. Softw. Eng. Methodol. 1992
Software testing
test oracle
0.011992
Testing for Linear Errors in Nonlinear Computer Programs · ICSE 1992
Software testing
test planning
0.011998
An Experiment in Estimating Reliability Growth Under Both Representative and Directed Testing · ISSTA 1998
Runtime systems and virtual machines
interpreter
0.011988
Interpretation in a Tool-Fragment Environment · ICSE 1988
Programming languages and type systems
language semantics
0.011988
Interpretation in a Tool-Fragment Environment · ICSE 1988
Software testing › test adequacy
test adequacy criteria
0.021989
Sufficient Tset Sets for Path Analysis Testing Strategies · ICSE 1981
A Formal Evaluation of Data Flow Path Selection Criteria · IEEE Trans. Software Eng. 1989
Software testing
fault-based testing
0.011984
Perturbation Testing for Computation Errors · ICSE 1984
Software testing
test adequacy
0.011984
Perturbation Testing for Computation Errors · ICSE 1984
Software testing
fault detection
0.011983
Testing for Perturbations of Program Statements · IEEE Trans. Software Eng. 1983
Software testing › test generation › white-box test generation
test path selection
0.011983
Testing for Perturbations of Program Statements · IEEE Trans. Software Eng. 1983
Software testing › structural testing
path testing
0.011981
Sufficient Tset Sets for Path Analysis Testing Strategies · ICSE 1981

Methods — techniques the papers use, named apart from their topics

reliability growth modeling · 0.0order statistic model · 0.0reliability models · 0.0perturbation analysis · 0.0error-space criterion · 0.0subsumption hierarchy · 0.0optimization · 0.0data flow analysis · 0.0vector space analysis · 0.0
YearPublicationVenuePosition
1998 An Experiment in Estimating Reliability Growth Under Both Representative and Directed Testing
abstract
The Order Statistic model of reliability growth offers improved• experimental design, and• flexibility in testing methodologycompared to conventional reliability growth models. It permits prediction of operational reliability without requiring that testing be conducted according to the operation profile of the program input space.This paper presents the first experimental use of the Order Statistic model under a test plan that combines both representative and directed tests. Results suggest that this is an effective way to obtain quantified measures of test quality without abandoning the advantages of directed test methods.
Brian S. Mitchell, Steven J. Zeil
ISSTA2
1996 A Reliability Model Combining Representative and Directed Testing
Steven J. Zeil
ICSE2
1992 Testing for Linear Errors in Nonlinear Computer Programs
abstract
This paper provides an approach to test nonlinear functions in computer programs, whether this function is used for control flow, such as a predicate inequality or equality constraint, or is given as an input-output relationship. This approach will obtain test data to detect linear errors in the given nonlinear function. An error-space criterion previously given by Zeil will be utilized, and a necessary and sufficient condition for the test data will be specified to guarantee the satisfaction of this criterion. This leads to a simple and efficient method to select test data which satisfies that condition; only (n+2) tests are required, where n is the number of input variables. An analysis will be given to show that this simple approach can be very effective in detecting nonlinear errors as well.
Faten H. Afifi, Lee J. White, Steven J. Zeil
ICSE3
1992 Employing Accumulated Knowledge to Refine Test Descriptions
abstract
Abstract Most testing methods generate test descriptions which define the desired characteristics of the input data in a test case. This paper describes the use of accumulated knowledge about a problem domain to refine these test descriptions, with the goal of increasing the probability that the input data generated from the refined test descriptions will reveal faults in a software system. A knowledge base is introduced to hold information about object semantics and object class/subclass relationships. Knowledge accumulates with experience in a particular domain and can be focused on those objects and relationships in that domain which experience has shown to be error‐prone. This paper also defines a knowledge‐driven functional testing (KDFT) method which derives test descriptions from a formal specification and refines these descriptions using that knowledge base. A case study of the KDFT method using data from a previous study of the launch intercept control problem is described. These preliminary results indicate that knowledge‐based refinement of test descriptions can dramatically improve their ability to detect certain classes of faults.
J. Christian Wild, Steven J. Zeil, Gao Feng
Softw. Test. Verification Reliab.2
1992 Detection of Linear Errors via Domain Testing
abstract
Domain testing attempts to find errors in the numeric expressions affecting the flow of control through a program. Intuitively, domain testing provides a systematic form of boundary value testing for the conditional statements within a program. Several forms of domain testing have been proposed, all dealing with the detection of linear errors in linear functions. Perturbation analysis has been previously developed as a measure of the volume of faults, from within a selected space of possible faults, left undetected by a test set. It is adapted here to errors and error spaces. The adapted form is used to show that the different forms of domain testing are closer in error detection ability than had been supposed. They may all be considered effective for finding linear errors in linear predicate functions. A simple extension is proposed, which allows them to detect linear errors in nonlinear predicate functions using only a single additional test point.
Steven J. Zeil, Faten H. Afifi, Lee J. White
ACM Trans. Softw. Eng. Methodol.1
1989 A Formal Evaluation of Data Flow Path Selection Criteria
abstract
The authors report on the results of their evaluation of path-selection criteria based on data-flow relationships. They show how these criteria relate to each other, thereby demonstrating some of their strengths and weaknesses. A subsumption hierarchy showing their relationship is presented. It is shown that one of the major weaknesses of all the criteria is that they are based solely on syntactic information and do not consider semantic issues such as infeasible paths. The authors discuss the infeasible-path problem as well as other issues that must be considered in order to evaluate these criteria more meaningfully and to formulate a more effective path-selection criterion.>
Lori A. Clarke, Andy Podgurski, Debra J. Richardson, Steven J. Zeil
IEEE Trans. Software Eng.4
1989 Perturbation Techniques for Detecting Domain Errors
abstract
Perturbation testing is an approach to software testing which focuses on faults within arithmetic expressions appearing throughout a program. This approach is expanded to permit analysis of individual test points rather than entire paths, and to concentrate on domain errors. Faults are modeled as perturbing functions drawn from a vector space of potential faults and added to the correct form of an arithmetic expression. Sensitivity measures are derived which limit the possible size of those faults that would go undetected after the execution of a given test set. These measures open up an interesting view of testing, in which attempts are made to reduce the volume of possible faults which, were they present in the program being tested, would have escaped detection on all tests performed so far. The combination of these measures with standard optimization techniques yields a novel test-data-generation method called arithmetic fault detection.>
Steven J. Zeil
IEEE Trans. Software Eng.1
1988 Interpretation in a Tool-Fragment Environment
Steven J. Zeil, Edward C. Epp
ICSE1
1988 Complexity of the EQUATE testing strategy
Steven J. Zeil
J. Syst. Softw.1
1985 A Comparison of Data Flow Path Selection Criteria
Lori A. Clarke, Andy Podgurski, Debra J. Richardson, Steven J. Zeil
ICSE4
1984 Perturbation Testing for Computation Errors
Steven J. Zeil
ICSE1
1983 Testing for Perturbations of Program Statements
abstract
Many testing methods require the selection of a set of paths on which tests are to be conducted. Errors in arithmetic expressions within program statements can be represented as perturbing functions added to the correct expression. It is then possible to derive the set of errors in a chosen functional class which cannot possibly be detected using a given test path. For example, test paths which pass through an assignment statement "X := f(Y)" are incapable of revealing if the expression "X -f( Y)" has been added to later statements. In general, there are an infinite number of such undetectable error perturbations for any test path. However, when the chosen functional class of error expressions is a vector space, a finite characterization of all undetectable expressions can be found for one test path, or for combined testing along several paths. An analysis of the undetected perturbations for sequential programs operating on integers and real numbers is presented which permits the detection of multinomial error terms. The reduction of the space of (potential undetected errors is proposed as a criterion for test path selection.
Steven J. Zeil
IEEE Trans. Software Eng.1
1981 Sufficient Tset Sets for Path Analysis Testing Strategies
Steven J. Zeil, Lee J. White
ICSE1