article

Free access

A benefit analysis of some software reliability methodologies

Author:

Robert L. GlassAuthors Info & Claims

ACM SIGSOFT Software Engineering Notes, Volume 5, Issue 2

Pages 26 - 33

https://doi.org/10.1145/1010792.1010797

Published: 01 April 1980 Publication History

PDF eReader

References

[1]

(ENDR75) "An Analysis of Errors and Their Causes in System Programs," IEEE Transactions on Software Engineering, June 1975; Endres. Reviews errors detected in a large assembler-coded operating system. Studies causes of errors, and detection and prevention methodologies. States "almost half of all errors (45 percent) are found in the area of understanding the problem."

Google Scholar

[2]

(GLAS79) Software Reliability Guidebook, Prentice-Hall, 1979; Glass. Surveys the available technological and managerial software reliability techniques. Makes value judgments about each technique; illustrates each by example.

Digital Library

Google Scholar

[3]

(GODO77) "Software Sneak Analysis," Proceedings of the AIAA Conference on Computers in Aerospace, 1977; Godoy and Engels. Describes a methodology based on hardware sneak-circuit-analysis techniques which involves converting a computer program into a hardware circuit representation, and analyzing the circuit for certain kinds of structural faults.

Google Scholar

[4]

(HOWD78) "An Evaluation of the Effectiveness of Symbolic Testing," Software Practice and Experience, July 1978; Howden. Evaluates several different debugging methodologies on their ability to detect errors. Finds symbolic testing particularly promising.

Google Scholar

[5]

(HOWD78A) "Functional Program Testing," University of Victoria Report DM-146-IR, 1978; Howden. Analyzes errors in a scientific library to determine what techniques could have detected them. Advocates "functional testing" (the testing of each function performed by the program) combined with "branch testing" (the testing of all program logic segments).

Google Scholar

[6]

(HOWD79) "An Analysis of Software Validation Techniques for Scientific Programs," University of Victoria Report DM-171-IR, 1979; Howden. A more comprehensive report on the studies of HOWD78A.

Google Scholar

[7]

(JACK71) "Software Validation of the Titan IIIC Digital Flight Control System Using a Hybrid Computer," Proceedings of the 1971 Fall Joint Computer Conference; Jackson and Bravdica. Describes a specific environment simulator--the Titan IIIC mission, the configuration of the test system, and its use in the software development process.

Google Scholar

[8]

(MYER78) "A Controlled Experiment in Program Testing and Code Walkthroughs/Inspections," Communications of the ACM, September 1978; Myers. Sees peer code review as a necessary but somewhat expensive component of the overall checkout process. Suggests the evolution of computer-assisted review techniques.

Digital Library

Google Scholar

[9]

(NG78) "A 1900 Fortran Postmortem Dump System," Software Practice and Experience, July 1978; Ng and Young. Describes a source language debug tool which includes Fortran language dumps, and data and logic tracing.

Google Scholar

[10]

(PAIG77) "Software Testing Principles and Practice Using a Testing Coverage Analyzer," Transactions of the Software '77 Conference, October 1977; Paige. The test coverage analyzer is defined and illustrated, with sample analyzer outputs shown. Testing strategies using an analyzer are discussed.

Google Scholar

[11]

(SCHN79) "An Experiemnt in Software Error Data Collection and Analysis," Transactions on Software Engineering, May 1979; Schneidewind and Hoffman. Analyzes errors and complexity measures. Concludes that program structure, measurable by complexity techniques, has a significant impact on the existence, detection, and correction of errors.

Google Scholar

[12]

(STUC75) "New Assertion Concepts for Self Metric Software Validation," Proceedings of the 1975 IEEE International Conference on Reliable Software; Stucki and Foshee. The PET (Program Evaluator and Test) system is described. Emphasis is placed on its assertion checker capabilities. Examples and attendant output are shown.

Digital Library

Google Scholar

[13]

(WEIS78) "Evaluating Software Development by Error Analysis," Naval Research Lab NRL-8268, December 1978; Weiss. Uses error analysis and programmer interviews to study error occurrences. Postulates an error-detection methodology, and discusses an instance of its use.

Google Scholar

Cited By

View all

Roach S(2011)Retrospectives in a software engineering project courseProceedings of the 2011 24th IEEE-CS Conference on Software Engineering Education and Training10.1109/CSEET.2011.5876126(467-471)Online publication date: 22-May-2011
https://dl.acm.org/doi/10.1109/CSEET.2011.5876126
Taylor R(2006)An integrated verification and testing environmentSoftware: Practice and Experience10.1002/spe.438013080513:8(697-713)Online publication date: 30-Oct-2006
https://doi.org/10.1002/spe.4380130805
Glass R(2006)Real‐time checkout: The ‘source error first’ approachSoftware: Practice and Experience10.1002/spe.438012010812:1(77-83)Online publication date: 27-Oct-2006
https://doi.org/10.1002/spe.4380120108
Show More Cited By

A benefit analysis of some software reliability methodologies
1. Software and its engineering
  1. Software creation and management
    1. Software verification and validation
      1. Software defect analysis

Recommendations

Empirical Study of Agile Software Development Methodologies: A Comparative Analysis

In today's software industry, technological prowess and ever-evolving customer requirements have led to more complex software demands. Agile based software development is increasingly being adopted by the software practitioners as it assures early ...
Methodologies for the cost-benefit analysis of computer graphics systems
SIGGRAPH '74: Proceedings of the 1st annual conference on Computer graphics and interactive techniques

This paper assesses the state of the art in cost-benefit analyses of computer graphics systems and suggests an approach for developing improved methodology. Cost-benefit analyses are distinguished from analyses of system performance in that the latter ...
A curriculum for agile software development methodologies

Agile software development methodologies are proliferating in software development organizations. Agile techniques can handle changing business requirements, schedule, cost, personnel turnover in an effective way in organizations. Here, major components ...

Comments

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes

ACM SIGSOFT Software Engineering Notes Volume 5, Issue 2

April 1980

32 pages

ISSN:0163-5948

DOI:10.1145/1010792

Issue’s Table of Contents

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 April 1980

Published in SIGSOFT Volume 5, Issue 2

Check for updates

Qualifiers

Article

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

6
Total Citations
View Citations
376
Total Downloads

Downloads (Last 12 months)27
Downloads (Last 6 weeks)1

Reflects downloads up to 06 Jan 2025

Other Metrics

View Author Metrics

Citations

Cited By

View all

Roach S(2011)Retrospectives in a software engineering project courseProceedings of the 2011 24th IEEE-CS Conference on Software Engineering Education and Training10.1109/CSEET.2011.5876126(467-471)Online publication date: 22-May-2011
https://dl.acm.org/doi/10.1109/CSEET.2011.5876126
Taylor R(2006)An integrated verification and testing environmentSoftware: Practice and Experience10.1002/spe.438013080513:8(697-713)Online publication date: 30-Oct-2006
https://doi.org/10.1002/spe.4380130805
Glass R(2006)Real‐time checkout: The ‘source error first’ approachSoftware: Practice and Experience10.1002/spe.438012010812:1(77-83)Online publication date: 27-Oct-2006
https://doi.org/10.1002/spe.4380120108
Mili AGuemara SJaoua ATorrés P(1987)On the use of executable assertions in structured programsJournal of Systems and Software10.1016/0164-1212(87)90004-57:1(15-28)Online publication date: Mar-1987
https://doi.org/10.1016/0164-1212(87)90004-5
Strigini LAvižienis A(1985)Software Fault-Tolerance and Design Diversity: Past Experience and Future EvolutionIFAC Proceedings Volumes10.1016/S1474-6670(17)60101-018:12(167-172)Online publication date: Oct-1985
https://doi.org/10.1016/S1474-6670(17)60101-0
Mili A(1982)Self-Stabilizing ProgramsIEEE Transactions on Computers10.1109/TC.1982.167606731:7(685-689)Online publication date: 1-Jul-1982
https://dl.acm.org/doi/10.1109/TC.1982.1676067

View Options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

References

Cited By

Recommendations

Empirical Study of Agile Software Development Methodologies: A Comparative Analysis

Methodologies for the cost-benefit analysis of computer graphics systems

A curriculum for agile software development methodologies

Comments

Information

Published In

Publisher

Publication History

Check for updates

Qualifiers

Contributors

Other Metrics

Bibliometrics

Article Metrics

Other Metrics

Citations

Cited By

View options

PDF

eReader

Login options

Full Access

Figures

Other

Share

Share this Publication link

Share on social media

Affiliations