Posts Tagged ‘software’

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

August 6, 2018

To become a Software Engineer with a Quality Assurance
capability, you must implement a basic philosophical change.

Software is not an art form; the computer is not the easel
where you can express your creative juices.

You will become an engineer responsible for providing tools
and services that will affect public safety.

You think not. I beg to disagree.

I was transferring $1000 between my savings and checking
accounts when the ATM went down. It took the bank half a
day to find my money.

You ask, what do I need to do in order to improve my quality
and be more indispensable to my employer.

RULE 1 — RIGOROUSLY USE STANDARD METHODS.

RULE 2 — TEST ALL WORK PRODUCTS.

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

RULE 4 — NEVER USE A PATCH TO SOLVE A PROBLEM.

MORE IN THE NEXT MESSAGE

PROGRESS REPORT

June 21, 2018

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

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

2018/06/14

PORTABILITY PROJECT

A windows version of the stndpcg executable has
been prepared and tested using the the Windows
gcc compiler/ link editor. The next task is to
prepare an equivalent make file for the apple machine.

2018/06/17

RELATIVITY BOOK / TOASTMASTERS

I have been using Toastmasters as an experimental laboratory for developing
my book. The evaluation of my last speech suggested a significant update
to make my “speed of light” discovery more understandable. Today, I
discovered a possible understandable example, namely a traffic signal.
Specifically, how does the signal behave when the vehicle velocity is
greater than the speed of light? I plan to make another speech.

2018/06/19

PORTABILITY PROJECT

A successful stndpcg make file has been made for apple machine.
It was successfully used to prepare a functioning apple stndpcg
executable. The stndpcg program is now completely portable
between the Windows, Linux and Windows machine. The next
task will be to make the explrpde portable.

ISO9001 BASED SOFTWARE ENGINEERING

June 12, 2018

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?

PROGRESS REPORT

June 7, 2018

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

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

2018/05/22

COMMON CLASS STRUCT LIBRARY

The functional tests of the CommonClassStruct library have been successfully
completed. The certification tests which include error detection will now be
started.

2018/05/29

COMMON CLASS LIBRARIES

A common problem throughout all of the commonclass libraries is the enforcement
of unique alias names. For example, a typedef alias name cannot subsequently used
to define a structure. A unique enforcement technique is to add additional descriptive
characters. For example the typedef name “name” would be in reality name_typedef.
This enforcement technique will be implemented. The certification tests for the
CommonClassStruct will be delayed until these modifications are completed.

2018/06/06

COMMON CLASS LIBRARIES

The unique alias enforcement problem has been solved by using a layered library
methodology. Adding additional text to the alias name was not necessary.
Some minor modifications to the CommonClassStruct will be implemented next.

PROGRESS REPORT

June 1, 2018

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

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

2018/05/22

COMMON CLASS STRUCT LIBRARY

The functional tests of the CommonClassStruct library have been successfully
completed. The certification tests which include error detection will now be
started.

2018/05/29

COMMON CLASS LIBRARIES

A common problem throughout all of the commonclass libraries is the enforcement
of unique alias names. For example, a typedef alias name cannot subsequently used
to define a structure. A unique enforcement technique is to add additional descriptive
characters. For example the typedef name “name” would be in reality name_typedef.
This enforcement technique will be implemented. The certification tests for the
CommonClassStruct will be delayed until these modifications are completed.

Software “Breaks”!

May 8, 2018

A 17 year old sailor on a submarine must be able to
fix a critical piece of electronic equipment within
15 minutes.

Critical submarine hardware has the required subsystems
to facilitate the location of a failed replaceable components.

Most hardware these days has at least one computer within it.
This includes critical submarine systems.

Can the same 17 year old sailor on a submarine find and
correct a critical software failure within 15 minutes?

Does software “break”? Not really. but software fails when
it illegally or incorrectly writes some data.

Programmers have many ways of preventing illegal writes which
they use in checkout and then remove before delivery.

WHATIFWE used formal illegal write prevention code in delivered
software?

Monte-Carlo Test Method

April 10, 2018

A Number of years ago, I had a contract to build a hardware
control sub-system software product.

This hardware control sub-system was designed to control
legacy hardware shipped back from the Middle East.

This legacy hardware appeared to have not been well-maintained;
it needed a lot of service.

I was afraid that I might break this hardware when I tested my
hardware control sub-system software product.

I developed a Monte-Carlo Simulator/Stimulator Test System to
validate my hardware control sub-system product.

The Monte-Carlo technology is based on a pseudo-random generator.
It was originally used in the development of nuclear weapons.

The random nature of my Monte-Carlo Test System enabled me to
rapidly and thoroughly test the hardware control sub-system, both
from a user and hardware point-of-view.

The use of a Monte-Carlo Simulator/Stimulator Test System
enabled me to deliver an error-free software product.

WHATIFWE used Monte-Carlo software test methods for all software.
Would we get better products?

PROGRESS REPORT

March 30, 2018

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

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

2018/03/23

MAKE FILE GENERATOR

The preparation of the STNDPCG make file has been started. The
preparation of the list of the source files and their dependencies has
begun with the entry of three source files.

2018/03/26

CLASS STRUCT LIBRARY

The sttruct software parts libraries have been prepared for the Linux, Apple,
and Windows machines

2018/03/27

MAKE FILE GENERATOR

The preparation of the STNDPCG make file continues. An additional
four source files and their dependencies has been added to the list of the source files

RELATIVITY BOOK

The relativity book has been update from the speech that was given last Saturday

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

Software “Breaks”!

August 8, 2017

A 17 year old sailor on a submarine must be able to
fix a critical piece of electronic equipment within
15 minutes.

Critical submarine hardware has the required subsystems
to facilitate the location of a failed replaceable components.

Most hardware these days has at least one computer within it.
This includes critical submarine systems.

Can the same 17 year old sailor on a submarine find and
correct a critical software failure within 15 minutes?

Does software “break”? Not really. but software fails when
it illegally or incorrectly writes some data.

Programmers have many ways of preventing illegal writes which
they use in checkout and then remove before delivery.

WHATIFWE used formal illegal write prevention code in delivered
software?