Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
Most systems engineering activities initially start out with early or draft rersion of various Customer or Company specifications written in popular desktop publishing tool formats (e.g. Interleaf, Framemaker & Word). Using the more advanced requirements & traceability management (RTM) tools (which are embedded directly into these desktop publishing systems) information relevant to the project can then be "captured" from these documents into the tool's requirements repository for audit trail, engineering and traceability purposes. Then typically, several months later (after much systems engineering activity, requirements editing/decomposition/focusing, CASE tool modelling & through ltfecycle traceability creation) updated copies of these documents are received. This then severely disrupts the flow of the project as much nugatory manual rework has to be done in the form of change identification, impact analysis and consistency checking bell-veen the 5ystems engineering work carried out so far in the project database and the latest information in the updated documents. This document examines the issues involved in automatic document update processing from a requirements & traceability management tool perspective. The document does not make any major assumptions about the reader's knowledge of any particular requirements management tool, although familiarity with general RTM operational philosophy concepts would be of benefit. For more detailed information on the GEC-Marconi preferred RTM solution, the reader is advised to sample relevant sections from references [l], [2] [3] & [4].