Posts Tagged ‘Formal Monte-Carlo Test Process’

Monte-Carlo Test Method

October 23, 2018

A Number of years ago, I had a contract to build a hardware
control sub-system software product.

This hardware control sub-system was designed to control
legacy hardware shipped back from the Middle East.

This legacy hardware appeared to have not been well-maintained;
it needed a lot of service.

I was afraid that I might break this hardware when I tested my
hardware control sub-system software product.

I developed a Monte-Carlo Simulator/Stimulator Test System to
validate my hardware control sub-system product.

The Monte-Carlo technology is based on a pseudo-random generator.
It was originally used in the development of nuclear weapons.

The random nature of my Monte-Carlo Test System enabled me to
rapidly and thoroughly test the hardware control sub-system, both
from a user and hardware point-of-view.

The use of a Monte-Carlo Simulator/Stimulator Test System
enabled me to deliver an error-free software product.

WHATIFWE used Monte-Carlo software test methods for all software.
Would we get better products?

Advertisements

Monte-Carlo Test Method

July 11, 2017

A Number of years ago, I had a contract to build a hardware
control sub-system software product.

This hardware control sub-system was designed to control
legacy hardware shipped back from the Middle East.

This legacy hardware appeared to have not been well-maintained;
it needed a lot of service.

I was afraid that I might break this hardware when I tested my
hardware control sub-system software product.

I developed a Monte-Carlo Simulator/Stimulator Test System to
validate my hardware control sub-system product.

The Monte-Carlo technology is based on a pseudo-random generator.
It was originally used in the development of nuclear weapons.

The random nature of my Monte-Carlo Test System enabled me to
rapidly and thoroughly test the hardware control sub-system, both
from a user and hardware point-of-view.

The use of a Monte-Carlo Simulator/Stimulator Test System
enabled me to deliver an error-free software product.

WHATIFWE used Monte-Carlo software test methods for all software.
Would we get better products?

Can Programming Be Strictly Portable Relative To Language?

March 19, 2013

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++.

TUESDAY: 2013/03/19

STATUS: The software parts for generating and running the format
scripts has been modified to use a post office rather than a local
dictionary.

DETAIL: This will render it possible to define a standard format set
separately from its use.

NEXT TASK: I have not forgotten about the software parts associated
with calling a format.  The next task will be to prepare format
commands associated with adding a pseudo-random string of blanks.  This
will be used as a means of protecting proprietary information.  A
varying number of blanks at the end of each line is hard to visually
detect and is a very good means of making the source files detectably
unique.

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.

Development of Utility Libraries

September 21, 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 TUESDAY ACTIVITY: I have prepared an error software part that
detects a lack of initial preparation before loading the commands. The
implementation of this software part is progressing. The modifications
of the calling commands will be performed next. This will include the
inclusion of this error detection software part.

Economical Rigorous Software Testing at All Levels

August 10, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

FRIDAY: A local script only exists in the task in which it was created. It is discarded when this task is complete. A global script that calls a local script in a particular task will fail to execute in a subsequent task.  The associated error is now properly reported. The single line this script calling capability for global and local scripts has now been sufficiently tested that it can been used for manual development.

SATURDAY: To determine what additional changes are needed to the script software parts library, I need to answer the question: How much is the script going to simulate a macro?  In the past, I made a limited effort. Maybe a complete simulation is needed. I will re-examine this question

MONDAY: To make the script simulate a macro, I will need to improve the script calling arguments and return capabilities, and both the automatic and global data storage. I have tentatively decided to proceed with the update.  The script calling arguments will be first. The planned improvement will include a parameter capability for the _RUN_SCRIPT macro.

Economical Rigorous Software Testing at All Levels

August 3, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

FRIDAY: The single line macro-loading local-script (script defined in the same task as it is executed) software parts of the script software parts library have been modified and formally tested. These commands load the macro name and up to four arguments into a specified local script so that they will be executed when the script is executed. The formal testing of the single line macro-loading global (capable of being executed in a later task than defined) is next.

SATURDAY: The single line macro-loading global-script (capable of being executed in a later task than defined) software parts of the script software parts library have been modified and formally tested. The formal testing of multi-line equivalent macro-loading software parts is next.  These parts enable macros with more than four arguments to be loaded into a script.

MONDAY: The formal testing of both the global and local multi-line equivalent macro-loading software parts has been successfully completed. I believe that the corrections required for the testing of the common-include software parts library has been accomplished.  My next step is to verify my assessment and to update the status of the script software parts library relative to the manual upgrade.

TUESDAY: A script is capable of calling another script. The software parts library associated with manual development uses this script calling capability. The formal testing of this capability has been started. An error reporting deficiency has already been detected and will be corrected.

WEDNESDAY: A local script only exists in the task in which it was created. It is discarded when this task is complete. A global script that calls a local script in a particular task will fail to execute in a subsequent task.  The associated error is not properly reported. The necessary corrections will be made next.

Is Strictly Portable Web-Site Development Possible?

May 11, 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++.

TUESDAY: In reviewing the language specific routine libraries development process, It is necessary to note that at this point we will be writing source files. Of particular importance is the certification that these source files have not been modified after the fact. The “Patch” must be eliminated from the design process.

THURSDAY: It is not only important to certify that a source file contains no “Patches”, it is also important to certify that the source files have been prepared exclusively with the agreed-upon software parts library. This need can best achieved by the cryptographic capabilities of the Programmable Software Development Environment. The pseudo-random generator based cryptographic algorithms of the Programmable Software Development Environment can be the basis of a very accurate certification instrument.

Economical Rigorous Software Testing at All Levels

May 11, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

MONDAY: One of my minor project is the development of a cryptographic software parts library for securing of various text files. A requirement of this cryptographic software parts library is to reliably error-out if the wrong key was used during decryption. The desire to thoroughly test this library caused me to seriously update the concept.

TUESDAY: The revised version of the cryptographic software parts library has been prepared and is ready for a comprehensive test.

THURSDAY: The revised version of the cryptographic software parts library has been functionally tested.  The testing process will continue.

Can Programming Be Strictly Portable Relative To Language?

May 4, 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 required modification and formal testing of the name routine library needed to add a second representation of the routine name has been accomplished.

TUESDAY: The formal tests of user definition step of the common routine library is complete.  The development and testing of the common routine library is complete.  The Language specific routine libraries are next.