Published in IEEE Software, Volume 22, Issue 6, November 1, 2005, pages 30-37.
Copyright © 2005 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE. The definitive version is available at http://dx.doi.org/10.1109/MS.2005.156.
NOTE: At the time of publication, the author Alex Dekhtyar was not yet affiliated with Cal Poly.
The software engineering industry undertakes many activities that require generating and using mappings. Companies develop knowledge bases to capture corporate expertise and possibly proprietary information. Software developers build traceability matrices to demonstrate that their designs satisfy the requirements. Proposal managers map customers' statements of work to individual sections of companies' proposals to prove compliance. Systems engineers authoring interface specifications record design rationales as they make relevant decisions. We developed an approach to tracing and mapping that aims to use fully automated information retrieval techniques, and we implemented our approach in a tool called RETRO (requirements tracing on target).