Posts Tagged ‘manual’

Open Source Software Development Tool: Upgrade Progress

February 11, 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.

MONDAY: 2014/02/10

STATUS: I have examined the Program Control section of the manual and have found that the _CONTINUE_IF and _CONTINUE_IF_NOT  commands can be added to this section without modifying the existing command presentation files (The table of contents will, of course, need to be modified).

DETAIL: The existing command presentation files were written by Microsoft Front Page and need to be replaced.  This can be done at a later time.

NEXT TASK: The next task will be to prepared the sub-directories, files, and modification to the table of contents associated with the _CONTINUE_IF command.

Advertisements

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.