P17363: Player Piano
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

Project Summary

Mechanical player pianos have existed since the late 19th century for entertainment and teaching purposes, with the innovation of the electric player piano debuting in the 20th century. Both, unfortunately, have a distinct ineptitude interacting with a human performer. Some costly programs exist today that allows for the performer to play one of the two clefs but the temp is set and determined by a defined beat per minute value beforehand.

The goals of this project are to retrofit a modern acoustic piano to act as a player piano with the added capability of performing a duet with a human performer who is setting the tempo. Storing songs, transferring data, and an intuitive user interface will also be added challenges to this project. The expected result is a marketable prototype that can be installed in a modern standard piano for the purposes as a teaching aid, entertainment, and to allow handicapped pianist play pieces they once thought impossible.

Use Cases

Benchmarking

Devices on the market that we can compare to our design.

Above products lack duet abilities, require smart devices, don’t control foot pedals, and can’t provide accessibility technology which are all goals for our device.

Project Goals and Key Deliverables

Expected end result of the project, what the customer can expect to receive at the end of the project.

Customer Requirements (Needs)

https://edge.rit.edu/edge/P17363/public/Problem%20Definition%20Documents/Customer%20Requirments%20Rev2.PNG

Link to Excel File

Engineering Requirements (Metrics & Specifications)

Engineering Requirements

Engineering Requirements

Link to Excel File

Constraints

Project Plan

Project Plan

Project Plan

Link to Excel File

Risks

Risks and Management

Risks and Management

Link to Excel File

House of Quality

House of Quality

House of Quality

Outputs and Destination

Provide input to the risk management process. This table highlights the give and take of certain requirements with others. For example how keeping costs down is at odds with number of keys automated, because the more keys we automate the more the system will cost.

Design Review Materials

Customer Requirements File

Group Plans for next phase

In 3 weeks time we expect as a team to be able to deliver in our review:

Individual Plans


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