Posts Tagged ‘precedence’

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

September 29, 2013

ERROR-FREE SOFTWARE DEVELOPMENT — DOES SOFTWARE “BREAK”?

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?

Advertisements

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

September 27, 2013

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?

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

September 22, 2013

With the right development program, you can develop Error
Free Software.

There are some historical examples of this truth.

In the early 1960’s, Fortran was a major computing languages.

The Fortran compiler had a never ending bug list.

PL/1, the next major language, was far more reliable.

I used it at Lockheed for over five years and never encountered
any errors.

PL/I was designed in strict compliance with the principles of
simple precedence.

MORE IN THE NEXT MESSAGE

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

August 7, 2013

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

August 4, 2013

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 CONTINUES

June 15, 2013

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

June 15, 2013

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

June 13, 2013

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 CONTINUES

May 15, 2013

ERROR-FREE SOFTWARE DEVELOPMENT — DOES SOFTWARE “BREAK”?

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

May 7, 2013

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?