|
|
|
|
|
Object Model |
|
Hardware/Software allocation |
|
API We Provide |
|
Scenario |
|
Sequence Diagram |
|
Service We Need |
|
Status and Schedule |
|
|
|
|
|
|
|
|
|
|
Hardware: none |
|
|
|
Software: Java3D package, CAD software |
|
|
|
|
|
|
|
Inspector starts up the system, authenticate |
|
himself, and gets a work order. |
|
Modeling.ModelControl.initialize(IETM ietm,
Panel p); |
|
Modeling.ModelThread modelthread = new ModelThread(); |
|
AugmentedReality.EventManager.addVectorEventListener(VectorListener
vl); |
|
modelthread.start(); |
|
|
|
|
|
He then goes to the plane and inspect as asked
in the work order. If he find any defects, he would place a sticky. |
|
Modeling.Location loc =
Modeling.ModelControl.convertTo3D(int x, int y); |
|
Modeling.ModelControl.addSticky(Location loc,
String ID, int severity); |
|
When he finish with the work order, he |
|
Syncs with server and exit the system. |
|
|
|
|
|
|
|
Repair is pretty much the same except it may
want to highlight a specific sticky. |
|
Modeling.ModelControl.highlightSticky(String
ID); |
|
|
|
Or he may want to remove a sticky after he is
finished with it. |
|
Modeling.ModelControl.removeSticky(String ID); |
|
|
|
|
|
|
|
|
|
From AR: |
|
Vector events |
|
From Workflow: |
|
A way to store and retrieve documents |
|
A way to obtain a list of work orders |
|
A way to retrieve any work order |
|
|
|
|
Finished with object design and is ready to
implement. |
|
|
|
All public API's finalized by Dec. 1 |
|
Implementation, Nov. 22 - Dec. 5 |
|
Unit Tests, Dec.1 - Dec. 5 |
|
Integration Testing, Dec. 4 - Dec.8 |
|
Notes