A brief examination of ADA however indicates that the language is far more extensive than is needed to successfully code the vast majority of avionic software. One possible approach therefore is to establish what is effectively a proven sub-set of ADA commands and to use only those constructs in the construction of avionic programs. This sub-set would not be implemented explicitly as a separate ADA compiler but rather would use the full compilers already available. All that would be done would be those portions on the compiler which are necessary for avionic programs would be tested and proved to be reliable. The avionic software engineer would then only use those portions of the language which have been approved for avionic purposes. It is suggested that this approach would not infringe the concept that ADA should not be sub-setted which presumably is to prevent the proliferation of a wide variety of ADA sub-sets and hence loss of commonality. This implicit avionic sub-set of ADA would be capable of producing code which could be compiled using the fill ADA compiler. All that would happen is that many of the ADA constructs would not be used. This is of course the case in all programs since, in general, each program uses only a sub-set of the full language available.
Avionic software and ADA
Avionik-Software und ADA
1981
5 Seiten
Aufsatz (Konferenz)
Englisch
DAIS avionic software development techniques
AIAA | 1975
|Software for modular avionic systems
Tema Archiv | 1990
|DAIS avionic software development techniques
Tema Archiv | 1975
|NTIS | 1987
|