P13541: Eye Tracker
/public/

Systems Design

Table of Contents

Benchmarking

Concept Development (generation, improvement, selection)

Product Pugh Chart

Concept Analysis
Solution Interface Camera Processing Illumination
Solution 1 None Built-in Front Facing On Tablet None
Solution 2 Wifi Wireless Security Camera On Tablet None
Solution 3 USB USB Webcam On Tablet IR LED
Solution 4 USB USB Webcam On Tablet Visible Light
Solution 5 USB Monochrome Camera Module Microcontroller/ DSP IR LED

Pugh Analysis

Criteria Weight Specification Solution 1 Solution 2 Solution 3 Solution 4 Solution 5
Power 1 Power Consumption + -1 0 0 -1
Ease of Interfacing 2 No/ Easy /Hard + 0 0 0 -1
Size/Weight to Tablet 1 No/ Some/ Too Much + -1 0 0 -1
Accuracy of gaze Detection 3 Higher or Low -1 -1 + + +
Safety 3 Safe/ Unsafe + + + -1 +
Reliability 2 Yes/No 0 -1 0 0 0
Total + 7 3 6 3 6
Total 0 1 1 4 4 1
Total -1 3 7 0 3 4
Net Score 4 -4 6 0 2

Product Selection

Tablet

public/Photo Gallery/tablet_specs.png

Tablet Pugh Chart

public/Photo Gallery/Tablet Pugh Chart Final.png

Camera Pugh Chart

public/Photo Gallery/Camera Pugh Chart Final.png

Block Diagram

Functional Decomposition

Risk Assessment

ID Risk Item Effect Cause Likelihood Severity Importance Action to Minimize Risk Resolution Owner
Describe the risk briefly What is the effect on any or all of the project deliverables if the cause actually happens? What are the possible cause(s) of this risk? L*S What action(s) will you take (and by when) to prevent, reduce the impact of, or transfer the risk of this occurring? If it exists, what has been a resolution to the risk? Who is responsible for following through on mitigation?
1 Algorithmic Latency in processing imagery The device may not function in real time; Failure to meet customer needs High processing power required by algorithms 3 3 9 Consider benchmarks on algorithms M.Kelly B.Wideman
2 Lack of previous eye tracking experience by group members Improper design None of the team members have used eye trackers before 3 2 6 Research of eye tracking by members Research and meetings with eye-tracking experts T.Podrasky M.Krenzer H.Pichardo B.Wideman M.Kelly
3 Interface from camera to tablet may be complicated and may require additional hardware More time consumption; Additional items attached to tablet Camera may not be readily compatible with tablet 2 2 4 Research interface as soon as possible M.Krenzer H.Pichardo
4 Camera field of view not capturing the eye Inaccurate functionality Improper interfacing between camera and tablet 2 2 4 Using facial recognition software M.Krenzer H.Pichardo
5 Limited time available Failure to complete the project on time Imagine RIT brings sooner deadline; Scheduling conflicts among members 2 2 4 Meetings involve only pertinent members T.Podrasky M.Krenzer H.Pichardo B.Wideman M.Kelly
6 Lead times on components/tablet Less time with devices Some parts can be sold out 2 2 4 Alert user that they are out of camera's field of view T.Podrasky
7 Lack of mechanical engineering expertise Inability to properly mount components to tablet No mechanical engineer assigned 3 1 3 Seek mechanical help if needed; Use a clip; Possibly use a 3D printer to create mounts T.Podrasky
8 Poor library support available More workload for the Computer Engineers in the group; More time needed to accomplish goal Using a different platform 1 3 3 Make sure there is library support before making final decisions M.Kelly B.Wideman
9 Processing power of tablets within our budget could be inadequate Going over budget Components needed are expensive 1 2 2 Finding good deals for components T.Podrasky
Resolved Risks

Home | Planning & Execution | Systems Design | Detailed Design | Build, Test, Document | Photo Gallery | Project Review | Technical Paper | Poster | Final Results and Handoff