Posts Tagged ‘Version Control’

Open Source Software Development Tool: Upgrade Progress

July 10, 2015

The purpose of this update task is improve capability of the Programmable Software Development Environment to certify that a product is error free and functions according to specification.

The current version control defines the status of the software parts files. Specifically, the alpha version is still being tested; the beta version still has code that needs to be tested; and the release version has been completely tested.

A Programmable Software Development Environment equivalent to the First Article Test and the Factory Acceptance Test needs to be developed.

FRIDAY 2015/07/10

STATUS: Both the Win32 and Linux versions of “testproj.cpp” have been successfully modified to use “crypto.cpp” as its random generator.

RESULTS: The resulting Programmable Software Development Environment has been successfully put into service. The Win32 and Linux versions now appear to functioning identically.

NEXT TASK: My next task will be to prepare this version for publication.

Advertisements

Open Source Software Development Tool: Upgrade Progress

May 29, 2015

The purpose of this update task is improve capability of the Programmable Software Development Environment to certify that a product is error free and functions according to specification.

The current version control defines the status of the software parts files. Specifically, the alpha version is still being tested; the beta version still has code that needs to be tested; and the release version has been completely tested.

A Programmable Software Development Environment equivalent to the First Article Test and the Factory Acceptance Test needs to be developed.

FRIDAY 2015/05/29

STATUS: The Win32 version of “crypto.cpp” has been successfully modified so that it can be accessed by “testproj.cpp”

DETAIL: The modified “crypto.cpp” has been found to be functional on its current use.

NEXT TASK: The next task will be to equivalently modify the LINUX version of “crypto.cpp”.

Open Source Software Development Tool: Upgrade Progres

April 30, 2015

The purpose of this update task is improve capability of the Programmable Software Development Environment to certify that a product is error free and functions according to specification.

The current version control defines the status of the software parts files. Specifically, the alpha version is still being tested; the beta version still has code that needs to be tested; and the release version has been completely tested.

A Programmable Software Development Environment equivalent to the First Article Test and the Factory Acceptance Test needs to be developed.

THURSDAY: 2015/04/30

STATUS: I have decided to replace the test random generator with the one used as a software parts resource.

RESULTS: Using my secure text library, I formally tested the pseudo-random software parts resources on both the WIN32 and LINUX systems and found that they produced identical results.

NEXT TASK: My next task will be to plan the associated upgrade to test task portion of the Programmable Software Development Environment.

Open Source Software Development Tool: Upgrade Progress

April 18, 2015

The purpose of this update task is improve capability of the
Programmable Software Development Environment to certify that a product
is error free and functions according to specification.

The current version control defines the status of the software parts
files. Specifically, the alpha version is still being tested; the beta
version still has code that needs to be tested; and the release version
has been completely tested.

A Programmable Software Development Environment equivalent to the First
Article Test and the Factory Acceptance Test needs to be developed.

SATURDAY: 2015/04/18

STATUS: Modifications to the Programmable Software Development
Environment are needed.

NEXT TASK: The first sub-task will be selected.

Open Source Software Development Tool Error

February 28, 2015

An** Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: MacCert — 455
PCG ERROR: macproj — 2698
PCG ERROR: macproj — 315
PCG ERROR: devproj — 1400
PCG ERROR: mainprj — 1461
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: MacCert — 474
PCG ERROR: macproj — 2717
PCG ERROR: macproj — 334
PCG ERROR: devproj — 1419
PCG ERROR: mainprj — 1480
PCG ERROR: explrpde — 172

FRIDAY 2015/02/27

STATUS: I restored what I thought was the original WIN32 version. I
compiled both a debug version and release version, and performed some
preliminary tests. To my surprise, I found that nothing changed. The
“restored” versions did not produce the subject error where as the the
production tool being used did.

DETAIL: This surprise caused me to very carefully re-examine the
associated routines, macproj, precmac, maccert, and crypto. I was
looking for a very subtle error or some old coding method no longer
supported and I got my next big surprise. Specifically, my archival
version was not the original version. I checked the Linux version and
it was the equivalent original version.

RESULTS: My version control practices failed! I have a primitive
version control implemented in the Programmable Software Development
Environment and it is woefully inadequate. Improving it will be high
on my priorities.

NEXT TASK: Ny next task will be to very carefully compare the
associated routines of the Linux version with the Windows version to
determine how extensive the version control error is. Once this is
done, I will probably attempt to upgrade the Linux version to see if
it’s original difficulties can be resolved.

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.