AUTOMATED DEVELOPMENT LOG PREPARATION

Coordinator
Apr 22, 2011 at 4:50 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.

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 software part defined by the software parts files contained in the library development project.

The checkout of the revised Programmable Software Development Environment is complete. Status reports have been successfully generated. All versions of the software parts library have been successfully generated.

The revised Programmable Software Development Environment is currently being aggressively tested by using it to revise its manual. When this revision is complete and any errors encountered are fixed, the Programmable Software Development Environment will be published. One minor problems has been encountered and fixed.

The Manual Effort requires an update in the Project File, Development Task File, and the Library Sub-Task File sections.

Friday: The DISPLAY command page for the Development Task File has been prepared using the Single Point Source prepared for the Project File command. An error that prevents a macro call with nine arguments was discovered.  This error will not prevent the continued update of the manual.

Saturday:   The error discovered yesterday was corrected. Calling a macro with nine arguments now works correctly.

Tuesday: The _TASK_NO command page for the Development Task File has been prepared. Due to the fact that this command is used in both the source and library sub-tasks, a Single Point Source was used.

Thursday: The _DEBUG command page for the Development Task File has been prepared. Due to the fact that this command is also a software parts command, a Single Point Source was prepared.