Posts Tagged ‘Portability’

Development of Basic Text Write/Certification Utility Libraries

August 16, 2013

The effort associated with the development, upgrading and testing the  basic output software parts library will be documented here. If there is anyone who desires to assist me in this development process, please contact me by e-mail.

The affected software parts and their functional description are listed below. The purpose of this library is to be able to write or certify one or more text files. These parts are similar to object oriented subroutines. The parts that have been completely tested are noted.

_BASIC_OUT_CONSTRUCT: Initializes the library for a write or certification function.

_BASIC_OUT_DESTROY:   Completes the operation by eliminating the specific setup. COMPLETELY TESTED.

_BASIC_OUT_BEGIN_SETUP: Begins a setup procedure by which the files to be processed are specified. COMPLETELY TESTED.

_BASIC_OUT_ADD_FILE: Add a file to the process list.

_BASIC_OUT_END_SETUP: Completes the setup procedure. COMPLETELY TESTED.

_BASIC_OUT_GET_WRITE_NO: Utility: Search the output file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_GET_READ_NO: Utility: Search the input file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_ALIAS_FORMAT: Utility: Check for duplicate file specification.

_BASIC_OUT_FILES_BEGIN: Begin the processing of files. COMPLETELY TESTED.

_BASIC_OUT_FILES_END: Ends the processing of files. COMPLETELY TESTED.

_BASIC_OUT_TEXT: Processes a text segment in a specified file.

_BASIC_OUT_CHAR: Processes a special character in a specified file.

_BASIC_OUT_END_LINE: Processes a CRLF in a specified file.

_BASIC_OUT_READ_SEGMENT: Utility — Reads a text segment or special character.

_BASIC_OUT_BASIC_READ: Utility — Basic Read for text segment, special character, or CRLF.

_BASIC_OUT_FILE_LINE_END: Utility — Find the next CRLF in the file.

_BASIC_OUT_ERROR_INITIAL: Utility — Initial Error Management System file.

_BASIC_OUT_ERROR_RECORD: Utility — Record Error, COMPLETELY TESTED.

_BASIC_OUT_ERROR_END_FILE: Utility — Record Unexpected End of File. COMPLETELY TESTED.

_BASIC_OUT_ERROR_READ_OK: Utility — Permission to read a line. COMPLETELY TESTED.

_BASIC_OUT_GET_NO_ERRORS: Return the number of error entries.

_BASIC_OUT_GET_ERROR_TYPE: Return the error type associated  with a error number.

_BASIC_OUT_GET_ERROR_LINE_NO: Return the line number associated with a error number.

_BASIC_OUT_GET_ERROR_PREP_NO: Return the preparation number associated with a error number.

_BASIC_OUT_TEST_NO_ERRORS: Verify the number of error entries.

_BASIC_OUT_TEST_ERROR_TYPE: Verify the error type associated with a error number.

_BASIC_OUT_TEST_ERROR_LINE_NO: Verify the line number associated with a error number.

_BASIC_OUT_TEST_ERROR_PREP_NO: Verify the preparation number associated with a error number.

_BASIC_OUT_WRITE_REPORT: UTILITY — Record a certification error. COMPLETELY TESTED.

_BASIC_OUT_VERIFY_ALIAS: UTILITY — Verify Postal Alias .

THURSDAY: 2013/08/15

STATUS: The end-of-file testing has been successfully completed. The testing of its multiple error processing capability has been successfully started.

DETAIL: The software parts library is designed to be able to have up to a user specified n-consecutive lines with errors before terminating execution. The basic technique appears to be functional

RESULTS: This library has been sufficiently tested to render it usable in various applications.

NEXT TASK: The testing of its multiple error processing capability will continue.

Development of Utility Libraries

January 11, 2013

The activity associated with development of utility software parts libraries will be presented here.

CERTIFICATION THURSDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library check out / formal test continues. The functional check-out of certification error report handling software parts continues. There are four kinds of certification errors (I have added one more): 1) The text read from the file is different than the required text, 2) an illegal blank line, 3) a missing blank line and 3) an illegal end of file. The detection and reporting of all four certification errors types have been successfully tested. There are still some usage errors that need to be tested; however, I believe that this software parts library can be experimentally used.  These additional tests will be run on a lower priority basis.

Development of Utility Libraries

December 28, 2012

The activity associated with development of utility software parts libraries will be presented here.

CERTIFICATION MONDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library check out / formal test continues. The functional check-out of report handling software parts continues.  Not all of the certification errors have been simulated.

CERTIFICATION THURSDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library check out / formal test continues. The functional check-out of certification error report handling software parts continues.  It is a significant challenge in that currently a certification error does not terminate the execution of the certification test.  More modifications are expected.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

December 24, 2012

HAS A MAJOR ERROR FREE SOFTWARE METHODOLOGY BEEN DEVELOPED?

The principles of simple-precedence produced one of the best compilers that I have ever used.

Can the principles of simple-precedence be used in the development of other applications?

Would you believe it if I told you that simple-precedence has been used in a lot of different applications.

In 1973, IBM introduced the principles of structured programing.

Strict Structured Programming satisfies the requirements of simple-precedence.

Strict Structured Programming is a excellent means of defining an error-free process.

Unfortunately, the management of data is different than the management of a process.

WHATIFWE developed a simple-precedence means of managing data? Can we do it?

Open Source Software Development Tool: Upgrade Progress

December 21, 2012

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.

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: The new utility routine for precfile.cpp for completing a string of characters read from a “paste-in” file has been prepared. The next step will be to continue the required integration efforts.

Can Programming Be Strictly Portable Relative To Language?

November 9, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

MONDAY: Having upgraded both the script and certification software parts library, I reexamined the software parts associated with the common includes software parts library to determine the need of script software parts library. Specifically in the preparation of a source or header file, all of the system includes must written first, the data includes must be written second, and the class includes must be written last. The script is not needed to accomplish this task. The next step is to complete the formal testing of the common includes library.

TUESDAY: The formal testing of the common includes software parts library has been completed. The certification process will only be complete when we are able to perform a certification test on the generated source product. To meet this goal, the software parts library associated with the generation of output source files must be examined, upgraded as necessary and formally tested.  This will be the next task and the associated research / development activities will be reported in the utility blog.

Can Programming Be Strictly Portable Relative To Language?

August 10, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

FRIDAY: The script library has been sufficiently tested that the testing of the second level operation of the common include library can continue.

TUESDAY: The testing of the second level operation of the common include library has been completed. The tests include the copying of the system includes and the definition of class and data includes. Testing the third level of operation is next.

Can Programming Be Strictly Portable Relative To Language?

July 13, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

SATURDAY: The modified common include library has been prepared. Preparing its Monte-Carlo checkout/testing process is next.

TUESDAY: The Monte-Carlo checkout/testing process has been prepared. Checkout of the first level operation of the common include library is next.

THURSDAY: First level operation of the common include library has been checked out. Checkout of the second level operation of the common include library is next.

Can Programming Be Strictly Portable Relative To Language?

July 7, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

SATURDAY: The modified common include library has been prepared. Preparing its Monte-Carlo checkout/testing process is next.

Can Programming Be Strictly Portable Relative To Language?

May 18, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

THURSDAY: The development of a certification library has begun.  The certification methodology for post office communication involves implementing a certified copy of a sequence of macro-calls in the user task.  Cryptographic methods will be used to certify the communication process.