Posts Tagged ‘Automated Manual Preparation’

Open Source Software Development Tool: Upgrade Progress

May 25, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

FRIDAY 2014/05/24

STATUS: The manual description of the _ERROR command has been
successfully modified.

NEXT TASK: The manual description of the ERROR RESOURCE needs to be
modified.

 

Open Source Software Development Tool: Upgrade Progress

February 14, 2014

The overall purpose of the current Programmable Software Development Environment upgrade process is to certify that a product generated is certifiably releasable.

Major improvement have been made from the 1) Implementation of the experimental, alpha, beta, and release versions of a software parts library and 2) the ability to detect whether the product text files have modified manually (patched).

To certify a software parts library, every command defining this library must be executed. This includes all error detection and reporting statements.  These error statements not only include those associated with the user but also those that detect and report programming and Programmable Software Development Environment errors.

Ideally, those _ERROR statements that report programming and Programmable Software Development Environment errors will never be executed. Therefore, they currently can not be included in the certification test sequence. The challenge is to provide a set of commands which will be executed during a test sequence and report a specified programming or Programmable Software Development Environment failure should it occur.

The following two commands need to be developed: 1) _CONTINUE_IF which will error out if the preceeding test condition is false and 2) _CONTINUE_IF_NOT which will error out if the preceeding test condition is true. These statements replace the currently used _JUMP_IF and _JUMP_IF_NOT statements.

THURSDAY: 2013/02/13

STATUS: I have modified the Program Control section of the manual to include the _CONTINUE_IF and _CONTINUE_IF_NOT  commands.

DETAIL: The other commands which were documented using Microsoft Front Page have not been updated.

NEXT TASK: The new version will next be prepared for publication,

Open Source Software Development Tool: Upgrade Progress

December 26, 2013

It is planned to upgrade the Programmable Software Development Environment to include the capability of reading the paste-in text files where the each paragraph is one very long line.  You may need to download the latest version of the Programmable Software Development Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the capability of reading a standard ASCII text file where the TAB character is replaced with a suitable number of blanks. Each line of the text file cannot be longer than 256 characters. On the other hand, the Programmable Software Development Environment has the capability of writing a paste-in text file where each paragraph is one very long line. This capability includes the ability to include special characters such the TAB.

The ability to read the paste-in text file is needed to certify that the file has not been changed, was developed using the agree-upon standard libraries, or has not been illegally copied.

THURSDAY: 2013/12/26

STATUS: I have completed the re-documentation process of the INPUT FILES software parts commands.

NEXT TASK: The next step will be to make a final proof of the updated manual pages, Once this is done, the updated Programmable Software Development Environment will be prepared for uploading to my website and my CodePlex account.

Open Source Software Development Tool: Upgrade Progress

December 25, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

TUESDAY: 2013/12/24

STATUS: The manual page associated with the _TEXT_BASE_NAME (not the
_TEXT_PATH as originally planned) has been updated.

NEXT TASK: The next task will be to update the _TEXT_PATH manual page.
There are two more pages to update.

Open Source Software Development Tool: Upgrade Progress

December 17, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

MONDAY: 2013/12/16

STATUS: I have re-documented the _TEXT_NAME manual page.

NEXT TASK: The next task will be to update the _TEXT_PATH manual page.
There are three more pages to update.

Open Source Software Development Tool: Upgrade Progress

August 26, 2013

MONDAY: 2013/08/26

STATUS: The manual pages associated with the _SOURCE_NAME and
_READ_TEXT of the INPUT_FILE Command Sub-Section have been updated the
new, non Front Page format.

NEXT TASK: The next task will be to update the _STATE_READ_TEXT manual
page.

MANUAL MAINTENANCE

August 16, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

SATURDAY: The Manual Update has been completed.  Please track the completion of this Programmable Software Development Environment update project in the “Open Source Software Development Tool: Upgrade Progress”. Section.

MANUAL MAINTENANCE

August 10, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

FRIDAY: The “_REPORT_FILE” has been successfully prepared. The development of the new “Report Generation Commands” page is next.

MONDAY: The development of the new “Report Generation Commands” page has been successfully completed. I believe that the current version of the manual is adequate for the new version of the Programmable Software Development Environment. The common line screen reporting capabilities are important for our communication. The next step will be to proof the manual. When completed, this version of the Programmable Software Development Environment can be prepared for publication

TUESDAY: My first examination of the Manual revealed link errors that have been corrected. I also observed some deficiencies in the documentation of the Project File relative to the Command-Line Report Generation File. My next task will be to re-examine and correct these deficiencies.

THURSDAY: The observed deficiencies in the documentation of the Project File relative to the Command-Line Report Generation File have been fixed. A second overall review of the manual needs to be made and then this version of the Programmable Software Development Environment can be packaged for upload. It is also important at this time to review the web-site for needed upgrade.

MANUAL MAINTENANCE

July 27, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

THURSDAY: The development of the “_REPORT_FILE” Command” page has been started. The script library error being corrected was encountered. The Manual Update may needed to be put on hold until these script library corrections have been made.

MANUAL MAINTENANCE

July 20, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

SATURDAY: The “_SET_TAB Command” has been successfully moved to a dedicated sub-directory.  The development of the new “_REPORT_FILE” command page is next.