Summary statements relative to the Independent Research and Development programs can be found in this category. Software Engineers are invited to contribute their personal IRAD summary statements in this category.
PURPOSED OF IRAD CATEGORY
December 7, 2009PURPOSE OF TOOLS CATEGORY
December 7, 2009Although all of the tools available on the web-site, www.whatifwe.com, are well documented, their use is not always obvious. This category has been provided to assist the user in the use of these tools and to report any problems.
BETA VERSION PHILOSOPHY
January 26, 2010The Programmable Software Development Environment is a beta version. This means it is a work in progress driven by an extensive personal research and development effort focused on the development of portable error-free software using enforceable standard methods and processes.
The program is continually tested by using it on real problems. Errors will be discovered from time to time. Most of these errors will occur in the error-handling sub-systems which do not get exercised at the same rate as the functional sub-systems. These errors will be reported in this blog and corrected in a timely manner with a set of new download files. The corrected version of the program will not be considered a new version of the program.
New capabilities will be added from time to time as needed. New capabilities will result in revisions to the web-site and a new set of download files which will be considered a new version of the program.
If the user needs to access previous downloads, a more complete collection can be found on CodePlex under the Project Title “Programmable Development Software Environment”.
2012-01-26 ERROR
January 27, 2012My 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…
An Algorithmic Error has been encountered in the _ENCRYPT, _DECRYPT commands which produces an “Illegal InpuLength” user error (Pardon my spelling)
Can Programming Be Strictly Portable Relative To Language?
January 20, 2012The 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: I am continuing to modify the common routine software parts library and I have started to modify the CPP routine software parts. I have completed the declaration script up to the argument list.
Is Strictly Portable Web-Site Development Possible?
January 3, 2012The 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: I have re-examined the common routine library and have found it to be too complex (Simplify and add lightness). Every class has a data structure. There are three routine types: 1) Routines that process the data structure and return data, 2) Routines that process the data structure and do not return any data, and 3) a routine the processes and returns the status/error reporting. Their implementation for the service and client classes will be different for each of the languages. I have started to modify the common routine software parts library
Open Source Software Development Tool: Upgrade Progress
January 3, 2012It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.
MONDAY: The modified Programmable Software Development Environment is capable of accessing up to 16 levels of development task files. This Programmable Software Development Environment has been published and can be downloaded.
Is Strictly Portable Web-Site Development Possible?
December 30, 2011The activity associated with the maintenance of whatifwe.com web-site be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the web-site files using the Programmable Software Development Environment.
FRIDAY: The software part that prepares one or more paragraphs has been modified.
Open Source Software Development Tool: Upgrade Progress
December 23, 2011It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.
FRIDAY: Checkout of the Windows upgrade is complete. The preparation of the Linux version is next.
SATURDAY: Modification and checkout of the Linux upgrade is complete. The modification of the manual to reflect these changes is next.
MONDAY: The modifications to the development task section of the manual has been started.
WEDNESDAY: An maximum number of post office error handling error was encountered and identified. It will be fixed.
THURSDAY: The post office error has been corrected and the manual has been updated. Windows and Linux packages will be prepared for upload.
Can Programming Be Strictly Portable Relative To Language?
December 16, 2011The 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: I hope that all readers had a good Thanksgiving. I have examined the software parts library associated with the definition of a routine (name, arguments, return, etc). It does not appear to require modification. I will proceed to integrate it to the service class base where its client owns the data.
Open Source Software Development Tool: Upgrade Progress
December 16, 2011It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.
FRIDAY: I hope that all readers had a good Thanksgiving. I appeared to have violated one of my basic principles in developing the upgrade: “Simplify and add Lightness”. I have modified the typedef.h, define.hpp and associate *.mac files to implement the capability of handling up to 16 development task files using an array. The modification are proceeding; they appear to be a much simpler design.
MONDAY: The modifications to the devprj routines of the Programmable Software Development Environment have been completed and are ready for test.
TUESDAY: The modifications to Programmable Software Development Environment have been tested relative to a single-level development task file. Testing of multi-level development task files will commence.
WEDNESDAY: Testing of multi-level development task files has revealed an error in the revised precall, precallproc, and precallutil routines. I plan to return to the original routines.
THURSDAY: Using the original precall, precallproc, and precallutil routines was successful. Two multi-level error conditions will be tested next.
Open Source Software Development Tool: Upgrade Progress
November 18, 2011It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.
FRIDAY: The modifications to Programmable Software Development Environment have been tested relative to a single level of development task file with an error. Testing of multi-level development task files has begun.
SATURDAY: The modifications to Programmable Software Development Environment have been tested relative to a multi-level development task files. Testing of multi-level development task files with an error is next.
MONDAY: Testing of multi-level development task files with an error has revealed an error in the management of task numbers in the development task file. The correction of this error has begun.
Open Source Software Development Tool: Upgrade Progress
November 11, 2011It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.
THURSDAY: The modifications to Programmable Software Development Environment have been tested relative to a single level of development task file. Testing of a single level of development task file with an error will commence.
