Archive for January, 2013

The Twitter Seminar On The Development Of Error Free Software Continues

January 31, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do the job correctly without these constraints.

Would you believe it I told you that all programmers, even the great ones, make errors.

The errors made by the junior programmers show up quickly during checkout and are easy to fix.

MORE IN THE NEXT MESSAGE

Advertisements

Open Source Software Development Tool: Upgrade Progress

January 31, 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.

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.

FRIDAY: 2013/01/25 ************************************************

STATUS: It occurred to me last night that both the reading and the writing of the paste-in text file can be accomplished by one command each; i.e., _READ_SEGMENT and _WRITE_SEGMENT.

DETAIL: The biggest challenge is that multiple use of the command is required to write / read the line. Specifically, writing of the line will not be complete until the Line-feed character is written.

NEXT TASK: Plan the changes to precfile.cpp that will be necessary to implement a one command implementation of the writing and reading of a long paste-line text file line.

THURSDAY: 2013/01/31 ************************************************

STATUS: Each of the text file output commands write a complete line. Each of the text file input commands read a complete line.

DETAIL: The buffer output command set assembles the segments into a temporary file and then when completed, transfer the entire line to the selected output file.

RESULTS: The property of reading or writing a text file one line at a time is important to preserve.  The Write Buffer commands will not be functionally changed.

NEXT TASK: Plan the upgrade to the precfile of the Programmable Software Development Environment to render the read utilities previously developed accessible from the precoper class.

The Twitter Seminar On The Development Of Error Free Software Continues

January 30, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do the job correctly without these constraints.

Would you believe it I told you that all programmers, even the great ones, make errors.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 29, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros would take all of the fun out of the project.

In addition, a highly skilled programmer can be trusted to do the job correctly without these constraints.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 28, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

Restricting the programming effort to a minimal set of macros would take all of the fun out of the project.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 28, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

A computing language is often considered the pallet where the programmer expressive his creative juices.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 26, 2013

CAN WE PREVENT ERRORS DURING SOFTWARE DEVELOPMENT?

Suppose we had a software tool that produced source code exclusively from a set of macros? Would it be restrictive?

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 25, 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?

Open Source Software Development Tool: Upgrade Progress

January 25, 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.

MONDAY: 2013/01/21

STATUS: Checkout of the updated Programmable Software Development Environment relative to reading a LINUX text file in a WIN32 enviroment has begun.

DETAIL: The files defining this blog, written on my LINUX machine, will be used as the test LINUX text files.

RESULTS: This capability has been successfully tested.

NEXT TASK: Install the updated Programmable Software Development Environment on my LINUX machine and verify proper operation.

TUESDAY: 2013/01/22

STATUS: The updated Programmable Software Development Environment has been successfully installed and tested on my LINUX machine.

DETAIL: To avoid problems resulting from differences between WIN32 and LINUX, the precfile source generation file was appropriate modified. The early forms of the Programmable Software Development Environment are not strictly portable between WIN32 and LINUX.

RESULTS: Release forms of the updated Programmable Software Development Environment were installed on both my WIN32 and LINUX machines.

NEXT TASK: Plan the additional Programmable Software Development Environment commands for reading the long “Paste In” lines.

WEDNESDAY: 2013/01/23

STATUS: To facilitate the certification of long “Paste In” lines, a read command set similar to that of the Buffer Output Command set was selected.

DETAIL: Specifically, the commands will be _BEGIN_READ, _READ_SEGMENT, and _END_READ. Special characters such as the TAB will be returned in the “Name” format. Text data will be returned in the “Text Expression” format.

NEXT TASK: The Buffer Output command can only be done one file at a time.  The equivalent read command set can simultaneously process multiple files. The next task will be to determine if the Buffer Output command set can/should be upgraded to be able to simultaneously process multiple files.

THURSDAY: 2013/01/24

STATUS: I have examined the three Buffer Output commands and have found that there is no reason why they cannot be updated to simultaneously process multiple files.

DETAIL: The primary problem is that the modifications will significantly change the commands and hence the current libraries that use them.

RESULTS: I believe that these changes, particularly if from a user point of view, cause the Write commands to behave in an identical manner with the corresponding Read commands. The command names may need to change; For example, _BEGIN_WRITE, _WRITE_SEGMENT, AND _END_WRITE.

NEXT TASK: Plan the upgrade to the Programmable Software Development Environment to implement the _BEGIN_READ, _READ_SEGMENT, and _END_READ commands.

THE TWITTER SEMINAR ON THE DEVELOPMENT OF ERROR FREE SOFTWARE CONTINUES

January 24, 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.