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.
SUMMARY (Fritz) - emphasizes need for traceability across levels of granularity - traceability generally important in design (not only software) - traceability links can be enriched through rationale sematics (URDAD: requiredBy, requiredService, ...) - include sufficiency and necessity, i.e. are all requirements met and are all design elements necessary/required to realize requirements - identify immediate impact point, calculate potential impact tree, prune impact tree
%0 Journal Article
%1 dick_design_2005
%A Dick, Jeremy
%D 2005
%J Software, IEEE
%K analysis code; design design; development engineering; formal information requirements software source specification; system systems tools; traceability traceability; verification;
%N 6
%P 14--16
%R 10.1109/MS.2005.150
%T Design traceability
%V 22
%X 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.
@article{dick_design_2005,
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.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {Dick, Jeremy},
biburl = {https://www.bibsonomy.org/bibtex/265f75d52e88d5ef5c4b071101092477c/fritzsolms},
doi = {10.1109/MS.2005.150},
interhash = {5a489948849a7e27c616f9dc50c5881b},
intrahash = {65f75d52e88d5ef5c4b071101092477c},
issn = {0740-7459},
journal = {Software, {IEEE}},
keywords = {analysis code; design design; development engineering; formal information requirements software source specification; system systems tools; traceability traceability; verification;},
lccn = {0033},
month = nov,
number = 6,
pages = {14--16},
review = {{SUMMARY} {(Fritz)} - emphasizes need for traceability across levels of granularity - traceability generally important in design (not only software) - traceability links can be enriched through rationale sematics {(URDAD:} {requiredBy}, {requiredService}, ...) - include sufficiency and necessity, i.e. are all requirements met and are all design elements necessary/required to realize requirements - identify immediate impact point, calculate potential impact tree, prune impact tree},
timestamp = {2013-02-28T11:13:46.000+0100},
title = {{Design traceability}},
volume = 22,
year = 2005
}