A design methodology for reliable software systems
The DOI matches its Crossref record; 10 of the 10 references it cites were found in a registry or an index.
Abstract
Any user of a computer system is aware that current systems are unreliable because of errors in their software components. While system designers and implementers recognize the need for reliable software, they have been unable to produce it. For example, operating systems such as OS/360 are released to the public with hundreds of errors still in them.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
On the criteria to be used in decomposing systems into modules
Parnas, D. L. (1972) · Communications of the ACM · doi:10.1145/361598.361623 · Cited by 4,704
The structure of the “THE”-multiprogramming system
Dijkstra, E. W. (1968) · Communications of the ACM · doi:10.1145/363095.363143 · Cited by 1,094
Conway, M. E. (1967) · Cited by 812
Chief programmer team management of production programming
Baker, F. T. (1972) · IBM Systems Journal · doi:10.1147/sj.111.0056 · Cited by 325
Information distribution aspects of design methodology
Parnas, D. L. (2018) · KiltHub Repository · doi:10.1184/r1/6606470.v1 · Cited by 315
Information distribution aspects of design methodology
Parnas, D. L. (2018) · KiltHub Repository · doi:10.1184/r1/6606470 · Cited by 312
The design of the Venus operating system
Liskov, B. H. (1972) · Communications of the ACM · doi:10.1145/361268.361272 · Cited by 98
Self-citationBuxton, J. N., & Randell, B. (1970) · Cited by 85
An experiment in structured programming
Henderson, P., & Snowdon, R. A. (1972) · BIT Numerical Mathematics · doi:10.1007/bf01932672 · Cited by 61
A modular approach to file system design
Madnick, S., & Alsop, J. W. (1969) · AFIPS Spring Joint Computer Conference (SJCC) · doi:10.1145/1476793.1476795 · Cited by 28
Cited by
A universal modular ACTOR formalism for artificial intelligence
Hewitt, C. E., Bishop, P., & de Steiger, R. (1973) · International Joint Conference on Artificial Intelligence · Cited by 927
Programming with abstract data types
Liskov, B., & Zilles, S. (1974) · Proceedings of the ACM SIGPLAN symposium on Very high level languages - · doi:10.1145/800233.807045 · Cited by 734
Self-citationProgramming-in-the large versus programming-in-the-small
DeRemer, F., & Kron, H. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808431 · Cited by 574
Exception handling: issues and a proposed notation
Goodenough, J. B. (1975) · Communications of the ACM · doi:10.1145/361227.361230 · Cited by 496
“They are needed, in general, as a means of conveniently interleaving actions belonging to different levels of abstraction [2-7].”
BackgroundSpecification techniques for data abstractions
Liskov, B., & Zilles, S. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808426 · Cited by 364
Self-citation
Metadata
- Authors
- Liskov, B. H.
- Affiliations
- Mitre (United States) (US)
- Corresponding author
- Liskov, B. H.
- Venue
- Proceedings of the December 5-7, 1972, fall joint computer conference, part I on - AFIPS '72 (Fall, part I)
- Publisher
- ACM Press
- Published
- 1972
- Pages
- 191
- OpenAlex
- W1976100766
- Cited by
- 107
- References
- 9
- Citations by year
- 2024: 1 · 2023: 2 · 2021: 6 · 2020: 1 · 2018: 1 · 2016: 1 · 2014: 3 · 2013: 1
- Type
- conference abstract
- Language
- en
- Open access
- closed
- Locations
- AFIPS Fall Joint Computer Conference (FJCC) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Software › Software Reliability and Analysis Research
- Physical Sciences › Computer Science › Computer Networks and Communications › Distributed systems and fault tolerance
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Keywords
- software reliability, software errors, software components, operating systems, design methodology
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A design methodology for reliable software systems. https://app.cochat.ai/papers/10.1145/1479992.1480018
- The paper
- Liskov, B. H. (1972). A design methodology for reliable software systems. Proceedings of the December 5-7, 1972, fall joint computer conference, part I on - AFIPS '72 (Fall, part I). https://doi.org/10.1145/1479992.1480018
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.