The DOI matches its Crossref record.
Reusing and Interconnecting Software Components
Abstract
This article covers some problems, concepts, and approaches relevant to environments for creating, documenting, and maintaining large software systems. The goal is to make programming significantly easier, more reliable, and cost effective by reusing previous code and programming experience to the greatest extent possible. Suggestions given here include: systematic (but limited) use of semantics, by explicitly attaching theories (which give semantics, either formal or informal) to software components with views (which describe semantically correct interconnections at component interfaces); use of generic entities, to maximize reusability; a distinction between horizontal and vertical composition; use of a library interconnection language, called LIL, to assemble large programs from existing entities; support for different levels of formality in both documentation and validation; and facilitation of program understanding by animating abstract data types and module interfaces. ADA is used for examples because it has some convenient features, but the proposals also apply to other languages.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
Cited by
A component- and message-based architectural style for GUI software
Taylor, R. N., Medvidovic, N., Anderson, K. M., Whitehead, E. J., Robbins, J. E., Nies, K. A., Oreizy, P., & Dubrow, D. L. (1996) · IEEE Transactions on Software Engineering · doi:10.1109/32.508313 · Cited by 325
Abstract data views: an interface specification concept to enhance design for reuse
Cowan, D. D., & Lucena, C. J. P. (1995) · IEEE Transactions on Software Engineering · doi:10.1109/32.372150 · Cited by 103
Metadata
- Authors
- Goguen
- Venue
- Computer
- Published
- 1986-02
- Volume
- 19
- Issue
- 2
- Pages
- 16-28
- ISSN
- 0018-9162 (ISSN-L)
- OpenAlex
- W2010315125
- Cited by
- 209
- References
- 0
- FWCI
- 9.00
- Type
- journal article
- Language
- en
- Open access
- closed
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
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.