P20225: Doc B Racing Real Time Telemetry
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

Since the problem definition for this project hasn't changed, the main plan for the group was to build on the definition based on where the last team finished their work and come to a consensus on what we felt was a reasonable summary of the work that lays ahead of us. In addition, the team went over the project goals and key deliverables to put forth an action plan. From this action plan and the information in the PRP the team then developed the list of customer and engineering requirements.

Project Summary

The Doc B Racing Real-time Telemetry System is an end-to-end system for data acquisition in the vehicle environment. The system will use a host of sensors and an onboard processor to log useful vehicle data metrics during a street or track driving event. This data is then made available to the user for review on a laptop or mobile device with intent to aid in vehicle setup, driver performance, and general maintenance. Link to full one-page project summary.

Use Cases

Below is the use cases diagram. The first use case describes the setup routine for the operator, or pit crew member, for placing the device in the car and setting up the calibration. The second and third use cases are for during and after the race, depending on how the data wants to be displayed and analyzed.
Use Case for operator setup and calibration.

Use Case for operator setup and calibration.

Use Case for driver saving data on SD card.

Use Case for driver saving data on SD card.

Use Case for driver sending data over Wi-Fi and saving on SD card.

Use Case for driver sending data over Wi-Fi and saving on SD card.

Project Goals and Key Deliverables

The main project goals are to complete a marketable product that has the ability to acquire data from the car and integrate with the customers needs. Also, to build on the previous team's work and finish embedded system and sensor integration. Some additional Key Deleverables would be to participate in Imagine RIT in the spring, finish a poster and technical paper, and test in race car under real race conditions.

Customer Requirements (Needs)

https://edge.rit.edu/edge/P20225/public/Photo%20Gallery/customer%20requirements%209_10_19.PNG

  1. A working document can be found here

Engineering Requirements (Metrics & Specifications)

Purpose

Create a contract between the engineer and the customer where indisputable satisfaction of the engineering requirements equates to customer satisfaction

https://edge.rit.edu/edge/P20225/public/Photo%20Gallery/ER_Edge.png

  1. A working document can be found here

Constraints

Factors, usually system-level, that limit your design space (e.g., cost, total weight, total footprint, total power available). Are your constraints measurable and testable, and can they be traced back to customer requirements? Have you considered economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability constraints and engineering standards, for example?

House of Quality

House of Quality - Doc B Racing Telemetry - P20225 .

House of Quality - Doc B Racing Telemetry - P20225 .

  1. A working document can be found here

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


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