1. Moti Abu & Roee Ben Halevi Supervisors: Prof. Mark Last, Mr. Hanan Friedman 10 April 2011

2. Reminder

3. Problem Domain

4. Dataflow in Solution Experimental Aircraft Experimental aircraft transmits data to ground receivers Ground Receivers Several ground receivers record the data Preprocess unit (XXX-Telemetry records creator) The raw data that was recorded in each receiver is formatted and metadata files are created Smart Data Selector (SDS) Integrates all inputs to one master record that is as close as possible to the original data Analysis tools and QuickView Master record is used for analysis of flight and plotting

5. Use Cases

6. Use Case 2 [UC2]: generate master Primary Actor: Telemetry technician (or common user). Interests: The technician wants to generate a master output from source inputs. Pre-conditions: User opened a new job, loaded sources and defined a configuration. Post-conditions: The master is generated and saved in the job directory with metadata information. Main success scenario: 1. User clicks on "play" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. After confirmation, master output and metadata information are generated according to user configuration and saved in job directory. Main fail scenario: 1. User clicks on "play" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. User cancels master generation.

7. System architecture

8. Sequence Diagrams

9. SDS Data Flow MasterReader Scheduler SlaveReader Algorithm MasterBuilder

10. Class Diagram (Control)

11. User Interface The interface will be implemented according to the KISS (Keep It Simple and Stupid) principles. The interface is designed according to the guidelines and the physical, technological, cognitive limitations, learning and attention limitation that Lansdale & Ormerod (1994) presented. Lansdale, M. & Ormerod, T. (1994), Understanding Interfaces: a Handbook of Human-Computer Dialogue, Academic Press, London. Windows, Frames, Icons, Buttons, …

12. User Interface

14. Task List Complete prototype – 1.3.2011 Testing with benchmarks – 31.3.2011 Implementing conclusions from test phase – 10.4.2011 Extending prototype: Phase 1 – halt/resume abilities Phase 2 – late integration abilities Phase 3 – override abilities Phase 4 - error-correcting algorithms Phase 5 – help/wizard/reports Testing with benchmarks – 31.4.2011 Implementing conclusions from test phase – 5.5.2011 GUI characterization and implementation – 20.5.2011 Deployment at customer – 1.6.2011 Project day – 15.6.2011