P16262: EV Team Motor Test Stand
/public/

Problem Definition

Table of Contents

Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use snapshots for display whenever possible so that information is easily viewable without the need to download files and open applications. Any time you post a snapshot of a document for a phase review, you should also provide a link to the live document (Your EDGE file repository should still contain original editable files).

You should use the Problem Definition Documents directory to store this information. Some templates are available there for your use.

For an first drafts of use cases and customer requirements click Falzone Draft.

All template text must be removed from this page prior to your Week 3 Problem Definition Review Link title

Team Vision for Problem Definition Phase

Summarize:

Project Summary

Problem statement goes here. Link to 1-page project summary or project charter

Use Cases

Your team will identify the different scenarios in which your project will be used. This will help inform your requirements and set bounds on specifications.

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)

Purpose

Decompose the Problem Statement into functions of elements needed to satisfy the customer.

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. Include this document in all project reviews during MSD1.
  4. Have you sought input from all the relevant stakeholders? How will you confirm this?
  5. Have you converted customer-generated solutions into needs statements?
  6. Describe why each requirement has been requested.
  7. Have you confirmed this list with your customer?
  8. Customer requirements often evolve over the first several weeks of the MSD. Understanding the customer’s overall objective (Problem Statement) and the levels of each requirement needed to achieve that objective will help you get to a final requirements document more quickly.
  9. Functional requirements (e.g. capabilities, performance, robustness, etc.) typically denote the purpose of the project. Constraints (e.g. cost , safety, size & weight , etc.) typically denote conditions for acceptance of the solution.

http://edge.rit.edu/edge/P15001/public/MSDI/Problem%20Definition%20Documents/Edge_Pictures/P15001_Customer_Requirements.png

  1. In addition to a snapshot, include a link to the live document here
  2. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. PRP.
  2. Problem Statement.
  3. Customer Interviews. (Interview guidelines and expected outcomes are available for your reference)
  4. Customer's customer if possible.
  5. Template and Example.
  6. Guide & other stakeholders.

Outputs and Destination

A completed form matching the supplied template to be used as input to define the Engineering Requirements.

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

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. Include this document in all project reviews during MSD.
  4. The Engineering Requirements (often called Specs.) must; cover all of the Customer Requirements, be as unambiguous as possible, and be confirmed by the customer, with signature if possible.
  5. System-level and function-level engineering requirements define the intended capabilities and performance of your system. Are your engineering requirements measurable and testable? Can they all be traced back to customer requirements?
  6. Constraints are 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, for example?
Engineering Requirements Template

Engineering Requirements Template

  1. References:

https://edge.rit.edu/edge/PTemplate/public/Establish%20Engineering%20Requirements

  1. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. Customer Requirements.
  2. Customer.
  3. Selected concept list.
  4. System Design.
  5. Template and Example .
  6. Guide & other stakeholders.

Outputs and Destination

  1. Function Decomposition.
  2. Concept Generation & Development.
  3. HoQ.
  4. System & Detail Design.
  5. Test Plans.
  6. Poster & Final Report.

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, for example?

House of Quality

Purpose

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

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. This document will be inspected at all project reviews during MSD1.
  4. Array customer requirements in the first column and the Engineering Requirements across the top row.
  5. Evaluate the correlations between Customer and Engineering Requirements to ensure all of the Customer Requirements will be satisfied if the Engineering Requirements are satisfied.
  6. Evaluate the potential conflicts between the Engineering Requirements.
  7. Evaluate targets set for Engineering Requirements verses best benchmarking results.
  8. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

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.

Design Review Materials

Include links to:

Plans for next phase


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Subsystem 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