The DOI matches its Crossref record; 10 of the 10 references it cites were found in a registry or an index.
Design for testability in object-oriented systems
Open accessAbstract
Design #or TestabiMtyObject-Oriented Systems estability is the relative ease and expense of revealing software faults.This article maps the testability terrain for object-oriented development to assist the reader in finding relatively shorter and cheaper paths to high reliability.Software testing adds value by revealing faults.It is fundamentally an economic problem characterized by a continuum between two goals.A reliability-dtiven process uses testing to produce evidence that a pre-release reliability goal has been met.Time and money are expended on testing until the reliability goal is attained.This view of testing is typically associated with stringent, quantifiable reliability requirements.Other things being equal, a more testable system will reduce the time and cost needed to meet reliability goals.A resource-limited process views testing as a way to remove as many rough edges from a system as time or money permits.Testing continues until available test resources have been expended.Measurement of test adequacy or system reliability are incidental to the decision to release the system.This is the typical view of testing.Other things being equal, a more testable system provides increased reliability for a fixed testing budget.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Deming, W. E. (1982) · Medical Entomology and Zoology · Cited by 7,297
A metrics suite for object oriented design
Chidamber, S. R., & Kemerer, C. F. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.295895 · Cited by 5,669
Object-Oriented Software Construction
Meyer, B. (1988) · UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno · Cited by 4,011
(2014) · African Studies Companion Online · doi:10.1163/1872-9037_afco_dum_r0022a · Cited by 1,664
Object Oriented Software Engineering: A
Jacobson, I. (1991) · Cumulative Index of Computer Aided Architectural Design · Cited by 1,174
Software testing techniques (2nd ed.)
Beizer, B. (1990) · Cited by 744
On testing non-testable programs
Weyuker, E. J. (1982) · The Computer Journal · doi:10.1093/comjnl/25.4.465 · Cited by 606
The ASTOOT approach to testing object-oriented programs
Doong, R.-K., & Frankl, P. G. (1994) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/192218.192221 · Cited by 321
Software System Testing and Quality Assurance
Beizer, B. (1984) · Medical Entomology and Zoology · Cited by 315
Planning the software industrial revolution
Cox, B. J. (1990) · IEEE Software · doi:10.1109/52.60587 · Cited by 154
Cited by
Introduction to Software Testing
(2021) · Essentials of Software Testing · doi:10.1017/9781108974073.004 · Cited by 1,056
Metadata
- Authors
- Binder, R. V.
- Venue
- Communications of the ACM
- Published
- 1994-09
- Volume
- 37
- Issue
- 9
- Pages
- 87-101
- ISSN
- 0001-0782 (ISSN-L)
- 1557-7317
- OpenAlex
- W1964497219
- Cited by
- 271
- References
- 10
- FWCI
- 13.69
- Type
- journal article
- Language
- en
- Open access
- bronze
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: Design for testability in object-oriented systems. https://app.cochat.ai/papers/10.1145/182987.184077
- The paper
- Binder, R. V. (1994). Design for testability in object-oriented systems. Communications of the ACM. https://doi.org/10.1145/182987.184077
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.