The CMS toolset comprises of 5 sub-modules that may be purchased separately and added-on to the core system at a latter time. These modules are as follows:

Database Alteration Request (DBAR), used to manage changes to a database related development. This will include table changes, table attributes, triggers, stored procedures, and code tables.

Program Design Alteration Request (PDAR), used to manage changes to the program design and will include internal interfaces, interfaces to other executable units under the control of the development team, as well as interfaces to external sources.

Defect Identification Report (DIR), used to manage defects found in a software development based project.

Issue Tracking Register (ITR), used to manage the resolution and tracking of issues/risks associated with a project.

System Alteration Request (SAR), used to manage and control changes to the baseline requirements currently being developed by a software development team.

Risk Management Register (RMR), used to identify risk and risk impacts on projects and provides a mechanism to assign risk mitigation strategies and track them.

For each module purchased, any number of instances may be created within the CMS system. For example, management/tracking of software defects within development and production separately will require two instances of the DIR module to be created. Creating a new DIR, for example, is as simple as pressing a button, see below:

and then configuring the item to suit your particular requirements. With the example above, the DIR configuration screens are as follows:

The CMS system also offers the capability for remote users, where they can create items (e.g. DIR) and submit via e-mail. Therefore, access to the installed system is not necessary.

For each module, the analysis tools are specific for that module and aids metric based analysis. For example, one of the analysis displays for baseline requirement changes managed via the SAR module shows variation costs and schedule impacts, illustrated below:

Some other data analysis formats, such as analysing the detection and rectification rates of defects found in a version of the system, are illustrated below (DIR samples):

Also, available is data relating to the time taken to rectify and verify the correction of defects within the system, as illustrated below:

Other analysis information is based on functional categorisation, as illustrated below:

All the above sub-modules have a set of batch utilities to support data administration, such as bulk assignment and status setting. See below for an example:

The CMS system provides a toolset for migrating existing items within the CMS system. For example, a number of DDRs may need to be migrated to SARs. Below is a sample of the migration display and illustrates the data mapping capabilities:

Also, since the CMS system is based on Excel® all the standard import/export features are available (e.g. save as HTML, save as word, copy/paste to any other supported application).

CMS items may also be created by importing data from an existing Excel® spreadsheet. This data may have been created manually or exported from another system. The technique is similar to the migration where data fields are mapped to CMS item fields. See below for an illustration of the importation tool:

You may Send an E-mail Request for the full set of Change Management & Requirements Tracing system documents to be sent back to you via e-mail or you may download a copy of this page directly from this link CMSTechReport.zip.

Adobe Acrobat (PDF) files require Adobe Acrobat Reader. Acrobat Reader can be obtained from Adobe.

© Copyright 1999-2004 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®, Microsoft® Office 97, Microsoft® Office 2000/XP, Excel®, Word®, and Access® are trademarks of Microsoft Corporation, USA.