Posts Tagged ‘programming standards certification’

PROGRESS REPORT

November 10, 2017

This purpose of this post is to publish single line
reports on the projects performed during the week.

**************************************************************
**************************************************************

2017-11-03

STRUCTURE SOFTWARE PARTS LIBRARY

The loading commands of the structure software parts library has been prepared.
Preparing the read commands is the next step.

**************************************************************

2017-11-07

STRUCTURE SOFTWARE PARTS LIBRARY

The preparation of the read commands of the structure software parts library has been started.
The capability of reading the number of structures and the structure name associated with
a specific integer has been implemented..

**************************************************************

2017-11-09

STRUCTURE SOFTWARE PARTS LIBRARY

The preparation of the commands of the structure software parts library has been completed.
Preparing the software parts library is next.

Advertisements

Life of A Programmer — Session 8.2 — Tools Help Make The Software Engineer

June 27, 2017

The Tool, if it is to be compliant of the principles of ISO-9001 must be capable of:

1.0 Developing a system of Standard Methods.

2.0 Exclusively using these Standard Methods in the development of product.

3.0 Testing all work-products from the Standard Methods all the way to the Product.

An experimental beta development system that satisfies these requirements is available on my web-site, http://www.whatifwe.com

I have developed both a Linux and Windows Open Source version.

They can be downloaded free-of-charge.

The download has a fairly decent manual.

THE END

Can Programming Be Strictly Portable Relative To Language?

October 1, 2016

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++, and Java; and Linux based C and C++, and Java.

SATURDAY: 2016/10/01

STATUS: The classcommonnames library has been developed and fully tested.

DETAIL: All of the development language have collections of name. They specify data types, data names, structures, class names, subroutines and arguments. Most of these names require the definition of other names. For example, data name needs a data type. This library provides the capability of defining a name in terms of the other required names. The postoffice capabilities of the Programmable Software Development Environment define the communication between libraries.

RESULTS: It is ready for use.

NEXT TASK: The next library will define the data types. Four libraries being considered. One will be a common library and the other three will be for C, C++, and Java.

Can Programming Be Strictly Portable Relative To Language?

June 14, 2016

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: 2016/06/14

STATUS: The CPP output library has been successfully tested. It is
ready for use.

NEXT TASK: The next task will be to examine previously CPP development
activities to determine the next step.

Can Programming Be Strictly Portable Relative To Language?

May 3, 2016

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: 2016/05/3

STATUS: The CPP output library has been prepared and is ready for
test. This library has the required header commant instruction.

NEXT TASK: The test tasks will now be developed for the C++ output
library.

Can Programming Be Strictly Portable Relative To Language?

September 18, 2015

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

THURSDAY: 2013/09/17

STATUS: The write and verification test files have been prepare and are ready to be used to both check out and thoroughly test the common program output library.

DETAIL: This library has both the capability of writing an output file and verifying that a previously created file has not been modified.

RESULTS: The need to thoroughly test the library has resulted in test files that were much larger and more complicated than expected. The conditional test library needs to be upgraded.

NEXT TASK: The next task will be to prepare the test task definition files and start performing the tests.

Can Programming Be Strictly Portable Relative To Language?

July 27, 2015

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

MONDAY: 2015/07/27

STATUS: This project has been restarted by preparing a common program
output library.

DETAIL: This common output library will be capable of 1) making a
comment line, indenting a program line, and making lines of any length.

RESULTS: The Certification process has been prepared and the Setup has
been started,

NEXT TASK: The Indentation Variable has been defined. Incrementing and
Decrementing a specific Indentation is next

Can Programming Be Strictly Portable Relative To Language?

June 12, 2015

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

FRIDAY: 2015/06/12

STATUS: This development effort has been backlogged for several years.

RESULTS: The basic output library developed for document and web-site development is a good starting point for this project. This library has the capability of certifying that the output source code has been developed exclusively with the approved software libraries and has not been modified by any patches.

NEXT TASK: I will restart this project by preparing output libraries for C, C++, Visual Basic, and C##. A common set of a commands will be defined first.

Development of Basic Text Write/Certification Utility Libraries

August 26, 2013

The effort associated with the development, upgrading and testing the  basic output software parts library will be documented here. If there is anyone who desires to assist me in this development process, please contact me by e-mail.

The affected software parts and their functional description are listed below. The purpose of this library is to be able to write or certify one or more text files. These parts are similar to object oriented subroutines. The parts that have been completely tested are noted.

_BASIC_OUT_CONSTRUCT: Initializes the library for a write or certification function.

_BASIC_OUT_DESTROY:   Completes the operation by eliminating the specific setup. COMPLETELY TESTED.

_BASIC_OUT_BEGIN_SETUP: Begins a setup procedure by which the files to be processed are specified. COMPLETELY TESTED.

_BASIC_OUT_ADD_FILE: Add a file to the process list.

_BASIC_OUT_END_SETUP: Completes the setup procedure. COMPLETELY TESTED.

_BASIC_OUT_GET_WRITE_NO: Utility: Search the output file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_GET_READ_NO: Utility: Search the input file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_ALIAS_FORMAT: Utility: Check for duplicate file specification.

_BASIC_OUT_FILES_BEGIN: Begin the processing of files. COMPLETELY TESTED.

_BASIC_OUT_FILES_END: Ends the processing of files. COMPLETELY TESTED.

_BASIC_OUT_TEXT: Processes a text segment in a specified file.

_BASIC_OUT_CHAR: Processes a special character in a specified file.

_BASIC_OUT_END_LINE: Processes a CRLF in a specified file.

_BASIC_OUT_READ_SEGMENT: Utility — Reads a text segment or special character.

_BASIC_OUT_BASIC_READ: Utility — Basic Read for text segment, special character, or CRLF. COMPLETELY TESTED.

_BASIC_OUT_FILE_LINE_END: Utility — Find the next CRLF in the file.

_BASIC_OUT_ERROR_INITIAL: Utility — Initial Error Management System file.

_BASIC_OUT_ERROR_RECORD: Utility — Record Error, COMPLETELY TESTED.

_BASIC_OUT_ERROR_END_FILE: Utility — Record Unexpected End of File. COMPLETELY TESTED.

_BASIC_OUT_ERROR_READ_OK: Utility — Permission to read a line. COMPLETELY TESTED.

_BASIC_OUT_GET_NO_ERRORS: Return the number of error entries.

_BASIC_OUT_GET_ERROR_TYPE: Return the error type associated  with a error number.

_BASIC_OUT_GET_ERROR_LINE_NO: Return the line number associated with a error number.

_BASIC_OUT_GET_ERROR_PREP_NO: Return the preparation number associated with a error number.

_BASIC_OUT_TEST_NO_ERRORS: Verify the number of error entries.

_BASIC_OUT_TEST_ERROR_TYPE: Verify the error type associated with a error number.

_BASIC_OUT_TEST_ERROR_LINE_NO: Verify the line number associated with a error number.

_BASIC_OUT_TEST_ERROR_PREP_NO: Verify the preparation number associated with a error number.

_BASIC_OUT_WRITE_REPORT: UTILITY — Record a certification error. COMPLETELY TESTED.

_BASIC_OUT_VERIFY_ALIAS: UTILITY — Verify Postal Alias .

MONDAY: 2013/08/26

STATUS: The testing of the capability to start testing at a specified line has been started.  When the starting line read and the starting line to be generated are the same, the process appears to be functional. The implementation of this feature was found to be inadequate when the starting line read read and the starting line generated are not same.

DETAIL: Each file may need a different number of lines to be read before testing begins.

NEXT TASK: The number of lines to be read before testing begins will be specified for each file in the _BASIC_OUT_ADD_FILE, not the _BASIC_OUT_CONSTRUCT module.  The necessary modifications will be made.

Development of Basic Text Write/Certification Utility Libraries

August 20, 2013

The effort associated with the development, upgrading and testing the  basic output software parts library will be documented here. If there is anyone who desires to assist me in this development process, please contact me by e-mail.

The affected software parts and their functional description are listed below. The purpose of this library is to be able to write or certify one or more text files. These parts are similar to object oriented subroutines. The parts that have been completely tested are noted.

_BASIC_OUT_CONSTRUCT: Initializes the library for a write or certification function.

_BASIC_OUT_DESTROY:   Completes the operation by eliminating the specific setup. COMPLETELY TESTED.

_BASIC_OUT_BEGIN_SETUP: Begins a setup procedure by which the files to be processed are specified. COMPLETELY TESTED.

_BASIC_OUT_ADD_FILE: Add a file to the process list.

_BASIC_OUT_END_SETUP: Completes the setup procedure. COMPLETELY TESTED.

_BASIC_OUT_GET_WRITE_NO: Utility: Search the output file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_GET_READ_NO: Utility: Search the input file list for the the specified file. COMPLETELY TESTED.

_BASIC_OUT_ALIAS_FORMAT: Utility: Check for duplicate file specification.

_BASIC_OUT_FILES_BEGIN: Begin the processing of files. COMPLETELY TESTED.

_BASIC_OUT_FILES_END: Ends the processing of files. COMPLETELY TESTED.

_BASIC_OUT_TEXT: Processes a text segment in a specified file.

_BASIC_OUT_CHAR: Processes a special character in a specified file.

_BASIC_OUT_END_LINE: Processes a CRLF in a specified file.

_BASIC_OUT_READ_SEGMENT: Utility — Reads a text segment or special character.

_BASIC_OUT_BASIC_READ: Utility — Basic Read for text segment, special character, or CRLF.

_BASIC_OUT_FILE_LINE_END: Utility — Find the next CRLF in the file.

_BASIC_OUT_ERROR_INITIAL: Utility — Initial Error Management System file.

_BASIC_OUT_ERROR_RECORD: Utility — Record Error, COMPLETELY TESTED.

_BASIC_OUT_ERROR_END_FILE: Utility — Record Unexpected End of File. COMPLETELY TESTED.

_BASIC_OUT_ERROR_READ_OK: Utility — Permission to read a line. COMPLETELY TESTED.

_BASIC_OUT_GET_NO_ERRORS: Return the number of error entries.

_BASIC_OUT_GET_ERROR_TYPE: Return the error type associated  with a error number.

_BASIC_OUT_GET_ERROR_LINE_NO: Return the line number associated with a error number.

_BASIC_OUT_GET_ERROR_PREP_NO: Return the preparation number associated with a error number.

_BASIC_OUT_TEST_NO_ERRORS: Verify the number of error entries.

_BASIC_OUT_TEST_ERROR_TYPE: Verify the error type associated with a error number.

_BASIC_OUT_TEST_ERROR_LINE_NO: Verify the line number associated with a error number.

_BASIC_OUT_TEST_ERROR_PREP_NO: Verify the preparation number associated with a error number.

_BASIC_OUT_WRITE_REPORT: UTILITY — Record a certification error. COMPLETELY TESTED.

_BASIC_OUT_VERIFY_ALIAS: UTILITY — Verify Postal Alias .

THURSDAY: 2013/08/15

STATUS: The end-of-file testing has been successfully completed. The testing of its multiple error processing capability has been successfully started.

DETAIL: The software parts library is designed to be able to have up to a user specified n-consecutive lines with errors before terminating execution. The basic technique appears to be functional

RESULTS: This library has been sufficiently tested to render it usable in various applications.

NEXT TASK: The testing of its multiple error processing capability will continue.