The decision to use operational software as a major component of MPT training software proved to be valid. Although operational software was under development, the attendant risks were minimized by using the build approach and constructing a software development schedule that contained block changes to the MPT software. A rigid, disciplined system approach ensured that requirements were identified and baselined before the build design process was started. To base training software on operational software is not the usual first choice for training software design. However, for MPT, the software architecture largely decoupled operational software from the training-peculiar software. Therefore, operational software revisions did not perturb the training-perculiar software residing in the ICU. Also, training fidelity is guaranteed and maintainability is enhanced. The major problem during MPT software development focused upon the LCC and ICU interface. This was caused primarily by the incomplete documentation which, in turn, was caused by the evolving nature of the operational software. This was tirally overcome by an aggressive and intensive integration test program and by working closely with the customer/user, who had an indepth understanding of the operational software functional performance.
Use of operational software for GLCM missile procedures trainer
Verwendung von Betriebssoftware fuer GLCM-Flugkoerper Verfahrenstrainer
1983
6 Seiten, 6 Bilder, 1 Tabelle
Conference paper
English
Computer-Based Cruise Missile Trainer for Nuclear WSEP
AIAA | 2007
|Computer-Based Cruise Missile Trainer for Nuclear WSEP
British Library Conference Proceedings | 2007
|Use of the Operational Flight Trainer
NTIS | 1966
India's sitara trainer nears operational status
Online Contents | 2014
|