The DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
Structured Analysis for Requirements Definition
Abstract
Requirements definition encompasses all aspects of system development prior to actual system design. We see the lack of an adequate approach to requirements definition as the source of major difficulties in current systems worlk This paper examines the needs for requirements definition, and proposes meeting those objectives with three interrelated subjects: context analysis, functional specification, and design constraints. Requirements definition replaces the widely used, but never well-defined, term "requirements analysis."
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
Teichroew, D., & Hershey, E. A. (1977) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1977.229902 · Cited by 520
Software and Its Impact: A Quantitative Assessment
BOEHM, B. W. (1972) · Cited by 266
Software Engineering: Process, Principles, and Goals
Ross, D. T., Goodenough, J. B., & Irvine, C. A. (1975) · Computer · doi:10.1109/c-m.1975.218952 · Cited by 87
Self-citation
Cited by
Towards modelling and reasoning support for early-phase requirements engineering
Yu, E. S. K. (2002) · Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering · doi:10.1109/isre.1997.566873 · Cited by 1,579
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Structured Analysis (SA): A Language for Communicating Ideas
Ross, D. T. (1977) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1977.229900 · Cited by 867
Self-citationTelos: representing knowledge about information systems
Mylopoulos, J., Borgida, A., Jarke, M., & Koubarakis, M. (1990) · ACM Transactions on Information Systems · doi:10.1145/102675.102676 · Cited by 786
Handling obstacles in goal-oriented requirements engineering
van Lamsweerde, A., & Letier, E. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.879820 · Cited by 648
Metadata
- Authors
- Ross, D. T., & Schoman, K. E.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1977-01
- Volume
- SE-3
- Issue
- 1
- Pages
- 6-15
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W3904314
- Cited by
- 843
- References
- 3
- FWCI
- 92.12
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Structured Analysis for Requirements Definition. https://app.cochat.ai/papers/10.1109/tse.1977.229899
- The paper
- Ross, D. T., & Schoman, K. E. (1977). Structured Analysis for Requirements Definition. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.1977.229899
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.