The DOI matches its Crossref record; 10 of the 10 references it cites were found in a registry or an index.
Requirements engineering as a success factor in software projects
Abstract
Defficient requirements are the single biggest cause of software project failure. From studying several hundred organizations, Gapers Jones discovered that RE is deficient in more than 75 percent of all enterprises,(1) In other words, getting requirements right might be the single most important and difficult part of a software project. Despite its importance, we know surprisingly little about the actual process of specifying software. "The RE Process" sidebar provides a basic description.
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
Software Engineering Economics
Boehm, B. W. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_5 · Cited by 5,981
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
Software engineering economics: background, current practices, and future directions
Erdogmus, H., Boehm, B. W., Harrison, W., Reifer, D. J., & Sullivan, K. J. (2002) · Proceedings of the 24th international conference on Software engineering - ICSE '02 · doi:10.1145/581441.581444 · Cited by 711
Guinan, P. J., Cooprider, J. G., & Faraj, S. (1998) · Information Systems Research · doi:10.1287/isre.9.2.101 · Cited by 341
A review of the state of the practice in requirements modeling
Lubars, M., Potts, C., & Richter, C. (2002) · [1993] Proceedings of the IEEE International Symposium on Requirements Engineering · doi:10.1109/isre.1993.324842 · Cited by 225
Nidumolu, S. R. (1996) · Journal of Management Information Systems · doi:10.1080/07421222.1996.11518124 · Cited by 183
A field study of requirements engineering practices in information systems development
El Emam, K., & Madhavji, N. H. (2002) · Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95) · doi:10.1109/isre.1995.512547 · Cited by 181
Macaulay, L. A. (1996) · Applied computing · doi:10.1007/978-1-4471-1005-7 · Cited by 156
Applied software measurement (2nd ed.): assuring productivity and quality
Jones, C. (1996) · McGraw-Hill, Inc. eBooks · Cited by 76
Doherty, N. F., & King, M. (1998) · Behaviour and Information Technology · doi:10.1080/014492998119661 · Cited by 63
Cited by
Requirements Elicitation: A Survey of Techniques, Approaches, and Tools
Zowghi, D., & Coulin, C. (2006) · Engineering and Managing Software Requirements · doi:10.1007/3-540-28244-0_2 · Cited by 430
A survey of traceability in requirements engineering and model-driven development
Winkler, S., & von Pilgrim, J. (2010) · Software & Systems Modeling · doi:10.1007/s10270-009-0145-0 · Cited by 313
Designing a multi-sided data platform: findings from the International Data Spaces case
Otto, B., & Jarke, M. (2019) · Electronic Markets · doi:10.1007/s12525-019-00362-x · Cited by 261
A Unified Model of Requirements Elicitation
HICKEY, A. M., & DAVIS, A. M. (2004) · Journal of Management Information Systems · doi:10.1080/07421222.2004.11045786 · Cited by 253
Using an expert panel to validate a requirements process improvement model
Beecham, S., Hall, T., Britton, C., Cottee, M., & Rainer, A. (2005) · Journal of Systems and Software · doi:10.1016/j.jss.2004.06.004 · Cited by 171
Metadata
- Authors
- Hofmann, H. F., & Lehner, F.
- Venue
- IEEE Software
- Published
- 2001-07
- Volume
- 18
- Issue
- 4
- Pages
- 58-66
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W2145960294
- Cited by
- 514
- References
- 10
- FWCI
- 33.05
- 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: Requirements engineering as a success factor in software projects. https://app.cochat.ai/papers/10.1109/ms.2001.936219
- The paper
- Hofmann, H. F., & Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE Software. https://doi.org/10.1109/ms.2001.936219
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.