1. Wearable Interface 3

2. Agenda Introduce Team Team Values Problem Statement Use Scenario
Customer Requirements
Engineering Requirements
Risk Management
Project Planning
Questions & Comments

3. Team Introductions Name Major Role Willow Baker ME Project Manager
Alice Fischer CE Technical Writer
Vincent Yu IE Lead Purchaser
Sarah Kordiyak EE Fabricator
Nick Breeman EE PCB Lead Designer
Tim Preskenis BME Facilitator
Jonathan Hoey EE Lead Engineer

4. Team Values Punctuality Communication Being open to other ideas
Speaking up if confused
Doing assigned work
Sharing ideas if you have them
Respect each other and the project
Honesty
Check in regularly

5. Problem Statement Project Description Current State Desired State
Phones are something that require full attention to interact with, causing people to be distracted when using them. If the person is walking while using their phone this can be a problem. The idea of this device is to allow the user to be paying attention to their surroundings and have their hands free while still be interacting with their phone through a device worn on one hand that is used to input commands through certain motions.
Current State
Prototypes that were created in previous years that are too large, uncomfortable, and do not work very well.
Desired State
The device should be small, comfortable, and respond well to the inputs it is given without being too distracting to the wearer.
Project Goals
Decide on a sensor type
Going through the older model and seeing what is usable

6. Use Scenario

7. Customer Requirements
We separated customer requirements into categories and assigned them each an Importance ranking. We also assigned a Feasibility rating that denotes how confident we as a team feel about our chances at accomplishing that task. Each of these uses a scoring system with 9 being very important / very feasible. Priority is an additive combination of these scores, and serves as an overall score that we can organize requirements with. For example, SF2 pertains to battery protection circuits. This is very important to ensure the safety of the user and product, and is also very simple to integrate, so it gets a maximum Priority of The primary customer needs boil down to the categories shown. Functionality and performance fall under electrical engineering, while durability and comfort are on more of the biomed / mechanical side of things. Aesthetic design is also something to be considered, as this is a product that aims to be a consumer device, and competition already exists.

8. Engineering Requirements
rqmt. #
Importance
Source
Engr. Requirement (metric)
Unit of Measure
Marginal Value
Ideal Value
Direction of Improvement
ER1 9
CV7
Communication Delay ms
300
100
Minimize
ER2 6
CV6
Battery Life hr 8
Maximize
ER3 1
CV3
Recharge Rate 2
Minimize*
ER4 3
CV4,CF2
Weight
oz. 20
14-16
ER5
CV4, CF2, CF3
Vertical Profile mm 12
ER6
CF3, CF5
Adjustability
Range of inches
8" to 10"
6" to 12"
ER7
CV5,CF1
Comfort
ER8
CV2, FN4
Amount of possible controls
Number of inputs 27 70
ER9
DR2,SF4,DR1
Durability
J / m²
ER10
CF4
Removal / Equip time s. 30 5
*Charging faster than 1C can
be dangerous
The qualitative customer requirements are translated into quantifiable engineering requirements here. Each requirement here refers to the corresponding customer requirement and gives some rough numbers about what we think we can realistically accomplish (Marginal Value), what we hope to accomplish (Ideal Value), and the direction we should be working towards. These are also given a Importance rating based on the customer requirement importance ratings and how we as engineers view the severity of each issue.

9. Risk Management

10. Project Planning

11. Questions or Comments?