Posts Tagged ‘Software Development Documentation’

Development of Presentations

September 21, 2012

The activity associated with development of presentation documents that
can be used over the Internet or in a group meeting.

I met Tisha Silvers, a Marketing Strategist on a LinkedIn Group
Discussion. She show sufficient interest in my technology that I
eventually wrote her a recommendation.

I wrote her recommendation with my resume development application
(software parts library). I subsequently offered to show her how I
wrote this document. I felt that this might be easiest way for her to
relate to my technology. She accepted this plan.

I chose my manual development application as the means of preparing
this presentation. This application builds documents in the HTML file
format. These files can be presented over the Internet, at a group
meeting using a projecting computer, and can be printed for further
reference.

I will present my presentation development activities on this blog.

PRESENTATION TUESDAY ACTIVITY: I have decided that the next page will
introduce the recommendation text file and three document generation
files that defined it.

PRESENTATION WEDNESDAY ACTIVITY: I have completed the page that
introduces the recommendation text file and three document generation
files that defined it. The page describing the header/special phrases
is next.

Advertisements

PORTABLE SOFTWARE DEVELOPMENT

August 26, 2011

MONDAY: To properly update the certification software parts library, it is necessary to update the libraries that prepare the output source files.

TUESDAY: A means of updating the certification software parts library that did not require updating the libraries that prepare the output source files was found. Testing of the certification software parts library has been started.

THURSDAY: The testing of Includes software parts library has been completed. Minor changes in  the libraries that prepare the output source files were required. The certification library will need to be further modified relative to testing of the product source code. (Common Criteria, First Article Test, etc).

AUTOMATED DEVELOPMENT LOG PREPARATION

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

MONDAY:  Examples have been tentatively prepared.  The remaining pages of the Library Sub-Task have been prepared. A proof-examination of the pages needs will be performed next.

TUESDAY: A Format error in the header of the Manual was discovered. Specifically, multiple colons followed the Titles in some of the Header Lines. The software parts associated with the generation of the header has been corrected

THURSDAY: The proof-examination of the manual revealed errors that were corrected. A second proof-examination will be performed next.

AUTOMATED DEVELOPMENT LOG PREPARATION

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

FRIDAY: After making a required update of my UBUNTU Linux Operating System, I encountered the following system error in the recompiled Programmable Software Development Environment:

PCG ERROR: devproj — 306
PCG ERROR: mainprj — 1300
PCG ERROR: explrpde — 187

SATURDAY: The cause of the error has been identified. The required changes will be implemented in both the Windows and Linux versions.  The Windows version will be updated first due to the better debugging capabilities of Visual Studio.net

SUNDAY: The Manual Pages for the Library Version Control Sub-Section of the Library Sub-Task Section have been completed. The Command Sub-section is next.

MONDAY:  The required changes to the Windows version of the updated Programmable Software Development Environment have been successfully implemented.  The changes to the Linux version will now be implemented.

TUESDAY: The required changes to the Linux version of the updated Programmable Software Development Environment have been successfully implemented.

THURSDAY: The Table of Contents page for the Command Sub-Section of the Library Sub-Task has been completed

AUTOMATED DEVELOPMENT LOG PREPARATION

May 13, 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: Preparations were made for the LIBRARY Sub-Task File section of the manual. This is the last section that must be updated before the latest version of the Programmable Software Development Environment can be published. These preparations included the LIBRARY SUB-TASK FILE Table of Contents.

THURSDAY: The OVERVIEW page for the library sub-task section has been prepared. Also, preparations  were made for the version control sub-section of the library sub-task section.  These preparations included the associated table of contents.

AUTOMATED DEVELOPMENT LOG PREPARATION

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

FRIDAY: Preparations were made to create the _LIBRARY_PROJECT and _SOURCE_PROJECT pages from a single point source. Each of previous sections each had one post office containing the special phrases needed for the section.  The development section will need three post offices; one for the section, one for the _LIBRARY_PROJECT page, and one for _SOURCE_PROJECT page.

MONDAY:  The _LIBRARY_PROJECT and _SOURCE_PROJECT command pages for the development task section have been updated using a single point source.

TUESDAY: The _MAKE command page for the development task section has been updated using a single point source

AUTOMATED DEVELOPMENT LOG PREPARATION

April 22, 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.

Friday: The DISPLAY command page for the Development Task File has been prepared using the Single Point Source prepared for the Project File command. An error that prevents a macro call with nine arguments was discovered.  This error will not prevent the continued update of the manual.

Saturday:   The error discovered yesterday was corrected. Calling a macro with nine arguments now works correctly.

Tuesday: The _TASK_NO command page for the Development Task File has been prepared. Due to the fact that this command is used in both the source and library sub-tasks, a Single Point Source was used.

Thursday: The _DEBUG command page for the Development Task File has been prepared. Due to the fact that this command is also a software parts command, a Single Point Source was prepared.

AUTOMATED DEVELOPMENT LOG PREPARATION

April 15, 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 page for the Development Task File section has been started, This page is similar to the Command Sequence page for the Project File. Both of these pages will be defined by a single point text source.  Improvements on both pages are expected.

Monday:  The Command Sequence Page for both the Development Task File and Project File sections should be completed by tomorrow,

Tuesday: The Command Sequence Page for both the Development Task File and Project File sections has beens completed.  The pages for the Development Task file commands will now be started. Single Point sources will be used where appropriate.

Thursday: The _UPDATE command page for the the Development Task File has been prepared. Due to the fact that this command is used in both the source and library sub-tasks, a Single Point Source was used.

AUTOMATED DEVELOPMENT LOG PREPARATION

April 1, 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. The Development Task File section has been started. The associated software parts library has been updated to facilitate the preparation of similar text with a single point source.  Similar commands (_DRIVE_PATH for example) provided the motivation.

AUTOMATED DEVELOPMENT LOG PREPARATION

March 25, 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. The Project File file section has been completed. The Development Task File section will be updated next.