Archive for the ‘INVITATION’ Category

The Twitter Seminar On The Development Of Error Free Software Concludes — Session 8

November 15, 2016

PROGRAMMERS ARE SPECIAL QUALITY ASSURANCE MANAGERS!

Requiring our programmers to be special Quality Managers? This would be a terrible inconvenience?

On one of my contracts, I had the opportunity to witness an attempt to become ISO-9001 certified.

There were two ISO-9001 certification meetings; the first with the software manager and the second with QA.

The software manager had no idea as to what his group could do to be compliant with ISO-9001.

The QA manager described the increased formality required to be compliant with ISO-9001.

The body language of my client’s employees told me that no one except management wanted ISO-9001 certification.

One of the requirements of ISO-9001 is the use of “Standard Processes and Methods”.

The use of “Standard Processes and Methods” means that management would control our programming efforts.

Would you believe it I told you that programmers are already using “Standard Processes and Methods”?

No I don’t! As long as I do my job, management leaves me alone. They create more problems than they solve.

Then would you believe it I told you that programmers create their own “Standard Processes and Methods”.

No? How many times have you prepared a new source file by modifying an old previously developed source file?

Your collection of sources files defines your “Standard Methods and Processes” that you use.

Will this help you to develop error-free software? Reflect on your experience. It already has.

WHATIFWE were to make a conscious Quality Assurance Effort? Will it help? Try it, sees what happens.

The Twitter Seminar On The Development of Error Free Software Continues — Session 7

November 7, 2016

Can a software engineer be a Quality Assurance Manager?
Quality Assurance is a management task.

To find out, let us look at the beginning of all Quality
Assurance programs; i.e., the Deming Cycle.

The Deming Cycle, first used in Japan in 1947, consists of
the following four steps.

The first Deming Cycle Step is “make a plan”. The second
Deming Cycle Step is “do the plan”.

The third Deming Cycle Step is “check the results”. The
four Deming Cycle Step is “change the plan if needed”.

The Deming Cycle appears to be a concise definition of
common sense!

Would you believe it if I told you that all programmers
are Quality Assurance Managers?

No! Then would you believe it if I told you that a computer
program is a Deming Plan?

A computer program is a Deming Plan to be done at the
client’s site by a computer, not by a person.

Most Programmers do not understand that they are very special
Quality Assurance Managers.

WHATIFWE required our programmers to be special Quality
Managers? Would this be a terrible inconvenience?

MORE IN THE NEXT MESSAGE

The Twitter Seminar On The Development of Error Free Software Continues — Session 6

October 31, 2016

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code
exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where
the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros
would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do
the job correctly without these constraints.

Would you believe it I told you that all programmers, even the
great ones, make errors.

The errors made by the junior programmers show up quickly
during checkout and are easy to fix.

The errors made by the senior programmer take a long time to
show up and are difficult to fix.

Restricting the “field of play” can greatly simplify the
development process.

Restricting the “field of play” can greatly reduce the
occurrence of errors.

In the hardware world circa 1980’s, management select the
Integrated Circuits to be used in the project.

Unfortunately, management cannot provided the an appropriate
set of software parts.

Programmers are needed to develop an appropriate set of software
parts. Is a programmer a QA manager?

WHATIFWE had a senior programmer who was also a Quality Manager?
Would this help?

MORE IN THE NEXT MESSAGE

The Twitter Seminar On The Development of Error Free Software Continues — Session 5

October 25, 2016

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

It is important to detect and properly respond to an error
condition during the execution of the product.

It is also very important to prevent errors in the software
development process.

Perhaps we should look again at the development of military
hardware, circa, 1980’s.

In the hardware world, Quality Assurance begins with the
selection of a set of parts.

Management selected a set of Integrated Circuits and the
Engineers were required to use them in the design.

Would you believe it if I told you that there is an software
equivalent to the integrated circuit?

There is a “software part” equivalent and it is not an object
(which is more like a circuit board).

We can find our “software part” in the history of software
engineering.

Specifically, it is the macro instruction set in the
macro-assembler circa 1990.

These macros were used to define common multi-instruction
processes such as 4-byte addition in a Z80 machine.

Once defined, these macros were never changed. They became
standard “Software Parts”.

Unfortunately, the use macro instruction set was optional
in the development of an assembly language program.

WHATIFWE had development software tool that produced source
code exclusively from a set of macros?

The Twitter Seminar On The Development of Error Free Software Continues — Session 4

October 17, 2016

Are simple-precedence methods the only way to detect and
prevent errors? No, there are other ways.

To find these other ways, let us look at development of
military hardware, circa, 1980’s.

In a project that I worked on, the sailor needed to replace
no more than four circuit boards to fix the hardware.

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

Would you believe it if I told you that software “breaks”?

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?

The Twitter Seminar On The Development of Error Free Software Continues — Session 3

October 10, 2016

ERROR-FREE SOFTWARE DEVELOPMENT — HOW DO WE HANDLE THE FLOW OF DATA?

In most cases, the management of data is quite different than that of
the associated process.

In the 1960’s, the acronym HIPO defined a basic software documentation
process.

HIPO stands for the following four sections; hierarchy, input, process,
and output.

Obviously, the flow of data was considered different than the associated
process.

Would you believe it if I told you that simple-precedence can also be
used to manage data?

Data Management is also a process. Therefore, Simple-precedence methods
can be used to manage data.

WHATIFWE rigorously used the principals of simple precedence in all
software development? Is that all we have to do?

The Twitter Seminar On The Development of Error Free Software Continues — Session 2

October 3, 2016

HAS A MAJOR ERROR FREE SOFTWARE METHODOLOGY BEEN DEVELOPED?

The principles of simple-precedence produced one of the
best compilers that I have ever used.

Can the principles of simple-precedence be used in the
development of other applications?

Would you believe it if I told you that simple-precedence
has been used in a lot of different applications.

In 1973, IBM introduced the principles of structured
programming.

Strict Structured Programming satisfies the requirements
of simple-precedence.

Strict Structured Programming is a excellent means of
defining an error-free process.

Unfortunately, the management of data is different than
the management of a process.

WHATIFWE developed a simple-precedence means of managing
data? Can we do it?

The Twitter Seminar On The Development of Error Free Software Has Begun — Session 1

September 26, 2016

HAS A MAJOR ERROR FREE SOFTWARE APPLICATION BEEN DEVELOPED?

When was the last time that a computer error created a real
problem for you?

An ATM failure occurred when I was transferring $1000. It took
the bank 5 hours to find it.

Have you heard that the development of error-free software was
economically unachievable?

Would you believe it if I told you that a major error-free
application was developed in 1968.

IBM developed the PL/1 compiler in 1968. It was error-free.
Unlike Fortran, it had no bug list.

How did IBM do it? They developed it in strict compliance
with the principles of simple-precedence.

WHATIFWE developed other applications in strict compliance
with principles of simple-precedence? Can we do it?

The Twitter Seminar On The Development Of Error Free Software Concludes — Session 8

January 3, 2016

PROGRAMMERS ARE SPECIAL QUALITY ASSURANCE MANAGERS!

Requiring our programmers to be special Quality Managers? This would be a terrible inconvenience?

On one of my contracts, I had the opportunity to witness an attempt to become ISO-9001 certified.

There were two ISO-9001 certification meetings; the first with the software manager and the second with QA.

The software manager had no idea as to what his group could do to be compliant with ISO-9001.

The QA manager described the increased formality required to be compliant with ISO-9001.

The body language of my client’s employees told me that no one except management wanted ISO-9001 certification.

One of the requirements of ISO-9001 is the use of “Standard Processes and Methods”.

The use of “Standard Processes and Methods” means that management would control our programming efforts.

Would you believe it I told you that programmers are already using “Standard Processes and Methods”?

No I don’t! As long as I do my job, management leaves me alone. They create more problems than they solve.

Then would you believe it I told you that programmers create their own “Standard Processes and Methods”.

No? How many times have you prepared a new source file by modifying an old previously developed source file?

Your collection of sources files defines your “Standard Methods and Processes” that you use.

Will this help you to develop error-free software? Reflect on your experience. It already has.

WHATIFWE were to make a conscious Quality Assurance Effort? Will it help? Try it, sees what happens.

The Twitter Seminar On The Development of Error Free Software Continues — Session 7

December 30, 2015

ARE PROGRAMMERS SPECIAL QUALITY ASSURANCE MANAGERS?

Can a software engineer be a Quality Assurance Manager?
Quality Assurance is a management task.

To find out, let us look at the beginning of all Quality
Assurance programs; i.e., the Deming Cycle.

The Deming Cycle, first used in Japan in 1947, consists of
the following four steps.

The first Deming Cycle Step is “make a plan”. The second
Deming Cycle Step is “do the plan”.

The third Deming Cycle Step is “check the results”. The
four Deming Cycle Step is “change the plan if needed”.

The Deming Cycle appears to be a concise definition of
common sense!

Would you believe it if I told you that all programmers
are Quality Assurance Managers?

No! Then would you believe it if I told you that a computer
program is a Deming Plan?

A computer program is a Deming Plan to be done at the
client’s site by a computer, not by a person.

Most Programmers do not understand that they are very special
Quality Assurance Managers.

WHATIFWE required our programmers to be special Quality
Managers? Would this be a terrible inconvenience?

MORE IN THE NEXT MESSAGE