Configuration Management Notes

6/23/02 ML

This document lists file locations and deployment practices for the RedX project.  It should be considered a supplement to the FRED Configuration Management Plan.

Index:  Dev Procedures, Defect Tracking, Metrics, Source Code Location, Versioning  

Source Code Location

Source code for the FRED project will be stored under the share \\dogbert\tabletpc\src in the following locations:

type location JBuilder project name
Enterprise Java Beans EJB\RedXBuilderAppSvr\ RedX.jpx
Java Server Pages, beans and HTML ReleaseN RedXReleaseN.jpx

Source Code Versioning

$Revision $   and   $History$  keywords will be contained in each file header.  See additional MS VSS keywords.

Development Notes / Procedures

  1. Individual development will be done on COPIES of the above projects and tested by deploying to individual  J2EE application servers.
  2. When functions/features are complete, the development manager will integrate changes into the master copy, then deploy on the "production" J2EE server, MSEPC1.
  3. The development manager will check the project into MS VSS and create a baseline report that lists the versions of all source files in the release..

Defect Tracking

Rational Clearquest will be used to track defects throughout the lifecycle, including development defects.  See Installation Instructions.

Metrics

Metrics will be collected each Sunday night in the Automated Metrics spreadsheet, which will count lines of code for each Java and J2EE program.  Each week, the total number of  DEV defects will be input to this spreadsheet (as taken from Clearquest) so that defects/LOC can be calculated.