Structured testing :
Published 1 January 1996Open access
Dolores R Wallace, Arthur H. Watson, Thomas J. McCabe
Citations318
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
This document summarizes current capabilities, research and operational priorities, and plans for further studies that were established at the 2015 USGS workshop on quantitative hazard assessments of earthquake-triggered landsliding and liquefaction in the Central American region.
Abstract
that satisfies the structured testing criterion, which consists of the three tests from Figure Input Output Correctness X -1 Correct ABCX 1 Correct Rgure 5-4. Tests for "count" that satisfy statement and branch coverage. Input Output Correctness X -1 Correct ABCX 1 Correct A 0 Correct AB 1 Incorrect AC 0 Incorrect Figure 5-5. Tests for "count" that satisfy the structured testing criterion.
Keywords
Computer Science
Psychological ReviewThe magical number seven, plus or minus two: Some limits on our capacity for processing information.
17,276 Citations1994George Miller
About some experiments that tested how accurately people can assign numbers to the magnitudes of various aspects of a stimulus, and since the results are analyzed in terms of the concepts of information theory, I shall have to preface my discussion with a few remarks about this theory.
Mathematics and Computers in SimulationIntroduction to automata theory, languages and computation
10,827 Citations1981
Advances in Engineering Software (1978)Software engineering: A practitioner's approach
8,290 Citations1983
Software Engineering A Practitioner's Approach recognizes the dramatic growth in the field of software engineering and emphasizes new and important methods and tools used in the industry.
Communications of the ACMOn the criteria to be used in decomposing systems into modules
4,674 Citations1972David Lorge Parnas
Safeware: System Safety and Computers
1,665 Citations1995Nancy G. Leveson
SpringerReferencestructured programming
1,201 Citations2011
Much work is needed to determine how best to design and implement software with reliability, maintainability, and extensibility; there are already some techniques known that contribute materially to these aims.
Structured programming
889 Citations1972Olle Dahl, E. Dijkstra +1 more
Towards a metrics suite for object oriented design
832 Citations1991Shyam R. Chidamber, Chris F. Kemerer
These metrics are based upon measurement theory and are informed by the insights of experienced object-oriented software developers, and formally evaluated against a widelyaccepted list of software metric evaluation criteria.
Software Practice and ExperienceAn empirical study of FORTRAN programs
682 Citations1971Donald E. Knuth
The principal conclusion which may be drawn is the importance of a program ‘profile’, namely a table of frequency counts which record how often each statement is performed in a typical run; there are strong indications that profile‐keeping should become a standard practice in all computer systems, for casual users as well as system programmers.
Structured design
614 Citations1979W. P. Stevens, G. J. Myers +1 more
ComputerUsing metrics to evaluate software system maintainability
417 Citations1994Derek Coleman, Dan Ash +2 more
Software complexity metrics rarely measure the "inherent complexity" embedded in software systems, but they do a very good job of comparing the relative complexity of one portion of a system with another.
Communications of the ACMDesign complexity measurement and testing
369 Citations1989Thomas J. McCabe, Charles W. Butler
IEEE Transactions on Software EngineeringMethodology for validating software metrics
351 Citations1992Norman F. Schneidewind
The author shows that nonparametric statistical methods such as contingency tables play an important role in evaluating metrics against the validity criteria, and examples emphasizing the discriminative power validity criterion are presented.
IEEE SoftwareSoftware testability: the new verification
327 Citations1995J. Voas, Keith Miller
The authors present the benefits of their approach, describe how to design for it, and show how to measure testability through sensitivity analysis.
On the Criteria To Be Used in Decomposing Systems into Modules
307 Citations2002David Lorge Parnas
ComputerIdentifying and qualifying reusable software components
294 Citations1991Gianluigi Caldiera, Victor R. Basili
The results show that automated techniques can reduce the amount of code that a domain expert needs to evaluate to identify reusable parts.
ACM SIGPLAN NoticesTowards a metrics suite for object oriented design
249 Citations1991Shyam R. Chidamber, Chris F. Kemerer
IEEE Transactions on Software EngineeringCyclomatic complexity density and software maintenance productivity
229 Citations1991Geoffrey K. Gill, Chris F. Kemerer
A simple transformation of the metric is investigated whereby the cyclomatic complexity is divided by the size of the system in source statements, thereby determining a complexity density ratio, which is demonstrated to be a useful predictor of software maintenance productivity on a small pilot sample of maintenance projects.
IEEE Transactions on Software EngineeringThe Use of Software Complexity Metrics in Software Maintenance
214 Citations1987Dennis Kafura, Ram Mohana Reddy Guddeti
This paper reports on a modest study which relates seven different software complexity metrics to the experience of maintenance activities performed on a medium size software system.
Medical Entomology and ZoologyThe complete guide to software testing
207 Citations1984W. Hetzel, Bill Hetzel
This completely revised edition features new chapters on testing methodologies such as ANSI standard-based testing and a survey of testing practices.
IEEE SoftwareEarly quality prediction: a case study in telecommunications
199 Citations1996Taghi M. Khoshgoftaar, Edward B. Allen +2 more
The authors applied discriminant analysis to identify fault-prone modules in a large telecommunications system prior to testing to predict the quality of modules.
The Journal of Data EducationThe Elements of Programming Style
166 Citations1973Charles B. Kreitzberg, Ben Shneiderman
ACM SIGPLAN NoticesAn extension to the cyclomatic measure of program complexity
148 Citations1977Glenford J. Myers
A graph-theoretic measure of program complexity, where a program's complexity is assumed to be only a factor of the program's decision structure, is described and a simple extension to the measure is described to eliminate anomalies.
Communications of the ACMSystem structure and software maintenance performance
140 Citations1989Virginia R. Gibson, James A. Senn
Results indicate that system improvements lead to decreased total maintenance time and decreased frequency of ripple effect errors, which suggests that improving old systems may be worthwhile and may yield benefits over the remaining life of the system.
IEEE Transactions on Software EngineeringAn Experiment in Software Error Data Collection and Analysis
127 Citations1979Norman F. Schneidewind, H.-M. Hoffmann
An experiment in software error data collection and analysis was conducted in order to study relationships between complexity measures and error charateristics under conditions where the error data could be carefully defined and collected.
IEEE SoftwareQuantifying software validation: when to stop testing?
105 Citations1989Donald Musa, Aidan Ackerman
The authors explain how to use reliability models to determine how much system testing to do and how to allocate resources among the components to be tested, and examine the functions, presuppositions, and basic procedures of system testing.
IEEE Transactions on Software EngineeringOn the use of testability measures for dependability assessment
101 Citations1996Antonia Bertolino, Lorenzo Strigini
It is shown that a high testability is not an unconditionally desirable property for a program, and for programs complex enough that they are unlikely to be completely fault free, increasing testability may produce a program which will be less trustworthy, even after successful testing.
ACM SIGMETRICS Performance Evaluation ReviewOn the relationships among three software metrics
87 Citations1981Sallie M. Henry, Dennis Kafura +1 more
IEEE Transactions on Software EngineeringThe consistent comparison problem in N-version software
72 Citations1989Susan S. Brilliant, John Knight +1 more
A method to determine a basis set of paths to perform program testing
39 Citations1995Joseph Poole
On the relationships among three software metrics
32 Citations1981Sallie M. Henry, Dennis Kafura +1 more
The primary result of this study is that Halstead's and McCabe's metrics are highly correlated while the information flow metric appears to be an independent measure of complexity.
1979 International Workshop on Managing Requirements Knowledge (MARK)A software reliability study using a complexity measure
28 Citations1979Thomas J. Walsh
The complexity of the computer system will defeat the designer's efforts unless a relatively simple way is found to break the problem down in order that the resulting programs are testable and maintainable.
IEEE SoftwareCyclomatic complexity and the year 2000
21 Citations1996Thomas J. McCabe
This article elaborate on an adaptation of the cyclomatic complexity measure to quantify and derive the specific tests for date conversion and originated the use of cyclomatic simplicity as a software metric.
ACM SIGSOFT Software Engineering NotesThe consistent comparison problem in <i>N</i> -version software
20 Citations1987Susan S. Brilliant, John Knight +1 more
Proceedings. 26th International Conference on Software EngineeringTesting object-oriented software
14 Citations2004Mauro Pezzè, M. Young
A general approach that works in stages from independent consideration of classes and their features to consideration of their interactions is outlined, which would include three main phases: intraclass, interclass, and system and acceptance testing.
Communications of the ACMTechnical Correcspondence
13 Citations1994Issa Feghali, Arthur H. Watson +2 more
It will point out the analytical flaws behind Henderson-Sellers' proposed modification of the cyclomatic complexity fornmla, and then relate the modification to the integration complexity measure of McCabe and Butler.
Structured testing: analysis and extensions
7 Citations1996Arthur H. Watson
This dissertation analyzes the theoretical properties of structured testing, describes the implementation of a system to support structuredTesting, empirically evaluate the error detection performance of Structured testing, and extends the structured testing approach to cover integration testing.
Computers & Industrial EngineeringProducing maintainable software
4 Citations1987Doris L. Carver
A study of complexity increases during the testing and debugging phases of the software life cycle using complexity metrics as a technique for controlling software complexity.
Defense Technical Information Center (DTIC)The Effects of the Symbology and Spatial Arrangement of Software Specifications in a Coding Task.
4 Citations1981Sheppard,Sylvia B, Kruesi,Elizabeth