AUTOMATED DEVELOPMENT LOG PREPARATION

Coordinator
Jun 17, 2011 at 4:24 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.

SATURDAY: The Command Sequence, _TASK_NO Command, and _UPDATE Command Pages for the Command Sub-Section of the Library Sub-Task has been completed

SUNDAY: The software parts library sub-task requires that the library sub-task file be read twice; the first to evaluate the need to prepare the library based on the various file dates and the second to prepare it. On the first read, the library subtask file is not displayed. If the second read is necessary, the library subtask file will be displayed. As a consequence, it is very difficult to find syntax errors in the library sub-task file.  Changes to the Programmable Software Development Environment are being planned.

MONDAY:  To facilitate finding syntax errors in the library subtask file, a _DISPLAY command will be added.  This will unconditionally cause the file to be displayed during the first read. The Manual is still being updated to reflect the addition of version control.

TUESDAY: The Version Control, _LIBRARY, _MACRO and _APPEND Command Pages for the Command Sub-Section of the Library Sub-Task have been  prepared.  Proper examples still need to be selected.