Design Traceability
Abstract
Traceability is about documenting the relationships between layers of information, for instance, between system requirements and software design. Many software development tools manage design relationships, for instance, between modeling elements (such as classes) and source code, or between tasks and source code files. Whatever development scale we engage in, we systematically apply information traceability. It's a vehicle for thinking about the way the software meets its requirements; it captures design rationale to help others understand and review; and it gives us far greater confidence in managing future changes.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Lecture video is better than textbook readings to prepare students for classroom activities.
“lecture video is found to be better than textbook readings to prepare students for classroom activities (4).”
From Applying learning theories and instructional design models for effective instruction (2016) · cites this paper as [4]
The citation lists haven’t been fetched yet
References 1 · Cited by 46
- Authors
- Dick, J.
- Affiliations
- Telefónica (United Kingdom) (GB)
- Corresponding author
- Dick, J.
- Venue
- IEEE Software
- Published
- 2005-11
- Volume
- 22
- Issue
- 6
- Pages
- 14-16
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W2295859017
- Cited by
- 46
- References
- 1
- Citations by year
- 2026: 2 · 2025: 1 · 2021: 1 · 2020: 1 · 2017: 2 · 2016: 2 · 2015: 1 · 2014: 2 · 2013: 2 · 2012: 1
- FWCI
- 17.28
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- IEEE Software (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
- Keywords
- design traceability, data traceability, design rationale, software change management, software requirements
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
