The What If We Programmable Test System greatly facilitates the integration
of software test into all levels of a software development project. Software Modules and Kits can be easily tested
for not only proper operation but also resistance to programming errors relative to their use.
Testing the modules (subroutines, functions, classes, etc)
that make up the software product can greatly improve the effectiveness of the overall test effort. The module is less
complex than the product and hence can be more thoroughly tested. This will greatly reduce the total number of tests
needed to produce a quality product.
Modules can be designed with methods that are resistant to
programming errors relative to their use. These errors are detected when the executable is prepared (compiled
and linked). Consequently, it is quite costly to quantitatively evaluate programming error resistance capability of
a module. A unique test program will need to be developed for each unique test condition.
The What If We Programmable Test System was designed to rapidly:
Prepare a test program subjecting module to a unique
test sequence
Prepare the associated executable test program (compile
and link).
Execute the test module.
Test sequences are prepared randomly (Monte-Carlo) from a set of defining
rules which can include programming errors that should be detectable during the preparation of the executable test program.
This program can be used to test programs, modules, or software kits; and will score not only proper operation but also the
successfully detected programming and operational errors.
Formal
Software Quality programs are now practical.
All Quality programs such as ISO9001 have the
following three components:
Enforceable Standard Methods and Procedures:
The collection of software kits rapidly
converges to the software engineering standard
library for the organization.
A Measure
of Quality: The PMTS provides a means of
evaluating the resistance of modules and parts
to errors in the design phase of the project.
A means of updated the
Standard methods or Quality measure: The
responsible organization can easily develop all
of the defining files for the PCG and PMTS.
There are no required "silent partners".
