Archive for January, 2011

AUTOMATED DEVELOPMENT LOG PREPARATION

January 28, 2011

Keeping an accurate log of the development process is becoming increasingly difficult and time consuming. Modification of Programmable Software Development Environment to automate this record keeping process has begun and for the present will be top-priority.

Each of the software parts commands can be terminated by a comment.  This comment can be used to provide a checkout breakpoint, “;<—-“.  It can also be used to associate a completion date with the command.

The process associated with the development of standard software parts will consist of the following four versions: experimental, alpha version, beta version, and released version.

The release state is where every one of the commands has a completion date and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The beta state is every one of the commands has a completion date or breakpoint and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The alpha state is every one of the commands has a completion date or breakpoint.

The experimental state has no constraints relative to the commands relative to a completion date or breakpoint.

A Text file report will be prepared each time a software parts library is modified. This report will contain the total number of commands, the number of commands with checkout breakpoints, and the number of commands with today’s date in each of the associated software parts files.

Advertisements

AUTOMATED DEVELOPMENT LOG PREPARATION

January 21, 2011

Keeping an accurate log of the development process is becoming increasingly difficult and time consuming. Modification of Programmable Software Development Environment to automate this record keeping process has begun and for the present will be top-priority.

Each of the software parts commands can be terminated by a comment.  This comment can be used to provide a checkout breakpoint, “;<—-“.  It can also be used to associate a completion date with the command.

The process associated with the development of standard software parts will consist of the following four versions: experimental, alpha version, beta version, and released version.

The release state is where every one of the commands has a completion date and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The beta state is every one of the commands has a completion date or breakpoint and the software parts library is certified as being unchanged using a pseudo-random longitudinal parity.

The alpha state is every one of the commands has a completion date or breakpoint. A TBD Text file report will be prepared each time a software parts file is modified.

The experimental state has no constraints relative to the commands relative to a completion date or breakpoint.

PORTABILITY METHODS PROJECT

January 14, 2011

A critical goal of the Programmable Software Development Environment is strict portability between operating systems and source languages.

One of the goals is strict portability between a C++, C#, C, and Visual Basic design environment.

Relative to software portability, the challenge is to produce a single point definitions of all relevant information. A post office is being used to communicate data from its definition sub-task to the sub-tasks where it is used.

There are currently four sub-tasks under development:  The Include, Data Type, the Data  Structure, and the class sub-tasks.

The Includes sub-task defines the relevant data associated with the Imports (Visual Basic), using (C#) and the #includes (C++, C) statements. The Includes sub-task has been completed.

The Data Type sub-task defines the relevant data associated with the data types. Included are the names of data structures. The Typedef sub-task is tentatively complete pending upon revisions required by the class task.

The Data Structure sub-task defines the relevant data associated with a specific data structure. The Data Structure sub-task is tentative complete pending upon revisions required by the class sub-task,

A Strictly portable class definition sub-task will now be started.

Keeping an accurate log of the development process is becoming increasingly difficult and time consuming. Modification of Programmable Software Development Environment is currently being considered as a possible means of automating this record-keeping process.

PORTABILITY METHODS PROJECT

January 7, 2011

A critical goal of the Programmable Software Development Environment is strict portability between operating systems and source languages.

One of the goals is strict portability between a C++, C#, C, and Visual Basic design environment.

Relative to software portability, the challenge is to produce a single point definitions of all relevant information. A post office is being used to communicate data from its definition sub-task to the sub-tasks where it is used.

There are currently three sub-tasks under development:  The Include, Data Type, and the Data Structure sub-tasks.

The Includes sub-task defines the relevant data associated with the Imports (Visual Basic), using (C#) and the #includes (C++, C) statements.

The Data Type sub-task defines the relevant data associated with the data types. Included are the names of data structures.

The Data Structure sub-task defines the relevant data associated with a specific data structure.

A Strictly portable Data Types sub-task has been defined for all of the source languages. The next effort will be to integrate the Includes and Data Type post office into the Data Structure sub-task.  This sub-task will produce a source file as well as a post-office.