Archive for May, 2011

ERROR-2011-05-28

May 28, 2011

FRIDAY: After making a required update of my UBUNTU Linux Operating System, I encountered the following system error in the recompiled Programmable Software Development Environment:

PCG ERROR: devproj — 306
PCG ERROR: mainprj — 1300
PCG ERROR: explrpde — 187

AUTOMATED DEVELOPMENT LOG PREPARATION

May 27, 2011

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.

MONDAY:  The EXPERIMENTAL VERSION page for the version control sub-section of the library sub-task section has been prepared.

TUESDAY: The ALPHA VERSION page for the version control sub-section of the library sub-task section has been prepared.

AUTOMATED DEVELOPMENT LOG PREPARATION

May 20, 2011

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 OVERVIEW page for the version control sub-section of the library sub-task section has been prepared.

SATURDAY: The COMMENT RULES page for the version control sub-section of the library sub-task section has been prepared.

TUESDAY: The DEVELOPMENT PROCESS page for the version control sub-section of the library sub-task section has been prepared.

AUTOMATED DEVELOPMENT LOG PREPARATION

May 13, 2011

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: Preparations were made for the LIBRARY Sub-Task File section of the manual. This is the last section that must be updated before the latest version of the Programmable Software Development Environment can be published. These preparations included the LIBRARY SUB-TASK FILE Table of Contents.

THURSDAY: The OVERVIEW page for the library sub-task section has been prepared. Also, preparations  were made for the version control sub-section of the library sub-task section.  These preparations included the associated table of contents.

AUTOMATED DEVELOPMENT LOG PREPARATION

May 6, 2011

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: Preparations were made to create the _LIBRARY_PROJECT and _SOURCE_PROJECT pages from a single point source. Each of previous sections each had one post office containing the special phrases needed for the section.  The development section will need three post offices; one for the section, one for the _LIBRARY_PROJECT page, and one for _SOURCE_PROJECT page.

MONDAY:  The _LIBRARY_PROJECT and _SOURCE_PROJECT command pages for the development task section have been updated using a single point source.

TUESDAY: The _MAKE command page for the development task section has been updated using a single point source