AUTOMATED DEVELOPMENT LOG PREPARATION

Coordinator
Feb 4, 2011 at 5:09 PM

Keeping an accurate log of the development process is becoming increasingly difficult and time consuming. Modification of Programmable Software Development Environment to automate this record keeping process has begun and for the present will be top-priority.

Each of the software parts commands can be terminated by a comment.  This comment can be used to provide a checkout breakpoint, ";<----".  It can also be used to associate a completion date with the command.

The process associated with the development of standard software parts will consist of the following four versions: experimental, alpha version, beta version, and released version.

The release state is where every one of the commands has a completion date and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The beta state is every one of the commands has a completion date or breakpoint and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The alpha state is every one of the commands has a completion date or breakpoint.

The experimental state has no constraints relative to the commands relative to a completion date or breakpoint.

A Text file report will be prepared each time a software parts library is modified. This report will contain the total number of commands, the number of commands with checkout breakpoints, and the number of commands with today's date in each of the associated software parts files.

The Version Control Class has been prepared.  A class for preparing the report will be prepared next.