CoChat

A design methodology for reliable software systems

Liskov, B. H. · 1972 · Proceedings of the December 5-7, 1972, fall joint computer conference, part I on - AFIPS '72 (Fall, part I)

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

Crossref · 10.1145/1479992.1480018

Cites

10 of 10 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cites

Show all 10 references

Cited by

See all 107

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.