P17025: Portable Toddler Treadmill
/public/

Problem Definition

Table of Contents

Problem Definition Documents

All documents related to the problem definition phase are located here.

Team Vision for Problem Definition Phase

The team plans to define the problem and meet the deliverables presented in the problem definition.

The team has defined the problem definition and has met with the customer to go over customer requirements. From those requirements, and from the PRP, the team has defined engineering requirements. The use cases and risks were identified. benchmarking was also completed. The team has also assumed roles, such as engineering leads, project managers, communications leads and quality control and purchasing. The team has also defined its values.

Project Summary

Children with Down Syndrome typically learn to walk about year later than other children. A treadmill can be used to help these children learn to walk earlier. The child’s parent will support their body weight on the treadmill and gradually add more of their weight as they learn to walk. The treadmill will be used 5-8 minutes daily at home necessitating the need for portability and easy storage.

The goal of this project is to provide a functional prototype that is easy to use independently, cost effective, long lasting, safe for both the parent and child, and provides time, speed, and supported weight as feedback. The current commercial designs are heavier and larger than desired. Design, testing, and supply chain documentation with alternative designs will also be provided, as well as a user guide.

Use Cases

Use Case 1

Use Case 1

Use Case 2

Use Case 2

Stake Holders

Stakeholders

Stakeholders

Project Goals and Key Deliverables

Customer Requirements (Needs)

Customer Requirements

Customer Requirements

Engineering Requirements (Metrics & Specifications)

Engineering Requirements

Engineering Requirements

Constraints

House of Quality

The live document for House of Quality can be found here

Purpose

  1. Confirm that satisfaction of the Engineering Requirements implies that all of the Customer Requirements are met.
  2. Facilitate design trade off decisions

Inputs and Source

  1. Template and Example.
  2. Customer Requirements.
  3. Engineering Requirements.
  4. Benchmarking Data.

Outputs and Destination

Provide input to the risk management process.

Benchmarking

Benchmarks

Benchmarks

Risks

Risk Table

Risk Table

Design Review Materials

Problem Definition Meeting Agenda

Plans for next phase

A general overview of our future plans for the upcoming weeks:

centerr|3-Week Plan

centerr|3-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 | Integrated System Build & Test with Customer Demo | Customer Handoff & Final Project Documentation