|
Technical Overview (Requirement Tracing System)
The RTS toolset comprises of 4 sub-modules that may be purchased separately and added-on to the core system at a latter time. These modules are as follows:
 Requirement creation and specification, known as the Functional Specification,
 Requirements fulfillment, covering the design and coding of the individual requirements, known as the Program Design Specification,
 The system acceptance testing of the requirements , known as the Test Specification, and
 The requirement-tracing database providing the analysis of the requirements defined for a system.
The RTS sub-modules are based on a combination of Excel®, Word®, and Access®.
RTS System Components
The relationships between various modules are illustrated below:
Functional Specification Module
This module provides a methodology and toolset to suit the development of system requirements, which can easily adapt to your existing methodologies. The methodology allows for each specific requirement to be identified and tracked for change and completion. Within the Functional Specification module, the following is a summary of the tool available:
 Inserting a requirement trace point into the document,
 Insert a New Functional Category. Note, each set of requirements is collated into functional categories.
 Make/Start and End a requirement list. Requirements can be traced to a sub-list level (i.e. requirement SEC2.1/4a and SEC2.1/4b). See below for a sample requirement list:
 Insert a Note Marker, designated by the ` &' symbol indicates that this is a configuration or implementation note offering guidance to the document's audience
 Requirement Configuration, allows setting the parameters of the requirement identification, see Dialog below for an example:
The labeling convention is flexible to suit the individual project's requirements. An example of a labeling convention can be based on specification section numbers, as illustrated above, or on specification numbers, such as R2045187
 Requirement tracing builder prepares the import/export files for other modules of the RTS.
This sub-module is based on Word® and Excel®.
Program Design Specification Module
Similar functionality as the functional specification but is oriented towards system design specification. Requirements are tracked against code/design components and mapped back into the functional requirement via the tracing sub-module.
Again, the toolset can be configured to suit your particular methodology and work practices.
Test Specification Module
Similar to the functional specification, but is oriented towards system testing. Requirements are tracked against test cases and mapped back into the functional requirement.
Tracing Database
The requirements tracing database supports the 3 views of the requirement data matching the 3 sub-modules identified above. Examples of these views are illustrated below:
Requirements View
Code Module View
Test Specification View
In addition to the views above, various reports are available highlighting:
 Requirement mismatches, where a requirement may not be mapped to a design module or test case. Therefore, some required functionality might not be coded or tested.
 Impact analysis, where isolating the requirements that require modification can identify the affected code modules and test cases.
 Completion status, where as code modules and test cases are completed, the proportioned requirements are identified as coded and tested respectively.
The tracing sub-module supports data exporting and importing to facilitate upgrades to the RTS system.
The tracing facility also supports any user generates reports and queries on the requirement data supported via the standard Access® report and query generator.
This module is primarily based on Access® with data import/export function supported by Excel®.
You may download the full set of the Change Management & Requirements Tracing system documents directly from this link CMSTechReport.zip.
Adobe Acrobat (PDF) files require Adobe Acrobat Reader. Acrobat Reader can be obtained from Adobe. 
© Copyright 1999-2010 by Bandwood Pty Ltd. All rights reserved. This document contains information proprietary to Bandwood Pty Ltd. No part of this document may be reproduced in any form by any means without permission in writing from Bandwood Pty Ltd (
).
Win95/98®, NT4®, Win2000®, WinXP®, Win Vista®, Win 7®, Microsoft® Office 97, Microsoft® Office 2000/XP/2003, Excel®, Word®, and Access® are trademarks of Microsoft Corporation, USA.
|