Archive for January, 2013

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 23, 2013

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

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 22, 2013

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.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 21, 2013

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.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 19, 2013

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.

Open Source Software Development Tool: Upgrade Progress

January 18, 2013

It is planned to upgrade the Programmable Software Development Environment to include the capability of reading the paste-in text files where the each paragraph is one very long line.

Currently, the Programmable Software Development Environment has the capability of reading a standard ASCII text file where the TAB character is replaced with a suitable number of blanks. Each line of the text file cannot be longer than 256 characters. On the other hand, the Programmable Software Development Environment has the capability of writing a paste-in text file where each paragraph is one very long line. This capability includes the ability to include special characters such the TAB.

The ability to read the paste-in text file is needed to certify that the file has not been changed, was developed using the agree-upon standard libraries, or has not been illegally copied.

THURSDAY: The utility procedures for precfile.cpp for reading a “paste-in” file have been prepared, integrated into the standard text reading system, and tested in a Win32 environment with Win32 text files (lines ending with CRLF characters). These utilities still have to be tested with Linux generated files (lines ending with LF character) and in a Linux machine. This will be done next and no difficulties are expected.  Once this is done, the Programmable Software Development Environment instructions for reading the long paste-in text file lines can be defined.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 18, 2013

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

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 17, 2013

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?

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 16, 2013

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.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 15, 2013

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.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 14, 2013

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.