+ All Categories
Home > Documents > Moti Abu & Roee Ben Halevi Supervisors: Prof. Mark Last, Mr. Hanan Friedman 10 April 2011.

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

Date post: 19-Dec-2015
Category:
View: 218 times
Download: 1 times
Share this document with a friend
Popular Tags:
15
Moti Abu & Roee Ben Halevi Supervisors: Prof. Mark Last, Mr. Hanan Friedman SMART DATA SELECTOR 10 April 2011
Transcript
Page 1: Moti Abu & Roee Ben Halevi Supervisors: Prof. Mark Last, Mr. Hanan Friedman 10 April 2011.

Moti Abu & Roee Ben Halevi

Supervisors: Prof. Mark Last, Mr. Hanan Friedman

SMART DATA SELECTOR

10 April 2011

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

Reminder

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

Problem Domain

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

Dataflow in SolutionExperimental Aircraft

Experimental aircraft transmits data to ground receivers

Ground ReceiversSeveral 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

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

Use Cases

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

Use CasesUse Case 2 [UC2]: generate masterPrimary 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.

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

System architecture

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

Sequence Diagrams

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

SDS Data Flow

MasterReader

Scheduler SlaveReader

SlaveReader

SlaveReader

Algorithm

Algorithm

Algorithm

MasterBuilder

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

Class Diagram (Control)

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

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, …

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

User Interface

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

User Interface

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

Task List

Complete prototype – 1.3.2011Testing with benchmarks – 31.3.2011Implementing conclusions from test phase – 10.4.2011Extending prototype:

Phase 1 – halt/resume abilitiesPhase 2 – late integration abilitiesPhase 3 – override abilitiesPhase 4 - error-correcting algorithmsPhase 5 – help/wizard/reports

Testing with benchmarks – 31.4.2011Implementing conclusions from test phase – 5.5.2011GUI characterization and implementation – 20.5.2011Deployment at customer – 1.6.2011Project day – 15.6.2011

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

QUESTIONS…


Recommended