JOURNAL BROWSE
Search
Advanced SearchSearch Tips
A Suggestion on a Better Template for Requirements Traceability Matrix of a Requirements Specification
facebook(new window)  Pirnt(new window) E-mail(new window) Excel Download
 Title & Authors
A Suggestion on a Better Template for Requirements Traceability Matrix of a Requirements Specification
Kim, DaeSeung;
  PDF(new window)
 Abstract
Most of systems engineers make a traceability matrix and attach it to their technical documents as a result of systems engineering activities. I have been working in the field of systems engineering for many years and have been watching traceability matrices created by systems engineers or developers from various companies. I have been thinking that some of them are not suitable in terms of purposes of traceability matrix. In this paper, I would like to suggest a right template for the traceability matrix in conformance to traceability purposes. The key is that traceability matrix should be created from higher level of requirements to current level of requirements.
 Keywords
Requirements traceability matrix;Requirements Specification;Bi-directional traceability;Traceability matrix template;
 Language
Korean
 Cited by
 References
1.
DaeSeung Kim, Two Principles to Secure Practical Bi-directional Traceability, The Korea Society of Systems Engineering, 2014.

2.
Technical Document Templates as Software Development Artifacts, Defense Acquisition Program Administration, 2013.

3.
Leffingwell & Widrig, "Managing Software Requirements," Addison Wesley, 1999.

4.
CMMI Institute, "Introduction to CMMI for Development", 2015.

5.
Klasus Pohl, Chris Rupp, "Requirements Engineering Fundamentals", Rockynook, 2011.

6.
INCOSE Systems Engineering Handbook, Fourth Edition, 2015.

7.
Charles Wasson, "System Engineering Analysis, Design, and Development", Second Edition, Wiley, 2016.