Posts Tagged ‘certification capabilities’

Certifiable Test Methods

July 30, 2015

The activity associated with the development of certifiable test
processes will be presented in this blog.

The conditional test library has provided a good means of checking out
a library product. Currently, it does not produce a certifiable report.

A FAT (First Article Test) and FACT (Factory Acceptance Test) require
that a test report be prepared. Furthermore, this test report must
certifiable relative to the library product and that it has not be
altered.

THURSDAY: 2015/07/30

STATUS: The Conditional Test Library currently prepares a source file
for each set test condition for performing the specific test.

DETAIL: This source file is generated from the 128-Monte Carlo Test
bits in the “Define Test Step” of the Test Project. It has used in the
“Test Program Step”.

NEXT TASK: The subject library must be modified to render it capable of
preparing the report generation source in for the “Record Result Step”.
This report file must equipped with pseudo random parity bits to permit
certification.

Advertisements

Open Source Software Development Tool: Upgrade Progress

January 27, 2014

The overall purpose of the current Programmable Software Development Environment upgrade process is to certify that a product generated is certifiably releasable.

Major improvement have been made from the 1) Implementation of the experimental, alpha, beta, and release versions of a software parts library and 2) the ability to detect whether the product text files have modified manually (patched).

To certify a software parts library, every command defining this library must be executed. This includes all error detection and reporting statements.  These error statements not only include those associated with the user but also those that detect and report programming and Programmable Software Development Environment errors.

Ideally, those _ERROR statements that report programming and Programmable Software Development Environment errors will never be executed. Therefore, they currently can not be included in the certification test sequence. The challenge is to provide a set of commands which will be executed during a test sequence and report a specified programming or Programmable Software Development Environment failure should it occur.

The following two commands need to be developed: 1) _CONTINUE_IF which will error out if the preceeding test condition is false and 2) _CONTINUE_IF_NOT which will error out if the preceeding test condition is true. These statements replace the currently used _JUMP_IF and _JUMP_IF_NOT statements.

SUNDAY: 2014/01/26

STATUS: The update of the Programmable Software Development Environment has been completed and tested in both the Win32 and Linux environments.

DETAIL: The _CONTINUE_IF, and _CONTINUE_IF_NOT have been implemented in the in the global, precmac, precoper source files, compiled and tested. I am now using the resultant Windows and Linux executables.

NEXT TASK: The next task will be to update the manual to include these commands..

Open Source Software Development Tool: Upgrade Progress

January 20, 2014

The overall purpose of the current Programmable Software Development Environment upgrade process is to certify that a product generated is certifiably releasable.

Major improvement have been made from the 1) Implementation of the experimental, alpha, beta, and release versions of a software parts library and 2) the ability to detect whether the product text files have modified manually (patched).

To certify a software parts library, every command defining this library must be executed. This includes all error detection and reporting statements.  These error statements not only include those associated with the user but also those that detect and report programming and Programmable Software Development Environment errors.

Ideally, those _ERROR statements that report programming and Programmable Software Development Environment errors will never be executed. Therefore, they currently can not be included in the certification test sequence. The challenge is to provide a set of commands which will be executed during a test sequence and report a specified programming or Programmable Software Development Environment failure should it occur.

The following two commands need to be developed: 1) _CONTINUE_IF which will error out if the preceeding test condition is false and 2) _CONTINUE_IF_NOT which will error out if the preceeding test condition is true. These statements replace the currently used _JUMP_IF and _JUMP_IF_NOT statements.

MONDAY: 2014/01/20

STATUS: The first step in the plan to develop a release product which has been certified by the task test has been defined.

DETAIL: These two commands will require modifications of the global, precmac, and precoper source files of the Programmable Software Development Environment.

NEXT TASK: The next task will be to upgrade the global source files.

Developing a Website using a software parts library

September 12, 2013

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page.  It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site.  I told him my plan to use my tool
to rebuild my site.  He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

THURSDAY: 2013/09/12

STATUS: The preparation of the software parts associated with the HTML
Output library have been started. Specifically, the _HTML_OUT_CONSTRUCT
and _HTML_OUT_DESTROY parts have been preliminarily prepared.

MR_MIKE_CONTRIBUTION: I received Mr. Mike’s reconstruction of my first
web-site page.  It is nice looking and easy to read.  The code that he
used to make this page is still unfamiliar to me. Questions will be
asked and reported at the appropriate times.

DETAIL: The basic certification capabilities of the Basic Output
Library  will be enhanced by a running pseudo-random parity bit. The
key to the random generator will entered as the first parameter of the
_HTML_OUT_CONSTRUCT software part. This parity bit, the source line
number, and the date will be included as a comment at the beginning of
each line.

MY NEXT TASK: The preliminary preparation of the file setup software
parts will be the next HTML Output library task. Also, a detailed
examination of Mr. Mike’s source code will begin.