Archive for October, 2012

Development of Utility Libraries

October 26, 2012

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

In order to use the certification software parts library in the development of the class base software development process, it is necessary to include a script call capability in this library.  This effort will be reported in this sub-section of the utility blog.

CERTIFICATION SATURDAY ACTIVITY: The two software parts needed to add the script calling capability to the certification software parts library have been prepared. The next task will be to checkout / formal-test this additional capability.

CERTIFICATION TUESDAY ACTIVITY: The checkout / formal-test process has been started and the basic calling process has been successfully checked. The calling process that enables the client to become a subsequent service function.

Can Software Be Assembled Not Written?

October 26, 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 MONDAY ACTIVITY: Inorder to perform the design activity exclusively from a system of menus and dialog boxes, additional system related commands must be added to Programmable Software Development Environment. For example, commands for finding files, adding new directories,  compare file modification dates, and finding paths must be added. The next task will be to identify these commands.

Can Programming Be Strictly Portable Relative To Language?

October 19, 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 certification / common name issues of the includes software parts library will be reexamined and the development process re-planned.

MONDAY: A re-examination of the common class base software parts revealed the basic challenge. The act of referring to a class another class (sub-class) involves a number of sets of commands; i.e., the sub-class includes, sub-class typedefs, and sub-class data structure. The basic problem is that all of the include instructions must be executed first, then all of the typedef instructions next, and so forth. A script call instruction can satisfy this requirement. The next task will be to implement and test an appropriate certification command. This effort will be reported in the utility blog.

Development of Utility Libraries

October 19, 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.

My apologies for inadequacies in my blogging efforts.  I have had a non-related significant distraction from my research/development activities. These distractions have not as yet been completed.  Hopefully in a few weeks…

SCRIPT FRIDAY ACTIVITY: Being able to pass parameters to the script in the _RUN_SCRIPT command is next script library upgrade to be performed. In as much as I do not want to lose the use of this library for any length of time, this upgrade process will performed slowly with tiny steps.

Can Programming Be Strictly Portable Relative To Language?

October 12, 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: Currently, I believe that the common name problem can be resolved using the script calling capability of the script software parts library. This require a different form of certification chain capabilities which will probably require upgrading the certified copy library. The script software parts library has been sufficiently upgraded that I should be able to restart this development activity.

Development of Utility Libraries

October 12, 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.

My apologies for inadequacies in my blogging efforts.  I have had a non-related significant distraction from my research/development activities. These distractions have not as yet been completed.  Hopefully in a few weeks…

SCRIPT TUESDAY ACTIVITY: The transfer of text data from a calling script to the called script via the calling arguments has been successfully accomplished. There is still integration problems associated with the use of this data in the called program. The solution of these integration problems will be addressed next.

SCRIPT THURSDAY ACTIVITY: The software parts associated with a script calling another script have been modified and checked out. These software parts can now be used. Being able to pass parameters to the script in the _RUN_SCRIPT command has not been implemented.  There is still work to be done to upgrade the script library.