Archive for November, 2017

PROGRESS REPORT

November 3, 2017

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

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

2017-10-27

ELEMENT SOFTWARE PARTS LIBRARY

The element software parts library has been functionally tested.
Minor changes have were necessary to both the typedef and element
software parts libraries. The next step is to define the certification
test.

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

2017-10-28

ELEMENT SOFTWARE PARTS LIBRARY

The element software parts library passed the certification test on the LINUX
machine. Performing this test on the Windows and Apple machine is the
next task.

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

2017-10-30

ELEMENT SOFTWARE PARTS LIBRARY

The element software parts library passed the certification test on the Windows
machine. The software parts associated with the Array software parts library
have been modified to use the element parts library

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

2017-11-01

ELEMENT SOFTWARE PARTS LIBRARY

It has been determined that the processing of arrays was best accomplished by
the structure software parts library. The preparation of the structure software
parts library has been started.

Software “Breaks”!

November 1, 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?