Posts Tagged ‘Document Stadards’

TOOL UPGRADE

July 15, 2011

The activity associated with the maintenance of Programmable Software Development Environment will be presented here.

It is planned to update the development task file by adding a command to allow access to a different development task file. The preparation of the Programmable Software Development Environment manual will benefit from more than one level of development task files.

Advertisements

AUTOMATED DEVELOPMENT LOG PREPARATION

June 17, 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.

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 software part defined by the software parts files contained in the library development project.

The checkout of the revised Programmable Software Development Environment is complete. Status reports have been successfully generated. All versions of the software parts library have been successfully generated.

The revised Programmable Software Development Environment is currently being aggressively tested by using it to revise its manual. When this revision is complete and any errors encountered are fixed, the Programmable Software Development Environment will be published. One minor problems has been encountered and fixed.

The Manual Effort requires an update in the Project File, Development Task File, and the Library Sub-Task File sections.

SATURDAY: The Command Sequence, _TASK_NO Command, and _UPDATE Command Pages for the Command Sub-Section of the Library Sub-Task has been completed

SUNDAY: The software parts library sub-task requires that the library sub-task file be read twice; the first to evaluate the need to prepare the library based on the various file dates and the second to prepare it. On the first read, the library subtask file is not displayed. If the second read is necessary, the library subtask file will be displayed. As a consequence, it is very difficult to find syntax errors in the library sub-task file.  Changes to the Programmable Software Development Environment are being planned.

MONDAY:  To facilitate finding syntax errors in the library subtask file, a _DISPLAY command will be added.  This will unconditionally cause the file to be displayed during the first read. The Manual is still being updated to reflect the addition of version control.

TUESDAY: The Version Control, _LIBRARY, _MACRO and _APPEND Command Pages for the Command Sub-Section of the Library Sub-Task have been  prepared.  Proper examples still need to be selected.

AUTOMATED DEVELOPMENT LOG PREPARATION

February 11, 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 software part defined by the software parts files contained in the library development project.

A class for preparing the report has been prepared.  Its integration into the library development classes is progressing.

DOCUMENTATION ERROR — 2010-12-20 — COMPLETION

December 30, 2010

SECTION 9.6.4 _STATE_READ_TEXT COMMAND

The “true” state is returned when the end of file is encountered.

The manual has been corrected and can be found in the appropriate zip file.

You will observe that the manual now has two formats.  Pages in the original format were prepared by Microsoft Word and Front Page.  Pages in the new format were prepared by the Programmable Software Development Environment; i.e., the subject of the manual.

It is my intent to, in an orderly manner, replace all of the pages prepared by Front Page and Word. My Programmable Software Development Environment has provided me with a very easy and completely portable development process.

PORTABILITY METHODS PROJECT

November 12, 2010

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

The current focus is strict portability between a C++ and C# design environment. Specifically, the exact same source definition files must be able to produce functionally identical C++ or C# source files of an error-free product.

Strict compliance with the ISO-9001 requirement for standard methods and processes can only be accomplished by single point definitions.  This can be accomplished by a set of standard software parts libraries and communication mailboxes.

In the set of standards that I am developing, every class will have one associated data structure.  This data structure will either passed to class routines as parameter or be an element of the class.

Development of the Standard Software Parts libraries for defining a data structure is progressing.    The strictly portable standards associated with the basic data elements and those associated with a class data structure have been defined.

The operating system data types must be considered next.  Currently, the operating system data types being considered are the string, input and output text file, and the binary file.

RESUME RESEARCH STATUS REPORT-2010/08/27

August 27, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized *.html files such as used in a users manual.

It has also become apparent that this technology may be useful in the preparation of resumes.

A resume written in a *.txt file format is universally accepted.  A new standard software parts library is needed. Furthermore, the text file resume often needs to be pasted into a window on a web-site. The text file resume format is different in this case.  Specifically, each paragraph of the resume is one long line in the text file.

Currently, the maximum length of each line in the files generated by the Programmable Software Development Environment is 256 characters.  Consequently, this tool is not currently capable of preparing a resume to be pasted into a window on a web-site.

A new version of this tool is currently being developed which will eliminated this restriction thus rendering the resume generation process strictly portable between a printer-friendly file and a website paste-in file. This new version has been prepared and is ready for test which will begin within the next several days.

HTML RESEARCH STATUS REPORT-2010/08/06

August 6, 2010

The user’s manual for the Programmable Software Development Environment using the tool is now being prepared.  all of the pages associated with the Introduction have been completed.

The effort to build a resume using the tool has been progressing.  The two biggest challenges are 1) to prepare a process that is strictly portable between an *.html and *.txt files; and 2) render the document “printer-friendly”.

I performed a number of experiments to determine whether strict portability was achievable between Firefox in an Windowns NT environment and in a Linux (UBUNTU 904, UBUNTU 910) environment. In particular, could the printouts could be made functionally identical.  I determined that this was not achievable. The presentation of the web-page is defined in part by the web-browser and available fonts.  In particular, the printed pages were not always the same.

The text file appears to be the only way to build documents that are strictly portable from printing point of view. Most job sites accept the digital resume in either a *.doc or a *.txt file.  The *.txt file has been around a long time and hence it will the easiest to control the printed text. The next major task is to build an equivalent software parts library for the creation of a properly formatted equivalent text file.

As I have mentioned before, strict potability is a non-negotiable requirement of my efforts.  The *.html software development process and parts are strictly portable between the Linux Ubuntu 904-32 bit, Linux Ubuntu 919 64-bit and Windows XP professional operating system.  The creation of the *.txt file instead of the *.html file must not require any revisions of document definitions files and I am certain that I can accomplish this goal.