Design Traceability

DOI Bookmark:

http://doi.ieeecomputersociety.org/10.1109/MS.2005.150

November/December 2005 (vol. 22 no. 6) pp. 14-16

	This Article
	PURCHASE ARTICLE: $19 PDF HTML IEEE Xplore Subscribers
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/Endnote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by Jeremy Dick

	ASCII Text	x
	Jeremy Dick, "Design Traceability," IEEE Software, vol. 22, no. 6, pp. 14-16, November/December, 2005.

	BibTex	x
	@article{ 10.1109/MS.2005.150, author = {Jeremy Dick}, title = {Design Traceability}, journal ={IEEE Software}, volume = {22}, number = {6}, issn = {0740-7459}, year = {2005}, pages = {14-16}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2005.150}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - IEEE Software TI - Design Traceability IS - 6 SN - 0740-7459 SP14 EP16 EPD - 14-16 A1 - Jeremy Dick, PY - 2005 KW - traceability KW - requirements KW - design VL - 22 JA - IEEE Software ER -

Jeremy Dick, Telelogic UK

Design traceability--documenting the relationships between layers of design--can help systems engineers better manage requirements changes in their projects. Using traceability, engineers can identify immediate impact; calculate, prune, and elaborate the impact tree; and design and apply change.

Index Terms:

traceability, requirements, design

Citation:

Jeremy Dick, "Design Traceability," IEEE Software, vol. 22, no. 6, pp. 14-16, Nov./Dec. 2005, doi:10.1109/MS.2005.150

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.