The DOI matches its Crossref record; 22 of the 22 references it cites were found in a registry or an index.
LaSSIE: a knowledge-based software information system
Open accessAbstract
The growing cost of software development, particularly in larger systems, is well documented.Efforts at containing this growth have met with limited success.In his classic paper, "No Silver Bullet" [11], Brooks attempts to explain this; he argues that existing developments in software engineering, such as high-level languages, time-sharing and integrated programming environments have overcome certain accidental difficulties in the software development process.However, certain other problems that are the essence of the software process remain.He identifies four essential difficulties in building large software systems as follows:• Complexity: The complexity of the development process, the application domain, the internals of the system, etc.• Conformity: Software cannot have a regular formal structure (like Mathematics or Physics) because it must adapt to interact with people and institutions according to their diverse needs.• Changeability: In any system, the software component is usually the easiest one to modify.• Invisibility: The structure of software (unlike that of buildings or automobiles) is hidden.The only external evidence we have of software is its behavior when executing.
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
Cites
No Silver Bullet Essence and Accidents of Software Engineering
Brooks (1987) · Computer · doi:10.1109/mc.1987.1663532 · Cited by 3,186
A field study of the software design process for large systems
Curtis, B., Krasner, H., & Iscoe, N. (1988) · Communications of the ACM · doi:10.1145/50087.50089 · Cited by 2,076
An overview of the KL-ONE Knowledge Representation System
BRACHMAN, R., & SCHMOLZE, J. (1985) · Cognitive Science · doi:10.1016/s0364-0213(85)80014-8 · Cited by 1,772
Self-citationEmpirical Studies of Programming Knowledge
Soloway, E., & Ehrlich, K. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010283 · Cited by 877
Classifying Software for Reusability
Prieto-Díaz, R., & Freeman, P. (1987) · IEEE Software · doi:10.1109/ms.1987.229789 · Cited by 696
Learning to program = learning to construct mechanisms and explanations
Soloway, E. (1986) · Communications of the ACM · doi:10.1145/6592.6594 · Cited by 567
CLASSIC: a structural data model for objects
Borgida, A. T., Brachman, R. J., McGuinness, D. L., & Resnick, L. A. (1989) · ACM SIGMOD Record · doi:10.1145/66926.66932 · Cited by 498
Self-citationCambridge University Press, 1696–1712: A Bibliographical Study
McKenzie, D. F. (2010) · Cambridge University Press eBooks · doi:10.1017/cbo9781139197373 · Cited by 405
The Role of Domain Expenence in Software Design
Adelson, B., & Soloway, E. (1985) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1985.231883 · Cited by 394
Design recovery for maintenance and reuse
Biggerstaff, T. J. (1989) · Computer · doi:10.1109/2.30731 · Cited by 359
Expressiveness and tractability in knowledge representation and reasoning1
Levesque, H. J., & Brachman, R. J. (1987) · Computational Intelligence · doi:10.1111/j.1467-8640.1987.tb00176.x · Cited by 320
Self-citationPROUST: Knowledge-Based Program Understanding
Johnson, W. L., & Soloway, E. (1985) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1985.232210 · Cited by 284
The C information abstraction system
Chen, Y.-F., Nishimoto, M. Y., & Ramamoorthy, C. V. (1990) · IEEE Transactions on Software Engineering · doi:10.1109/32.48940 · Cited by 278
Designing documentation to compensate for delocalized plans
Soloway, E. M., Lampert, R., Letovsky, S., Littman, D., & Pinto, J. (1988) · Communications of the ACM · doi:10.1145/50087.50088 · Cited by 192
Doyle, J., & Patil, R. S. (1991) · Artificial Intelligence · doi:10.1016/0004-3702(91)90029-j · Cited by 168
Domain analysis: from art form to engineering discipline
Arango, G. (1989) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/75200.75224 · Cited by 130
Domain analysis: from art form to engineering discipline
Arango, G. (1989) · International Workshop on Software Specification and Design · doi:10.1145/75199.75224 · Cited by 88
Cognitive processes in program comprehension
Letovsky, S. I. (1986) · Cited by 61
Prototyping a project master database for software engineering environments
Penedo, M. H. (1987) · ACM SIGPLAN Notices · doi:10.1145/390012.24209 · Cited by 44
Generic lifecycle support in the ALMA environment
van Lamsweerde, A., Delcourt, B., Delor, E., Schayes, M. C., & Champagne, R. (1988) · IEEE Transactions on Software Engineering · doi:10.1109/32.6153 · Cited by 37
Prototyping a project master database for software engineering environments
Penedo, M. H. (1987) · Software Engineering Symposium on Practical Software Development Environments · doi:10.1145/24208.24209 · Cited by 29
SODOS—a software documentation support environment: its use
Horowitz, E., & Williamson, R. C. (1985) · doi:10.5555/319568.319571 · Cited by 7
Cited by
An analysis of the requirements traceability problem
Gotel, O. C. Z., & Finkelstein, C. W. (2002) · Proceedings of IEEE International Conference on Requirements Engineering · doi:10.1109/icre.1994.292398 · Cited by 1,246
Knowledge management in software engineering
Rus, I., & Lindvall, M. (2002) · IEEE Software · doi:10.1109/ms.2002.1003450 · Cited by 742
Software reflexion models: bridging the gap between design and implementation
Murphy, G. C., Notkin, D., & Sullivan, K. J. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.917525 · Cited by 398
Event-based traceability for managing evolutionary change
Cleland-Huang, J., Chang, C. K., & Christensen, M. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1232285 · Cited by 288
Knowledge-based approaches in software documentation: A systematic literature review
Ding, W., Liang, P., Tang, A., & van Vliet, H. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.01.008 · Cited by 107
Metadata
- Authors
- Devanbu, P., Brachman, R., Selfridge, P. G., & Ballard, B. W.
- Venue
- Communications of the ACM
- Published
- 1991-05
- Volume
- 34
- Issue
- 5
- Pages
- 34-49
- ISSN
- 0001-0782 (ISSN-L)
- 1557-7317
- OpenAlex
- W1965982049
- Cited by
- 340
- References
- 22
- FWCI
- 100.88
- 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
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.