TEAM 10: GLove
Spring 2014


MEMBERS

PROJECT CONCEPT

A smart glove that lets you dial and make phone calls, text message, share contacts by shaking hands, play games, control music, control your tv. All with your hands.

To be completed.

MOTIVATION

Being able to use your phone without physically holding your phone is the next big step in mobile techology. Putting this tech into a glove makes sense because people are used to wearing them already and it allows natural control of a phone using hand movements.

COMPETITIVE ANALYSIS

TECHNICAL SPECIFICATIONS

Hardware: Software: Protocols:

REQUIREMENTS

RISKS & MITIGATION STRATEGIES

Risks Mitigation
Glove becomes too heavy or big to wear comfortably. Look into having a custom chip fabricated. Split components across two gloves
Pressure sensors on glove are not precise enough for reliable button presses. Switch to a different type of sensor. Flex sensors, contacts...
Seamlessly networking phones over bluetooth is not possible. Find a way to have the glove transfer information directly between gloves.

Test Cases

Test #1: Sensor Test
Requirement:
User must be able to accurately and quickly type using pressure sensors
Use case:
Texting, calling
Metric:
Ease of use by measuring the number of mistakes per 50 numbers pressed

Test #2: Idle Mode Test
Requirement:
Idle mode should be effective in preventing unwanted behavior
Use case:
Doing things with your hands that does not involve GLove features
Metric:
The time it takes for a user to switch into idle mode. Once in idle mode we will test whether the GLove leaves idle mode without the user’s intent.

Test #3: Handshake Test
Requirement
Two users shaking hands should successfully send contact information 19/20 times.
Use Case
Two users shake hands to exchange contact information.
Metric
Whether two users’ entire contact information was exchanged.

Test #4: Latency Test
Requirement
Time for a character to appear on the LCD should be less than 0.16ms
Use Case
The user texting or making a phone call
Metric
Time from when a user presses a pressure sensor to output appearing on the LCD

Test #5: Bluetooth Reliability
Requirement
If the bluetooth connection fails, the connection should be reestablished within 10 seconds once the phone and glove are in range again.
Use Case
The user leaves their phone somewhere, leaves, then comes back.
Metric
The time it takes for the phone and GLove to reconnect once the devices are back in range.

TIME LAPSE

PRESENTATIONS & VIDEOS


Back to the top of this page
18-549 course home page