Posts Tagged ‘Record Keeping’

Computer Failure Recovery Status

May 24, 2013

My attempts to find a low cost (free), open source task/scheduling software that was portable between Windows and Linux was unsuccessful. I can get low cost software for the Windows machine; and I may be able to find some usable Linux software; but as far as I can tell, there was nothing available for both machines.  I am currently using TomBoy Notes on my Linux machine.  This program does produce HTML files that will be readable on the Windows machine.  I am not sure how useful it is going to be.  I am probably going to have to develop a program with my programmable software development tools.

The accounting recovery activity is going forward smoothly.  The replacement of QuickBooks by OpenOffice appears to be practical.

 

Advertisements

Machine Failure Recovery Progress Report

May 22, 2013

I plan to start preparing the Open Office  Spread Sheet Template files today.  I want to get back on air as soon as possible from an accounting point of view.  The check book template will be prepared first.

 

AUTOMATED DEVELOPMENT LOG PREPARATION

June 25, 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 development of the revised version of the Programmable Software Development Environment is now complete and can be downloaded from the web-site.  The development process and associated files are upward compatible. Version Control and Log Generation is an added capability.

AUTOMATED DEVELOPMENT LOG PREPARATION

June 24, 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:  Examples have been tentatively prepared.  The remaining pages of the Library Sub-Task have been prepared. A proof-examination of the pages needs will be performed next.

TUESDAY: A Format error in the header of the Manual was discovered. Specifically, multiple colons followed the Titles in some of the Header Lines. The software parts associated with the generation of the header has been corrected

THURSDAY: The proof-examination of the manual revealed errors that were corrected. A second proof-examination will be performed next.

AUTOMATED DEVELOPMENT LOG PREPARATION

June 17, 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: 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.

AUTOMATED DEVELOPMENT LOG PREPARATION

June 3, 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: 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

SATURDAY: The cause of the error has been identified. The required changes will be implemented in both the Windows and Linux versions.  The Windows version will be updated first due to the better debugging capabilities of Visual Studio.net

SUNDAY: The Manual Pages for the Library Version Control Sub-Section of the Library Sub-Task Section have been completed. The Command Sub-section is next.

MONDAY:  The required changes to the Windows version of the updated Programmable Software Development Environment have been successfully implemented.  The changes to the Linux version will now be implemented.

TUESDAY: The required changes to the Linux version of the updated Programmable Software Development Environment have been successfully implemented.

THURSDAY: The Table of Contents page for the Command Sub-Section of the Library Sub-Task has been completed

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

AUTOMATED DEVELOPMENT LOG PREPARATION

April 29, 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 File Update command page for the Development Task File has been prepared using the Single Point Source prepared for the Project File command.

Saturday: The _DRIVE_PATH command page for the Development Task File has been prepared using the Single Point Source prepared for the Project File command.