The DOI matches its Crossref record; 34 of the 34 references it cites were found in a registry or an index.
Event-based traceability for managing evolutionary change
Abstract
Although the benefits of requirements traceability are widely recognized, the actual practice of maintaining a traceability scheme is not always entirely successful. The traceability infrastructure underlying a software system tends to erode over its lifetime, as time-pressured practitioners fail to consistently maintain links and update impacted artifacts each time a change occurs, even with the support of automated systems. This paper proposes a new method of traceability based upon event-notification and is applicable even in a heterogeneous and globally distributed development environment. Traceable artifacts are no longer tightly coupled but are linked through an event service, which creates an environment in which change is handled more efficiently, and artifacts and their related links are maintained in a restorable state. The method also supports enhanced project management for the process of updating and maintaining the system artifacts.
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
(1994) · Cited by 21,711
Software engineering: A practitioner's approach
(1983) · Advances in Engineering Software (1978) · doi:10.1016/0141-1195(83)90118-3 · Cited by 8,234
On the criteria to be used in decomposing systems into modules
Parnas, D. L. (1972) · Communications of the ACM · doi:10.1145/361598.361623 · Cited by 4,704
The Rational Unified Process: An Introduction
Kruchten, P. B. (1998) · Cited by 2,592
An analysis of the requirements traceability problem
Gotel, O. C. Z., & Finkelstein, C. W. (2002) · Proceedings of IEEE International Conference on Requirements Engineering · doi:10.1109/icre.1994.292398 · Cited by 1,246
Program development by stepwise refinement
Wirth, N. (1971) · Communications of the ACM · doi:10.1145/362575.362577 · Cited by 960
Toward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912
Questions, Options, and Criteria: Elements of Design Space Analysis
MacLean, A., Young, R., Bellotti, V., & Moran, T. (1991) · Human-Computer Interaction · doi:10.1207/s15327051hci0603&4_2 · Cited by 794
The tree-to-tree editing problem
Selkow, S. M. (1977) · Information Processing Letters · doi:10.1016/0020-0190(77)90064-3 · Cited by 428
The Rational Unified Process: An Introduction, Second Edition
Kruchten, P. B. (2000) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 410
Cited by
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
A Traceability Framework to Enable Circularity in the Built Environment
Davari, S., Jaberi, M., Yousfi, A., & Poirier, E. (2023) · Sustainability · doi:10.3390/su15108278 · Cited by 32
Metadata
- Authors
- Cleland-Huang, J., Chang, C. K., & Christensen, M.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2003-09
- Volume
- 29
- Issue
- 9
- Pages
- 796-810
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2142809450
- Cited by
- 288
- References
- 34
- FWCI
- 25.56
- 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: Event-based traceability for managing evolutionary change. https://app.cochat.ai/papers/10.1109/tse.2003.1232285
- The paper
- Cleland-Huang, J., Chang, C. K., & Christensen, M. (2003). Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2003.1232285
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.