Posts Tagged ‘software’

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?

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

June 6, 2017

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

Never patch the program!!!.

A patch is usually a last minute change which is not clearly
thought out.

The product delivery is usually close at hand.

Management is saying “All you have to do is …” (The most
dangerous phrase in the English Language).

The patch will probably violate RULE 1 (The strict use
of standard methods).

None-the-less, avoid the short-cut and you will more likely
find the solution to the problem.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 2 — But You Have a BS Degree in Software Engineering

January 27, 2014

A College Education does not qualify you to be truly a “software engineer”?!

Your degree was granted to you when you successfully completed a set of classes.

Each class is basically a reward / punishment training process.

You satisfy the instructor, you get a good grade.

For all intents in purposes, you cannot become more skilled than the instructor.

To do so usually means that you are not using the techniques that he is teaching.

Disagreeing with the instructor usually does not result in good grades.

MORE IN THE NEXT MESSAGE

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 10, 2014

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?

Developing a Website using a software parts library

November 1, 2013

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page.  It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site.  I told him my plan to use my tool
to rebuild my site.  He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

FRIDAY: 2013/11/01

STATUS: The script related modifications to the software parts of the
CSS Output Library have been made.

NEXT TASK: My next task will be to update and test the CSS output
library with the modified parts.

Life of A Programmer — Session 3 — But You Have a Challenging Software Engineering Job.

October 31, 2013

You have a challenging job with a great software engineering company.

You have a software engineering degree from an excellent university.

Financially, you are upper-middle class.

You have a nice house in a upper-class neighborhood.

Your feel that your future is certain.

I beg to disagree.  If you can accurately predict the future, you are in the wrong business.

MORE IN THE NEXT MESSAGE

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?

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE HAS BEGUN

September 24, 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?

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

September 23, 2013

The Tool, if it is to be compliant of the principles of
ISO-9001 must be capable of:

1.0 Developing a system of Standard Methods.

2.0 Exclusively using these Standard Methods in the
development of product.

3.0 Testing all work-products from the Standard Methods
all the way to the Product.

An experimental beta development system that satisfies
these requirements is available on my web-site, http://www.whatifwe.com

I have developed both a Linux and Windows Open Source version.

They can be downloaded free-of-charge.

The download has a fairly decent manual.

THE END

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

September 20, 2013

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

Never patch the program!!!.

A patch is usually a last minute change which is not clearly
thought out.

The product delivery is usually close at hand.

Management is saying “All you have to do is …” (The most
dangerous phrase in the English Language).

The patch will probably violate RULE 1 (The strict use
of standard methods).

None-the-less, avoid the short-cut and you will more likely
find the solution to the problem.

MORE IN THE NEXT MESSAGE