Archive for November, 2014

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

November 18, 2014

RULE 1 — RIGOROUSLY USE STANDARD METHODS.

Prepare a minimum set of standard methods that you will use on all your programming effort. Keep them “simple, stupid”.

In the hardware world, the Quality Assurance Manager working with management purchase the set of Integrated Circuits needed to get the job done.

These standard methods are your “Integrated Circuits”.

MORE IN THE NEXT MESSAGE

Advertisements

The Purpose of My Blog

November 18, 2014

The original purpose of my blog was to provide me an easy
means of reporting my activity on my personally funded
research and development activities on error-free software
development methods.

I subsequently expanded the purpose of my blog to encourage
others to improve their skills by conducting their own
regular experimental process.

I became a software engineer in 1966 due to an experiment
that I had performed. I have never taken a course in
Software Engineering. You are encouraged to take a similar
path. If my tools can be of any benefit, they can be
downloaded free-of-charge from my web-site, http://www.whatifwe.com

Open Source Software Development Tool Error

November 18, 2014

An Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: MacCert — 455
PCG ERROR: macproj — 2698
PCG ERROR: macproj — 315
PCG ERROR: devproj — 1400
PCG ERROR: mainprj — 1461
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: MacCert — 474
PCG ERROR: macproj — 2717
PCG ERROR: macproj — 334
PCG ERROR: devproj — 1419
PCG ERROR: mainprj — 1480
PCG ERROR: explrpde — 172

MONDAY: 2014/11/17

STATUS: An examination of the precmac.cpp file reveals that none of the
software parts names were included in the computation in the pseudo
random parity. All of the commands contained in the software parts
were included this computation. The include files have no commands,

DETAIL: It will probably be necessary and desirable to include the
comments in the computation of the pseudo random parity for the release
version. It will probable also be necessary to include the test
sequence in the computation. The associated upgrade for the release
version is not needed to correct the associated system error and hence
will be considered later.

NEXT TASK: Start making the modifications to precmac.cpp needed to add
the software parts name (including the include statement) in the
computation of the pseudo-random certification parity bit.

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

November 15, 2014

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

I, A Programmer, Am Also A Quality Assurance Manager

November 15, 2014

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.

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

I inadvertently became a Quality Assurance Manager.

Life of A Programmer — Session 6.3 — What should a Quality Assurance Software Engineer Know.

November 15, 2014

SOFTWARE ERROR SOURCE 2: THE OPERATING SYSTEM.

The operating system is the silent partner in all software
development activities.

The operating system, also having been developed by human
beings, will also have errors.

Most of the errors will have already been discovered.

The ones that have not been discovered will, in general,
be difficult to fix.

You, as the user, will have no control over that repair
process.

Consequently, you may end up with a difficult task of
working around a system error that was discovered on your
watch.

MORE IN THE NEXT MESSAGE

The Computer Wisdom of Bugs Bunny

November 15, 2014

Do you remember the Bug’s Bunny cartoon where he pops out of the ground
in the middle of the desert and says “I think that I should have turned
left at Albuquerque”?

Mistakes always happen; some because of stupidity, some because of greed;
some because the required knowledge was not available, and some because
we are just human beings.

We are currently experiencing a great many security problems due to
hackers.

The basic computer design that makes this possible has a common program
and data buss. Hackers can cause their program to be loaded on the target
machine via this common buss.

In the late 1970’s, there was a different computer design, the Harvard
Architecture with separate data and program busses. This architecture
cannot be hacked.

About 1985, the microprocessor became practical and the Harvard
Architecture became obsolete.

“Did we turn right at Albuquerque in error”? I believe so. Could
have avoided it? I think not. We could not have predict the future.

Should we re-vitalize the Harvard Architecture? I think the benefits
would greatly out-weigh the costs.

Life of A Programmer — Session 6.2 — What should a Quality Assurance Software Engineer Know.

November 14, 2014

SOFTWARE ERROR SOURCE 1: THE SOFTWARE DEVELOPMENT ENGINEER.

All Software Development Engineers are human beings, not little
green-guys from Mars

All human beings, including Software Development Engineers make
errors.

Software errors created by Junior Programmers are discovered early
and easily fixed.

Errors created by Senior Programmers take a long time to surface
and are usually hard to fix.

You have probably already had to solve a very difficult problem
on a project that you completed a year ago

MORE IN THE NEXT MESSAGE

Limitation to My Response to Your Comments

November 14, 2014

Every day I receive between 50 and 100 comments. Many of these comments request information or advise from me.

I appreciate the honor of your request for information.

Unfortunately, there is only one of me managing and writing the blog. Consequently, I simply do not have enough time to reply to each of your questions.

There are many comments that ask the same question. In these situations where I have the information, I will provide my knowledge in a post, time permitting.

I will respond to any comment made by a person who is experimenting with my software development tools.

Thank You

Robert Adams

Open Source Software Development Tool Error

November 14, 2014

An Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: MacCert — 455
PCG ERROR: macproj — 2698
PCG ERROR: macproj — 315
PCG ERROR: devproj — 1400
PCG ERROR: mainprj — 1461
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: MacCert — 474
PCG ERROR: macproj — 2717
PCG ERROR: macproj — 334
PCG ERROR: devproj — 1419
PCG ERROR: mainprj — 1480
PCG ERROR: explrpde — 172

THURSDAY: 2014/11/13

STATUS: The following error was encountered when I was attempting to
separate the very large CSS Web Site Library into a system of smaller,
more compact libraries

DETAIL: When I developed the Programmable Software Development
Environment Version Control capabilities, I did not properly handle the
the include source files needed for the above library conversion effort.

NEXT TASK: An upgrade to the Version Control Capabilities is indicated.
Minimally, the Include statement must be included in the computation of
its pseudo-random parity computation. Furthermore, to insure that the
software parts files defining the release version of library are not in
any way altered, it may be appropriate to include the comments in the
pseudo-random parity computation The next step is to prepare a plan.