The DOI matches its Crossref record.
Adapting traceability environments to project-specific needs
Open accessAbstract
This article focuses on adapting traceability environments to project-specific needs. Requirements traceability is defined as the ability to describe and follow the life of a requirement, in both a forward and backward direction. While present traceability environments do offer some flexibility in the definition of trace data types, they do not lend themselves easily to a situated approach to defining trace capture and usage strategies. To empower the project-specific definition of data types, a traceability environment must provide capabilities to define new data types and to adjust predefined types according to project-specific needs. Moreover, it should systematically support the project manager in considering recorded experiences and the actual needs. Establishing project-specific traceability definitions does not guarantee that traces are correctly captured and used. To ensure definition-conform trace recording and usage, definitions must be communicated to stakeholders performing the process and must be applied in the corresponding situations throughout the project. INSET: Examples of Project-Specific Trace Capture and Usage.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Cited by
Toward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912
Lucia, A. D., Fasano, F., Oliveto, R., & Tortora, G. (2007) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/1276933.1276934 · Cited by 354
Software traceability with topic modeling
Asuncion, H. U., Asuncion, A. U., & Taylor, R. N. (2010) · Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1 · doi:10.1145/1806799.1806817 · Cited by 321
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
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
Metadata
- Authors
- Dömges, R., & Pohl, K.
- Venue
- Communications of the ACM
- Published
- 1998-12
- Volume
- 41
- Issue
- 12
- Pages
- 54-62
- ISSN
- 0001-0782 (ISSN-L)
- 1557-7317
- OpenAlex
- W2026032320
- Cited by
- 182
- References
- 0
- FWCI
- 20.68
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Adapting traceability environments to project-specific needs. https://app.cochat.ai/papers/10.1145/290133.290149
- The paper
- Dömges, R., & Pohl, K. (1998). Adapting traceability environments to project-specific needs. Communications of the ACM. https://doi.org/10.1145/290133.290149
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.