Project Readiness Package
Rev 5/21/12
ADMINISTRATIVE INFORMATION:

Project Name (tentative):

Project Number, if known:

Preferred Start/End term in Senior Design:
Fall/Spring
Spring/Fall

Faculty Champion: (technical mentor: supports proposal development, anticipated technical mentor during project
Project Name Goes Here
Pxxxxx
execution; may also be Sponsor)
Name

Dept.
Email
Phone
Other Support, if known: (faculty or others willing to provide expertise in areas outside the domain of the Faculty
Champion)
Name
Dept.
Email
Phone

Project “Guide” if known (deals with day-to-day project execution; may be assigned by the senior design program):
Name
Dept.
Email
Phone

Primary Customer, if known (name, phone, email): (actual or representative user of project output; articulates
needs/requirements)
Name

Dept.
Email
Sponsor(s): (provider(s) of financial support)
Name/Organization
Contact Info.
Page 1 of 5
Phone
Type & Amount of Support Committed
Project Readiness Package
Rev 5/21/12
PROJECT OVERVIEW:
Explain the overarching goals of this design project. What engineering principle(s) do you hope to
demonstrate, which courses will be using the hardware, and how do you envision future students
interacting with the hardware (observing a phenomenon, controlling experimental variables, collecting
data, making qualitative observations, etc.)? What can the design team expect to learn about the topic
after completing this project?
BACKGROUND:
First, explain the motivation for this project. Is it student-initiated, where a student selected a topic from a
prior class where he or she felt that a hands-on experience would have helped them to understand the
material more easily? Is it instructor-initiated, where an instructor has repeatedly encountered student
confusion and would like something more concrete to illustrate a particular point? Why did someone feel
that this project would be useful?
Next, include any benchmark lab hardware that the design team should investigate, along any particularly
relevant analysis models the design team should investigate and understand.
DETAILED PROJECT DESCRIPTION:

Customer Requirements (add/delete/edit as needed):
Customer Requirement
Category
1. Hardware
Functionality
CR #
1.1
Description
List needs related to the specific demo/experiment.
1.3
1.4
Example: Illustrate the difference between high and low
cycle fatigue
Example: Shows both laminar and turbulent flow
Example: Allows user to vary temperature
2. Usability
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
Continues to operate after light misuse or transportation
Easy to set up
Operates without needing repair
Stays clean/easy to clean
Easy to use controls interface
Easy to move between classroom/lab/storage area
Easy to store in between uses
Low recurring costs
3. Educational Value
3.1
3.2
Clearly demonstrates [one or more specific principles]
Students can observe the demo/experiment
1.2
Page 2 of 5
Importance
Project Readiness Package
Rev 5/21/12
Functional Decomposition: This should focus primarily on the functionality of the demo/experiment. See
below, for example.
Test
Specimen
Engineering/Functional Requirements: Examples related to above functional decomposition
ER#
Source
ER1
CR6, CR9
ER2
ER3
ER4
ER5
CR5, CR7,
CR14
CR1,
CR14
CR1,
CR14
CR10
Unit of
Measure
Metric
Can user see flow over test specimen
(Y/N)
Flow measurement accurate to XX ft/s
Page 3 of 5
Ideal Value
Y/N
ft/s
Allows user to input speed (Y/N)
Allows user to turn on and off system
(Y/N)
Test reaches steady state in less than XX
minutes
Min/Max
Value
min
0.05 ft/s
.025 ft/s
Y/N
Y/N
Y/N
Y/N
1 min
0.5 min
Project Readiness Package
Rev 5/21/12
Constraints (add/delete/edit as needed)::
o Storage size of n x n x n ft3 or less
o Can be transported on department rolling cart by n people
o Provide demo/experiment for class/lab/group size of n students
o Demo/experiment can be completed in time period, including setup time
o Per-use cost less than $n

Project Deliverables (add/delete/edit as needed)::
o Functioning demo/experiment unit(s), number to be agreed on at the start of MSD.
o User’s Manual, instructions
o Electronic copies of any handouts required for the demo/experiment
o Complete BOM, including suppliers for consumable items

Budget Estimate:
o Total budget estimate
o Highest-cost items

Intellectual Property (IP) considerations:

Follow on project possibilities:
o List opportunities for additional projects that could build on the hardware outlined here
STUDENT STAFFING:

Anticipated Staffing Levels by Discipline:
Engineering
Discipline
How
Many?
Anticipated Skills Needed
Computer
Electrical
Industrial &
Systems
Mechanical
Page 4 of 5
Project Readiness Package
Rev 5/21/12
OTHER RESOURCES ANTICIPATED:
Category
Resource
Available?
Description
Faculty
Environment
Equipment
Materials
Other
Prepared by:
Date:
Page 5 of 5