Archive for the ‘IRAD’ Category

PROGRESS REPORT

June 18, 2020

2020-06-16

Common Class Struct library

The software parts associated with the loading
structure data into the associated postoffice
have been functionally tested.
The functional testing of the software parts
associated reading this data has begun.

2020-06-17

Common Class Struct library

The construct and destroy routines have been
illegally called twice. The commonnameslibrary
has been upgraded to eliminate this problem.

PROGRESS REPORT

May 28, 2020
2020-05-25

STRUCT LIBRARY

The revised classcommonstructlibrary has been successfully prepared
and is ready for a functional test.  The preparation of the test
files is the next task. 

2020-05-26

STRUCT LIBRARY

The preparation of the test files has begun and a problem with
the interface with the classcommonarraylibray has been discovered.  
Specifically, the definition of the multi-dimensional array was
not consistant with its use.  The needed modifications to the
classcommonarraylibrary will be prepared and tested next.

PROGRESS REPORT – 2020-04-23

April 30, 2020

2020-04-25

The development of the struct library addressed the
following issues:

1: If the structure or element has the same name as
an array, it is an array. Additional software
parts were prepared for structure and element arrays. In these parts, the existence of the array is confirmed.

2. If the structure or element is not an array, the
corresponding software parts will report an error if
there is a corresponding array name.

3: Structures have status variables defined according to same rules as the element.

4: It is important to know which structures are not
components in other structures. For each structure,
a post office for containing the structure names that
use the given structure as an element has been defined. It will now be possible to determine / verify that a given structure is a base structure (one not used in another structure).

 

PROGRESS REPORT – 2020-04-23

April 23, 2020

2020-04-18

A preliminary attempt to modify the struct library
has come up with the following questions:

1: If the structure or element has the same name as
an array, is it unconditionally become an array?

2: Do structures have status variables?

The answer to both is “yes”.

PROGRESS REPORT – 2020-03-19

March 26, 2020

2020-03-20

The Array Library has been significantly modified. Every array specification will be associated will be associated with a element or a structure. The array name will be a uniquely modified name of
the element or structure. In defining the array, the element or
structure name will be used. The revised version was functionally tested. Some additional minor modifications are still required.
2020-03-24

The Modified Array Library completely tested on the Windows, Linux, and Windows machine. Its modification has been completed. The next step will be to modify the Struct Library to include the array library modifications and the status variables.

 

PROGRESS REPORT – 2020-03-19

March 19, 2020

2020-03-12

The Element library modified to include a status variable for each element variable defined has been
thoroughly tested on the Windows, Linux, and Apple machines. The next task will be to examine the Array library with the status variable in mind.

2020-03-14

The Array Library defines various array sizes without specifying the specific variable that it is used on. In particular a specified array definition can be used on any number of variables. Status variables can apply to each element in an array or to the array as a whole.
The basic question is to determine whether the status
variable specification should be made in the array library or the struct library where the arrays are used.

PROGRESS REPORT – 2020-03-12

March 12, 2020

2020-03-05

The Typedef library software parts has been thoroughly tested in the windows environment. The next step will be to prepare it for export to the Linux and Apple machine.

2020-03-06

The Typedef library software parts library has been successfully exported to both the Linux and Apple machine. The next task will be to integrate status typedef into the Element library.

2020-03-09

The Element library has been modified to include a status variable for each element variable defined. It has been functionally tested. The next task sill be to thoroughly test the library.

 

PROGRESS REPORT – 2020-03-05

March 5, 2020

2020-02-28

The Typedef library software parts has been upgraded to include the required definition of the status typedef. The associated library has also prepared. The functional tests will be started.

PROGRESS REPORT – 2020-02-06

February 6, 2020

2020-02-02

Both the read and load Modifications of the typedef library have been successfully tested on the Windows machine. Next task is to prepare the parts file for export to the Linux and Apple Machine.

2020-02-03

Both the read and load Modifications of the typedef library have been successfully tested on the Apple and Linux machines. No corrections or modifications of the software parts was needed. Next task will be to test its error handling capabilities

 

PROGRESS REPORT – 2020-01-30

January 30, 2020

2020-01-26

Modifications to the typedef library parts has begun.
A part for defining the status typedef has been prepared.

The software parts associated with loading the sign and
unsigned typedef have been modified to eliminating the
empty value specification.

The typedef library parts for reading typedefs will be
modified next.

2020-01-26

The preparation of the typedef library parts is complete.
The next step is to prepare the associated typedef library.

2020-01-28

Modification of the typedef library preparation file and
the resultant library has been successfully accomplished.

Next task is to modify the associated test file and retest
the library.