Posts Tagged ‘ISO 9001’

ISO9001 BASED SOFTWARE ENGINEERING

September 13, 2017

To be strictly compliant with ISO9001, Programmers must use enforceable standard methods and processes.

Assembly Language Programmers used macros for common multi-instruction processes. These macros, once developed, were never changed.

Software “breaks fatally” when it illegally writes. The error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly competent macro capability to facilitate using error detection code.

WHATIFWE used C++ Macro Preprocessor and its Macros to implement the Standards required by ISO9001.

Advertisements

PROGRESS REPORT

September 1, 2017

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

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

2017-08-26

ARRAY SOFTWARE PARTS LIBRARY

The software parts associated with reading the Array dictionary
has been prepared. An include file for the names software parts
library has been added to the typedef software parts library
to provide access to the names library.

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

2017-08-27

ARRAY SOFTWARE PARTS LIBRARY

The array software parts library has been successfully prepared
and is ready for functional test.

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

2017-08-28

APPLE PORTABILITY PROJECT

It occurred to me that use of a flash drive to transfer the
make file from the Linux machine where it was generated
to the apple machine might have file inconsistency problems.
A better method might be to transfer a *.zip file containing
the make file. I tried it and it seemed to behave better.
Unfortunately, it did not solve the link problem.

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

2017-08-29

ARRAY SOFTWARE PARTS LIBRARY

The functional test for the array software parts library has
been prepared. Some modifications in the array software parts
have been found.

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

2017-08-30

ARRAY SOFTWARE PARTS LIBRARY

The functional test of the array software parts library has
been started. A need for an alias search in the typedef program
has been found. Its development is the next step.

RELATIVITY BOOK / TOASTMASTERS PROJECT

The third book-reading speech has been prepared. It will
be used to correct / improve this section of the book.

PROGRESS REPORT

August 25, 2017

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

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

2017-08-18

RELATIVITY BOOK

The final Conclusion section of the book has been started.
The invitation written in the Introduction was stated again
in the conclusion. The requirements associated with the
continuation of the Personal Research Effort will be prepared
next.

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

2017-08-19

APPLE PORTABILITY PROJECT

An attempt to contact the gcc help center failed due to an
incompatibility between their cite and the Earthlink WebMail
cite that I use. I will attempt to develop a Clang equivalent
development project.

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

2017-08-21

RELATIVITY BOOK

The final conclusion section of the book has been tentatively
prepared. The remaining pages of the book need to be printed
and reviewed.

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

2017-08-23

RELATIVITY BOOK

The final conclusion section of the book has been printed and
briefly reviewed.

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

2017-08-24

ARRAY SOFTWARE PARTS LIBRARY

The software parts associated with loading the Array dictionary
has been prepared. Preparing the software parts associating with
reading Array dictionary is next

ISO9001 BASED SOFTWARE ENGINEERING

June 7, 2017

To be strictly compliant with ISO9001, Programmers must use enforceable standard methods and processes.

Assembly Language Programmers used macros for common multi-instruction processes. These macros, once developed, were never changed.

Software “breaks fatally” when it illegally writes. The error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly competent macro capability to facilitate using error detection code.

WHATIFWE used C++ Macro Preprocessor and its Macros to implement the Standards required by ISO9001?

Life of A Programmer — Session 7.4 — How Do I Become a Quality Assurance Software Engineer

May 29, 2017

RULE 3 — USE OLD, WELL-TESTED, OPERATING SYSTEM CAPABILITIES.

Relative to the operating system, use the old, well established
capabilities and minimize your interface.

Think of it in a similar manner as purchasing a new car.
If you purchase a radically new model, you will become an
unwilling member of the test team.

Similarly do not use a pipe if a file will do as well. Files
were developed long before the pipes.

An above all, do not use its multitasking capabilities unless
absolutely necessary. This capability can expose you to many
challenging problems.

MORE IN THE NEXT MESSAGE

Software Engineers are Quality Assurance Managers

May 9, 2017

Have you ever noticed that Quality Assurance, ISO-9001,
and the Deming Cycle is taught only in Business Administration?

I have found that when Quality Assurance was taught in Engineering
Schools, it was in Engineering Management Classes.

Is Quality Assurance just an Engineering Management Problem? Is
a Software Engineer a Quality Assurance Manager?

Computer Programs are special Deming Plans to be Done at the
client’s site by a computer not by a human being.

Software Engineers are, in reality, Quality Assurance Managers.
For the most part, they do not realize this fact.

WHATIFWE taught Quality Assurance, ISO-9001, and the Deming
Cycle to all Engineers in our Engineering Schools?

I, A Programmer, Am Also A Quality Assurance Manager

April 19, 2017

To be strictly compliant with ISO-9001, Programmers must
use enforceable standard methods and processes.

Assembly Language Programmers used macros for common
multi-instruction processes. These macros, once developed,
were never changed.

Software “breaks fatally” when it illegally writes. The
error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers
use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly
competent macro capability to facilitate using error detection code.

Unlike the Macro Assembler, my C++ Macro Preprocessor prepared
source code exclusively from the Macros.

IBM developed the first piece of error-free software in 1968.
It was the PL/1 Compiler and it was a joy to use.

The PL/I Compiler was error free due the strict application of
the requirements of simple precedence.

In the late 1960’s, Bob Prince of Lockheed developed a simple
precedence based compiler writer which I used.

In the early 1970’s, I used the Lockheed Compiler Writer to
prepare non-compiler applications with moderate success.

I had difficulty with the Compiler Writer on non-compiler
applications because data flows differently than processes.

I realized many years later that a multidimensional precedence
process could manage both processes and the data flow.

I learned how to make a set of coupled precedence processors
that “policed” the use of classes and the flow of data.

I updated my C++ Macro Processor to render it capable of
deploying simple precedence principles to my programming efforts.

My Macro Processor satisfied the Standard Methods and
processes requirements of ISO-9001.

I inadvertently became a Quality Assurance Manager.

Can Programming Be Strictly Portable Relative To Language?

November 13, 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/11/12

STATUS: The development of float decimal library has been started and it was quickly found the many forms of this number created a complex syntax processing problem.

RESULTS: I realized that I could restrict the format to two basic formats, one for float (7 numbers following the period) and the other for double (15 number following period). The period will be preceded by a + or – followed by a 0. The number will end with an e followed by a + or – and two integers. An example for the float number is -0.1234500e+11. An example for the double number is +0.112123489345158e-04.

NEXT TASK: The development software parts for the float library will continue using this restricted format.

Can Programming Be Strictly Portable Relative To Language?

November 7, 2016

MONDAY: 2016/11/07

STATUS: Preparing the second level parts of the typedef software parts library has been started. I found the need to identify and compare (less, equal, and greater) float decimal numbers

DETAIL: Currently, the Programmable Software Development Environment has no float decimal commands. Either the Programmable Software Development Environment would have to be updated or a special float decimal library would have to be developed.

RESULTS: I believe that developing a special float decimal library would take less time than updating the Programmable Software Development Environment.

NEXT TASK: I am suspending the development activity on the typedef software parts library and starting the development of the special float decimal library.

I, A Programmer, Am Also A Quality Assurance Manager

October 12, 2016

To be strictly compliant with ISO-9001, Programmers must
use enforceable standard methods and processes.

Assembly Language Programmers used macros for common
multi-instruction processes. These macros, once developed,
were never changed.

Software “breaks fatally” when it illegally writes. The
error cannot be fixed and it might take the machine down.

There are many error detection code segments that programmers
use during checkout and then remove before delivery.

I developed a C++ Macro Preprocessor to provide a highly
competent macro capability to facilitate using error detection code.

Unlike the Macro Assembler, my C++ Macro Preprocessor prepared
source code exclusively from the Macros.

IBM developed the first piece of error-free software in 1968.
It was the PL/1 Compiler and it was a joy to use.

The PL/I Compiler was error free due the strict application of
the requirements of simple precedence.

In the late 1960’s, Bob Prince of Lockheed developed a simple
precedence based compiler writer which I used.

In the early 1970’s, I used the Lockheed Compiler Writer to
prepare non-compiler applications with moderate success.

I had difficulty with the Compiler Writer on non-compiler
applications because data flows differently than processes.

I realized many years later that a multidimensional precedence
process could manage both processes and the data flow.

I learned how to make a set of coupled precedence processors
that “policed” the use of classes and the flow of data.

I updated my C++ Macro Processor to render it capable of
deploying simple precedence principles to my programming efforts.

My Macro Processor satisfied the Standard Methods and
processes requirements of ISO-9001.

I inadvertently became a Quality Assurance Manager.