P18047: Virtual Cane
/public/

Systems Design

Table of Contents

This page documents the process the team went through to accomplish a System Design. All sections on the EDGE were organized for ease of read. At the end of each section, a PDF version of each document is linked at the end.

In addition, links to the actual documents for each section can be found here Systems Level Design Documents

Team Vision for System-Level Design Phase

System Design Team Pre-Plan:


Team Plan For the System Design Phase:

Phase 2 Plan

Phase 2 Plan

Functional Decomposition

Functional Analysis

Functional Analysis

Benchmarking

Benchmarking

Benchmarking

Concept Development

Concept Development Chart

Concept Development Chart

Concept Selection

Concept Selection Criteria:


Concept Selection Process:

Concept Selection

Concept Selection

Feasibility: Prototyping, Analysis, Simulation

Analysis : Individual Members' Feasibility Questions:

1- What are we expecting from the device in terms of

2- Can 3D audio be used to accurately pinpoint an angular offset to a point?

3- Is using bone conduction audio feasible if the root audio will be superimposed by surrounding sounds?

4- Is picture distance enough to compare reference points ?

5- Can the device store all reference points or have easy access to images of the reference points?

6- Is it comfortable for the user to control the device with buttons?

7- Would the device easily fall off the user’s face/head since VIP are known to move their head to gauge orientation position as a reactionary nature?

Assumptions:

1- RaspberryPi Used

2- RaspberryPi Camera Used

3- Wearable Device

Means of Answering Feasibility Questions:

1: Device expectations can be assessed for various applications through the following approaches:

2: Prototyping a device that will output 3D audio (with a static reference point of “0 degrees”) to two earbuds / Stereo headphones will demonstrate how distinguishable and understandable 3D audio can be.

3: Prototyping bone conduction while testing superimposed surrounding audio will provide a good understanding of this function’s feasibility.

4: Picture distance question is best answered by analysis and prototyping. Look for studies where picture matching has been performed

5: To determine the answer to this question: one must know how big a picture is (typically in megapixels) and how much storage space that will consume. Then, it must be determined how much storage space is on the device after the final code and other necessary peripherals are loaded.

6: Will be comfortable to use as long as button has sufficient structural integrity behind it. The volume-control slider will be as usable as a hearing aide..

7: One solution to test feasibility for stability on the user's body is to run multiple iterations of a brute force test on the user. Additionally, having an elastic rope to hold it in would solve the problem as well.

Morphological Chart

Morph Chart

Morph Chart

Customer and Engineering Requirements

Customer Requirements

Customer Requirements

Engineering Requirements

Engineering Requirements

Systems Architecture

System Architecture:

Overall System Architecture

Overall System Architecture

System Architecture Mapping:

System Architecture Mapping

System Architecture Mapping

Designs and Flowcharts

System Architecture Input Stage:

Input Stage

Input Stage

System Architecture Processing Stage:

Processing Stage

Processing Stage

System Architecture Output Stage:

Output Stage

Output Stage

Risk Assessment

Risk Assessment

Risk Assessment

Design Review Materials

Include links to:

It is appropriate for you to send your customer and guide a link to this page in preparation for the review. This will ensure that they know what you will be presenting and how to view all of your work. Any EDGE link should start with http://edge.rit.edu/edge/P1xxxx..... Using "http" instead of "https" will ensure that non-RIT stakeholders can view the content without being prompted for a DCE login and password.

Plans for next phase

Team Plan For Phase III:

Team Phase III Plan

Team Phase III Plan


Individual 3-week plan:

Name Role Individual 3-Week Plan
Deepti Chintalapudi Project Manager Phase(I) Three-Week-Plan
Suhail Prasathong Team Lead Phase(I) Three-Week-Plan
AbdulAziz Alorifi Team Facilitator Phase(I) Three-Week-Plan
Josh Drezner Purchasing Phase(I) Three-Week-Plan
Stuart Burtner Engineer Phase(I) Three-Week-Plan
Eronmonsele Omiyi (EJ) Engineer Phase(I) Three-Week-Plan

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation