Development of Utility Libraries

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

CERTIFICATION BLOG: Inorder to certify that a product has been developed in strict compliance with the specified standards and has not been patched, pseudo-random longitudinal parity bits must be included in source code in the form of comments. These comments can be at the end of each line (C, C++, C#), at the beginning of each line (HTML), or at the end of each statement (Visual Basic).  This blog will present the research and development section associated with upgrading the existing output library to facilitate both the generation and the testing of all three forms of product source code.

CERTIFICATION TUESDAY ACTIVITY: There are existing libraries for writing source code. One of these libraries writes source code with the parity bit at the end of each line.  The other writes at the beginning. There is no well-developed way of testing the parity at this time. The first step is to define a structure which will facilitate the writing and testing of all three output formats.

CERTIFICATION WEDNESDAY ACTIVITY: It occurred to me last night that in the development of a software source file, there are two checkout / formal testing phases; one to certify the proper preparation of the source file and the other to certify its proper execution.  Arrows and dates will be used to record the status of both phases. As a consequence, it is probably easier to use a separate comment line at the end or beginning of each source statement to report the status of the statement and contain the parity bit.

CERTIFICATION THURSDAY ACTIVITY: There are three basic forms of output file: Programmable Software Development Environment files; source code files, and document text files. The Programmable Software Development Environment files will always have a comment at the end of the line with the parity byte.  The source code files will have a comment line following each statement with the parity byte. The document text file has no comment. In this case certification information can be added to the text by randomly increasing spaces from one to two blanks.


Tags: , , , , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: