a. Although this document describes interfaces for MS-DOS, it is anticipated that other platforms will be addressed in the evolution of both the IMA Recommended Practices and the DoD PORTCO initiative. ICW systems based on the Apple II and the Macintosh are widely used, and applications for 0S/2 and Microsoft Windows are starting to appear. Applications also exist for UNIX, VMS, and others.
b. Government procurement policies encourage including OSE application portability profile applications, such as POSIX, GOSIP. and XWindows in contract solicitation documents. While the PORTCO initiative supports this, the architecture will maintain” the general approach and command structure established by MlL-STD-l 379, Appendix D.
c. The ICW Portability Practices contained in this handbook are designed with the intent to adapt them to other operating systems and non-BOX86 hardware platforms. The general structure and functionality of the commands are transferable to other environments. However. substantial portions of the current recommendations, especially the ASCII and binary interfaces, are specific to MS-DOS of necessity.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|Military Handbook- Interactive Courseware for Military Training.pdf||application/pdf||9.01 MB||English||DOWNLOAD!|
Interactive courseware training systems (ICWTS) hardware will host a variety of operating system end authoring system applications to speed courseware development. Because these integrated ICWTSS are usually bundled with sophisticated end proprietary interfaces:
a. The ICW and authoring system software written to operate on one ICWTS will require expansive reprogramming to adapt it to another ICWTS having its own distinct end proprietary interfaces, since these interfaces are usually proprietary to the manufacturer. These reprogramming costs can be eliminated or significantly reduced by adopting standard software interfaces to shield the ICW and authoring system software from ICWTS hardware variations.
b. Portable ICW standards will solve the problems associated with ICWTS component variations and operating system environments by establishing standard interfaces. Standards will isolate the courseware and authoring systems from compliant hardware variations by defining standard software interface and command architectures. The courseware and authoring systems will interact through an application to an intermediate layer, such as VDI Management, rather than interacting through a proprietary interface or directly with the hardware or operating system.