P07002design Review 2 Documents 1

P07002design Review 2 Documents 1

P07002Design Review 2 Documents 1

Senior Design 1

P07002

Design Review 2

Date: Friday, November 3, 2006

Time: 9AM – 10AM

Location: 09/2271

P07002 – Two Way Communication Device

Design Review 2

Table of Contents

TopicPage Number

Design Review 2 Itinerary3

Project Introduction4

Concept Overview – Keyboard5

Concept Overview – LCD6

Concept Overview – Power Supply7

Concept Overview – SBC PCM93718

Concept Overview – Program Screenshot9

Potential Failure Modes10

Bill of Materials11

Current State of Design Specs12

Needs Assessment for Reference13

P07002 – Two Way Communication Device

Design Review 2

Design Review 2 Itinerary

Project Introduction/Background - Matt5 minutes

Introduction of team members/disciplines

Background on two-way communication device

Overview and updates of concept design

Software development - Zemma15 minutes

Overview of current state

Actions taken to mitigate risks

Demonstration of feasibility

SBC Selection- Aisosa5 minutes

Memory and storage selection

Heat Dissipation - Scott10 minutes

Overview of heat experiment

Results of heat experiment

Proposed path of heat flow

Proposed solution for heat dissipation

Bill of Materials - Glenn5 minutes

Summary of budget status

Long lead items

Wrap-up (Matt)20 Minutes

Design specifications complete to date

Review of Senior Design II Schedule*

Additional discussion and comments from panel**

*Microsoft Project document to be handed out at review

**This will include a brief discussion concerning the case design of the device

P07002 – Two Way Communication Device

Design Review 2

Project Introduction

Team members:

Matthew Tice – EE – Team Lead

Scott Keller – ME – Heat Dissipation/Case/Durability Subsystem Lead

Nathan Holland – ME – Benchmarking/Data collection Subsystem Lead

Zemma Kassa – EE – Software Development Subsystem Lead

Aisosa Ayela-Uwangue – EE – Components Subsystem Lead

Glenn Snyder – EE – User Interface Subsystem Lead

Project Background:

In the past, faculty and tutors have found that they are having difficulty communicating with hard-of-hearing and deaf students. The only method in which the student can communicate with the professor or tutor is by means of paper and pencil. This method of communication is very slow and tedious and can at times be frustrating to both individuals. The goal of this project is to design a device that will allow users to communicate rapidly and easily with minimal training. Professors and tutors will be able to effectively help students in an efficient manner.

The team started the project by defining the goal of the project and creating a needs assessment. This was accomplished by interviewing several stakeholders including professors, deaf students and hard-of-hearing students. The team then determined the specifications that the design must meet. Brainstorming sessions along with QFD analysis led to concept generation. A solution prioritization matrix was then used to filter several concept ideas down to a final device concept. A meeting was held to discuss risks involved in the implementation of the design that was selected. These risks have been broken down and steps have been taken to mitigate each risk.

This review will cover the overall design of the device in the areas of software development, single board computer selection, heat dissipation, casing design and project budget. Team members will discuss the risks that have been identified and the steps that have been taken to mitigate each risk in order to ensure smooth implementation of the final design.

P07002 – Two Way Communication Device

Design Review 2

Concept Overview - Keyboard

P07002 – Two Way Communication Device

Design Review 2

Concept Overview - LCD

LCD Power Consumption


P07002 – Two Way Communication Device

Design Review 2

Concept Overview – Power Supply

150 W ATX Power Supply Specs

P07002 – Two Way Communication Device

Design Review 2

Concept Overview – SBC PCM9371

P07002 – Two Way Communication Device

Design Review 2

Concept Overview – Program Screenshot

Above is a screenshot of the program running in the Qt Developer Environment. This screenshot shows the work completed on the program to date. Zemma will give a demonstration of the GUI later in the presentation.

P07002 – Two Way Communication Device

Design Review 2

Potential Failure Modes

P07002 – Two Way Communication Device

Design Review 2

Bill of Materials


The only anticipated long lead item is the LCD screen that has an estimated time of arrival of 12/10/2006.

The budget provides $228.00 for the case of the device. Conversations with the Brinkman Lab have resulted with a fabricated case at the price of the materials required. Future discussions need to occur before any agreement is finalized.

P07002 – Two Way Communication Device

Design Review 2

Current State of Design Specs


P07002 – Two Way Communication Device

Design Review 2

Needs Assessment for Reference

Need Topic /

Need Number/Statement

Software / 1)Have an optional use for visually impaired users (larger font)
2)Database that covers all disciplines in COE
3)Internet access
4)Means to update database/software
5)Have a way to provide graphical tools to users(graphs)
Team Capability / 6)Stay within budget
7)Design output must be within programming capability of team
Portability / 8)Portable for single user to carry
Display / 9)Screen size viewable by both student and teacher
10)Rotating capability
Manual / 11)Detailed user manual with troubleshooting and FAQ section
System Specifications / 12)Have RAM/processor speeds that are adequate for project
13)Storage space to accommodate database expansion
Durability / 14)Able to resist impact
15)Able to resist liquid spills
I/O / 16)Have capability to allow user to save session for later use
Maintenance / 17)Easy to clean in order to keep in orderly condition and sanitary
18)Include carrying case
Heat Control / 19)Dissipate heat in order to prevent over-heating
Security / 20)Have theft prevention capabilities
Power / 21)Have low power consumption
22)a low power mode
23)long battery life
User-Friendly / 24)Users must be able to be trained in a short time period
25)Menus must be easy to navigate through
26)Commonly used phrases and recently used history