• Journal of the Korea Society of Computer and Information
• /
• v.17 no.5
• /
• pp.115-126
• /
• 2012

It is very important to trace whether all the requirements has been reflected in the developed system. However, most existing researches apply Requirement Traceability Matrix(RTM) to the whole SDLC according to the development methodology. RTM has no practical value because it has not only too many pursuit items but also its tracking method is very complicated and the practical management in developing the information system is not accomplished nearly. Therefore, in this study, we proposed an enhanced RTM which was composed of only necessary items and allow us to manage the applied area effectively from Request for Proposal(RFP) or the proposal stage to SDLC stage then confirmed the effect through six actual applicable cases of information system development project of "K" company.

• Journal of the Korean Society of Systems Engineering
• /
• v.12 no.1
• /
• pp.1-5
• /
• 2016

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.