Which parts of ADI to replace

There are three aspects of ADI that are deemed to be undesirable.

• Object oriented methods - almost all methods within ADI are to do with file I/O. They require a large amount of unsupported code that can simply be replaced with an IF-THEN-ELSE clause.
• Internal data storage - ADI uses its own private functions to facilitate the storage and retrieval of internal data. Starlink supplies such function in a number of packages which could be used.
• Multiple types and checking - The higher (file type dependent) ADI code performs many repeated checks on operations and allows for the limited case of multiple requests. The removal of both these features allows for much simpler code without seriously affecting the flexibility of ASTERIX.

The first two points are for the reasons outlined in the previous section, the last point is that a simplification of the system that can be performed at the same time for little extra effort in either planning or implementation.

The above scheme will also requires the replacement of all BDI calls, most particularly for points one and three. Thus every user application will have to be altered in the ASTERIX monoliths.