Members Rahul Alavalapati Danton Harrylal

1
Automated System for Instructor Operator Stations
Members Rahul AlavalapatiDanton Harrylal Juli
LimJanuary Realista Meme Thai
CAE Liaisons Tara Cady Kevin Cahill Terry
Hung Mike Pacitti Jeff Torres
CoachDr. Joseph Wilson
2
Brief Overview of Problem Setting

• CAE designs and builds flight simulators for
  pilot-training
• Flight simulators use Instructor Operator Station
  control screens (also called IOS Pages) to
  control practice and flight conditions
• System Engineers
• Determine the controls needed for one simulation
  system
• Create the IOS Pages for each simulation system

3
Instructor Operator Station
4
Sample IOS Page for F18
5
description
sysDescription
Entity-Relation Diagram
systemID
simulatorID
pageTotal
sysName
System
Simulator
ownedBy
have
unit
controlInstID
controlInstName
controlName
controlID
IOSPage
ControlInstance
contains
label
IOSControls
helptText
pageID
pageName
headEngineer
representedBy
depends
funcDescription
funcID
funcName
GUIID
generates
type
CallbackFunctions
GUIObjects
picture
includes
description
position
objectName
fileName
platform
RenamedVariable
SystemVariable
binds
rvID
rvName
rvType
rvDescription
sysVarID
sysVarName
6
Problem Statement

• No software managed approach to the design of IOS
  system interface
• Engineers manually connect IOS Controls to system
  variables
• Creating the files for the simulation is a
  multi-step process
• Variable updates are difficult to track
• Unstructured interaction increases development
  costs and delays schedules

7
Project Objective

• Design an automated web-based database utility
  that
• Creates a more structured process for generating
  the IOS interface and manipulating data of the
  IOS
• Allows the system engineers to efficiently
  manipulate the information from IOS pages
• Provides user-friendly interface for navigation
  through the database
• Increase reuse of the IOS pages and GUI objects
• Decrease errors
• Reduce cost and schedule

8
Business Case

• Assumption Revenue is the engineering cost
  forgone due to a working database
• NPV 698,686
• Average Rate of Return 337
• Payback Period 3.36 months

9
System Specifications

• Allow System Engineers to do the following with
  IOS Page elements
• Search
• Edit
• Delete
• Add
• Utilize Microsoft Access, XML, VBScript, Active
  Server Pages
• Run on Windows 2000/NT

10
Project Highlights

• Populated database with sample data
• Changes to Entity-Relationship Diagram persisted
  until April 1
• Developed working interface for database
  functions using XML and ASP
• Tested extensive list of Use-Cases
• Developed User Manual

11
Three-Tier Application
12
Database Utility Interface

• Uses a General/Hierarchical approach in searching
  for components
• For instance
• View (Search) list of all available simulators
  along with their corresponding IOS Pages
• Search for the rest of the components from there
• Edit (Delete, Add, Modify) components at each
  resulting page

13
(No Transcript)
14
Adding a component
Editing a component
15
(No Transcript)
16
Testing 282 Specific Use Cases

• For Example

17
Wrap Up

• Product Verification/Testing resulted in 84.4
  success rate in terms of the 282 Use Cases (238
  pass, 44 fail)
• IOS pages developed by CAE are based on a
  commercial GUI builder tool, SL Corporation
  Graphical Modeling System (SL-GMS)
• Following project next year will work on
  extracting data from the SL-GMS and populating
  the database