This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Testing for training: Applying new technologies to an improved training readiness
Technical Paper
2002-11-0020
Sector:
Language:
English
Abstract
At present the most commonly used scheme for the validation of
commercial flight simulators is based on unit testing. The engineer
first executes a series of unit tests to validate the design.
Thereafter, the manufacturers' quality control evaluation test
pilot conducts the same series of tests to independently assess the
simulator fidelity. Finally, the customer re-executes the same unit
testing and, time permitting perhaps some training scenarios to
confirm that the flight simulator has been built according to the
contractual specifications. In using this approach, most of the
testing effort is dedicated to unit level testing, while the
customers only spend a portion of their time ensuring training
suitability. Should customers and instructor pilots concern
themselves with detailed unit level testing? Should they not
primarily concern themselves with integrated testing and the
overall training suitability of the simulator? Usually instructors
and pilots appreciate a well-engineered simulator; but, the real
satisfaction is found in being able to execute training that
ensures safe operational flying of the aircraft.
A solution to achieve this specific satisfaction and to meet the
critical operational issues (COI) of simulator operators is to
perform ""operational testing"" during the
acceptance phase to validate that simulators ensure proper
training. Realizing this solution, without adding additional time
to the build schedule for operational testing is not easy.
Similarly, one cannot eliminate unit testing and perform only the
operational testing. A solution can only be found in maximizing the
use of new technologies to change the testing process enabling unit
testing, integrated engineering testing, and operational testing
without increasing simulator schedule build time.
The authors recently defined and developed a hierarchy of
platforms for software development and testing. In this hierarchy,
system design occurs on a ""A"" platform that
resides within the design engineers' workspace. This design
platform is followed by a ""B"" platform that
is the first level using integrated simulations to perform
independent integrated unit testing. The ""C""
platform is the second level independent testing platform. This
platform is used to run independent integrated software and
hardware engineering testing. Some simulator systems may not be
present on the ""C"" platform such as motion,
flight controls and visual; however, a great deal of testing can
still be achieved. Finally, the third level of independent testing
platform is the full flight simulator (Platform
""D""). This platform is used to execute
integrated engineering tests that cannot be run on lower level
platforms as well as the operational testing.
This paper describes the architecture of these platforms and how
they can be used for testing as well as the methodologies used to
define the unit level, integrated engineering, and operational
testing.