Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 514

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

Hofmann, H.F., Lehner, F.·2001·IEEE Software

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.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1109/ms.2001.936219

Cites

10 of 10 references verified0 citation errors · 0 not checkable

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.

A few free checks a day · papers already verified open instantly · results are public

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

Show all 10 references

Cited by

See all 514

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.