Posts Tagged ‘assembly language program’

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

August 10, 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”.

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?

Advertisements

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

June 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?

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

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

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?