Archive for November, 2012

Development of Utility Libraries

November 30, 2012

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

CERTIFICATION BLOG: Inorder to certify that a product has been developed in strict compliance with the specified standards and has not been patched, pseudo-random longitudinal parity bits must be included in source code in the form of comments. These comments can be at the end of each line (C, C++, C#), at the beginning of each line (HTML), or at the end of each statement (Visual Basic).  This blog will present the research and development section associated with upgrading the existing output library to facilitate both the generation and the testing of all three forms of product source code.

CERTIFICATION THURSDAY ACTIVITY: I have now completed my Thanksgiving trip and will restart my research / development activities. Questions that will be considered is the certification of the paste oriented document files in which each paragraph is a long single line. It may be desireable to upgrade the Programmable Software Development Environment to make this possible.

Development of Utility Libraries

November 16, 2012

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

CERTIFICATION BLOG: Inorder to certify that a product has been developed in strict compliance with the specified standards and has not been patched, pseudo-random longitudinal parity bits must be included in source code in the form of comments. These comments can be at the end of each line (C, C++, C#), at the beginning of each line (HTML), or at the end of each statement (Visual Basic).  This blog will present the research and development section associated with upgrading the existing output library to facilitate both the generation and the testing of all three forms of product source code.

CERTIFICATION FRIDAY ACTIVITY: I reexamined the program output software parts library and I learned that 1) it is not being used in any current applications and 2) is very obsolete. It was developed over 10 years ago when I was not considering portability and certification. Furthermore, although it has been extensively used, it has not been formally tested. It is now time to perform this development and formal test effort.

CERTIFICATION SATURDAY ACTIVITY: The development process has been started and a significant challenge was discovered. It is important to make the selection to write a file or certify a file as simple and transparent as possible.  It is currently planned to make this decision in the source sub-task file.  If the  subject files are input files, they will be certified. If the subject files are output files, they will be written.

CERTIFICATION THURSDAY ACTIVITY: The development of the basic output / certification library is progressing without incidence. Certification at this level is accomplished on a line by line basis. Instead of writing the line in an output file, it is compared for equality with a line in the input file. An error will be reported if this comparison fails. This library should be ready for test soon after the Thanksgiving holidays.

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.

Development of Utility Libraries

November 9, 2012

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

CERTIFICATION BLOG: Inorder to certify that a product has been developed in strict compliance with the specified standards and has not been patched, pseudo-random longitudinal parity bits must be included in source code in the form of comments. These comments can be at the end of each line (C, C++, C#), at the beginning of each line (HTML), or at the end of each statement (Visual Basic).  This blog will present the research and development section associated with upgrading the existing output library to facilitate both the generation and the testing of all three forms of product source code.

CERTIFICATION TUESDAY ACTIVITY: There are existing libraries for writing source code. One of these libraries writes source code with the parity bit at the end of each line.  The other writes at the beginning. There is no well-developed way of testing the parity at this time. The first step is to define a structure which will facilitate the writing and testing of all three output formats.

CERTIFICATION WEDNESDAY ACTIVITY: It occurred to me last night that in the development of a software source file, there are two checkout / formal testing phases; one to certify the proper preparation of the source file and the other to certify its proper execution.  Arrows and dates will be used to record the status of both phases. As a consequence, it is probably easier to use a separate comment line at the end or beginning of each source statement to report the status of the statement and contain the parity bit.

CERTIFICATION THURSDAY ACTIVITY: There are three basic forms of output file: Programmable Software Development Environment files; source code files, and document text files. The Programmable Software Development Environment files will always have a comment at the end of the line with the parity byte.  The source code files will have a comment line following each statement with the parity byte. The document text file has no comment. In this case certification information can be added to the text by randomly increasing spaces from one to two blanks.

Development of Utility Libraries

November 2, 2012

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

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

SCRIPT MONDAY ACTIVITY: Being able to pass parameters to the script in the _RUN_SCRIPT command is next script library upgrade to be performed. I have now included the capability of insuring that the _BEGIN_RUN_SCRIPT, the _RUN_SCRIPT_ARGUMENT, and the _END_RUN_SCRIPT software parts are used in the proper order.  The next step is to prepare the _RUN_SCRIPT_ARGUMENT software part.

Can Software Be Assembled Not Written?

November 2, 2012

The software part is roughly equivalent to an integrated circuit. Can we assemble a software product in a manner similar to producing a a hardware product?

I believe that it is possible assemble a software product without any intimate knowledge of the product’s source language. Instead of writing the code in a computing language such as C++, the appropriate software parts will be selected from a system of menus.

This blog will be used to document my research and development efforts associated with a menu-driven product assembly capability.

ASSEMBLY THURSDAY ACTIVITY: The best way of creating the Programmable Software Development Environment capability for finding files, adding new directories,  compare file modification dates, and finding paths is to add an software parts instruction for launching a executable. This will enable a command-line script to be processed.