CoChat
Sign Up
Cited by 912Software Engineering Techniques and PracticesAdvanced Software Engineering MethodologiesSoftware Engineering Research

The DOI matches its Crossref record; 60 of the 63 references it cites were found in a registry or an index.

Toward reference models for requirements traceability

Ramesh, B., Jarke, M.·2001·IEEE Transactions on Software Engineering
DOI 10.1109/32.895989
Open this paper in CoChat — free account

Abstract

Requirements traceability is intended to ensure continued alignment between stakeholder requirements and various outputs of the system development process. To be useful, traces must be organized according to some modeling framework. Indeed, several such frameworks have been proposed, mostly based on theoretical considerations or analysis of other literature. This paper, in contrast, follows an empirical approach. Focus groups and interviews conducted in 26 major software development organizations demonstrate a wide range of traceability practices with distinct low-end and high-end users of traceability. From these observations, reference models comprising the most important kinds of traceability links for various development tasks have been synthesized. The resulting models have been validated in case studies and are incorporated in a number of traceability tools. A detailed case study on the use of the models is presented. Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed. Implications for the design of next-generation traceability methods and tools are discussed and illustrated.

Overview

Integrity signals

Registry

Crossref · 10.1109/32.895989

Cites

60 of 60 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cites

Show all 63 references

Research works printed but not linked: 15

  1. Ramesh, Requirements TraceabilityTheory and Practice, 3, 397
  2. Pohl, Process Centered Requirements Eng
  3. Ramesh, Supporting Systems Development Using Knowledge Captured during Requirements Engineering, 18, 498
  4. Pohl, PRIMETowards ProcessIntegrated Modeling Environments, 8, 343
  5. Palmer, Traceability, 364
  6. Stehle, Requirements Traceability for Real-Time Systems
  7. Wright, Requirements TraceabilityWhat? Why? and How?
  8. Jarke, ConceptBaseA Deductive Object Base for Meta Data Management, 5, 167
  9. Constantopoulos, The Software Information BaseA Server for Reuse, 4, 1
  10. Lee, Design Rationale Capture and Use, 14, 24
  11. Goldman-Segall, Collaborative Virtual Communities Using Learning Constellations: A Multimedia Research Tool
  12. RDD-100: Requirements Driven Design, User Guide
  13. Dynamic Object Oriented Requirements SystemReference Manual
  14. SLATE User Manual
  15. 1992, Cadre/RQT User Manual

Cited by

Sorted by citations

See all 912

Related

Metadata

Authors
Ramesh, B., & Jarke, M.
Affiliations
  • Georgia State University (US)
  • Fraunhofer Institute for Applied Information Technology (DE)
ORCID
Venue
IEEE Transactions on Software Engineering
Publisher
Institute of Electrical and Electronics Engineers (IEEE)
Published
2001
Volume
27
Issue
1
Pages
58-93
ISSN
0098-5589 (ISSN-L)
DOI
10.1109/32.895989
OpenAlex
W2045895677
Cited by
912
References
63
Citations by year
2026: 15 · 2025: 13 · 2024: 14 · 2023: 13 · 2022: 8 · 2021: 22 · 2020: 19 · 2019: 16 · 2018: 28 · 2017: 30 · 2016: 35 · 2015: 38 · 2014: 35 · 2013: 47 · 2012: 69
FWCI
92.83
Type
journal article
Language
en
Open access
closed
Licence
ieeexplore.ieee.org/Xplorehelp/downloads/license-information/IEEE.html (vor)
Locations
  • IEEE Transactions on Software Engineering (publishedVersion)
  • Publikationsdatenbank der Fraunhofer-Gesellschaft (Fraunhofer-Gesellschaft) (submittedVersion)
  • Fraunhofer-Publica (Fraunhofer-Gesellschaft) (submittedVersion)
  • RWTH Publications (RWTH Aachen) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
requirements traceability, reference model, traceability links, software development process, stakeholder needs, traceability tools, requirements engineering

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