Overall: well organized! Looks pretty comprehensive (quite impressively so!), but
always been on the look-out for requirements we have overlooked that need to be
added. 95/100
AETHSTETICS
• 75% of customers (children and
parents) must indicate that the
appearance of the fun fair game
will encourage further interest in
playing it
COST
• Fun fair game must cost less than
$100 total, which is the given
budget
• DIMENSIONS
• Dimensions must not exceed __ feet x
__ feet for the sake of storage,
transportation, and presence at
the fun fair* Must be at a height
appropriate for a kindergartener
standing 42.5” (50th percentile for
height for girls and
39.7th percentile for height for
boys) tall
• EASE OF USE
• Fun fair game must allow the average
operator to use with instructions
that can be communicated in
under two sentences.
• When provided a fifteen second
introduction to the game, 90% of
kids play the game correctly.
Must be used correctly by students of
the ages (4-10) and varying skill levels
• Must last under _ minutes to keep the
line down and move the children
through the game in a timely
fashion
• Clean up must not take more than 10
minutes
• ENERGY USE
nice
You can clarify a bit now that I have been
clearer on the budgets.
Split this out into many requirementsd.
What should dimension reqts be when set
up?
What should dimension reqts be for
storage?
Height (well researched!) is another
requirement altogether.
Great!
Awesome!
Not sure what this adds over prior one.
2 minutes seems reasonable – better at 11.5 minutes. This keeps it in-line with how
long other fun fair activities currently take.
Great to include!
• Fun fair game should not need an
outlet
• Game should be able to be powered
by a standard battery
ENVIRONMENT
• Fun fair game must be durable to
withstand unpredictable spring
weather, such as rain and fog,
without electrical or mechanical
failure
• Fun fair game must run at
temperatures between 40 and 90
degrees fahrenheit and humidity
between 50% and 100%
• MAINTENANCE
•
Game must require no maintenance on
the day of the fun fair by operators or
any other volunteers
• Game must not require batteries to be
changed on the day of the fun
fair
• NOISE LEVEL
• Must play music/mp3 loud enough for
everyone within a _ foot radius to
hear.
SAFETY
•
• Must not pose any bodily harm to
participants or operator Should
not have any small spaces that
could pinch participant/operator
• Should not be able to splinter in any
way
Should have no risk of electrical shock
• Should pose no risk of falling on
someone/no temptation for
children to climb on
• Should not contain any toxic materials
that could cause harm for
participants or operators
SCHEDULE
Yes!
Not by “a standard battery” necessarily, but
by “standard batteries.”
ok
good
good
good
Split into two; first one is more vague…
Great!!!!!
•
• Game must be feasible to be
designed and constructed so
that: a prototype is completed
and ready for presentation by the
November design review
the preliminary version of the game is
finished before Thanksgiving Break
(November 26, 2014)
• the final version of the game is
finished before the day of final
testing (December 11, 2014)
• WEIGHT
• Game must be easily carried by one
person
• FUN FOR KIDS
• 90% of participants (kids) must
indicate they had fun playing the
Music Maker (as shown by
questions on survey given after
the fun fair)
Must use sensors in the game design
• Must not infringe on copy rights
ENGAGEMENT
Must require action by the user at least
every 15 seconds
100% of participants at the end of the
fun fair must indicate they remember
playing the Music Maker
Actually, by December 5. I want y’all to
finish it by then so you won’t be working
on it while you are doing other finals.
Ok.
good

Functions
For Running the Game:
• Play sound/music
• Guide players through music/alert when action is needed
• Detect contact
• Determine if contact is correct
• Respond accordingly to contact
• Provide structure on which the game will be played
For Logistics of Fun Fair Activity:
• Provide operators with an easy, safe, entertaining method for running the
game
• Include reset ability
• Transport and store easily
Optional/Secondary Functional Requirements:
• Appear aesthetically appealing
• Adjust to the different ability levels of the children
Blue ones aren’t as strong. First set “for running the game” are great!
Provide operators  I don’t see this as a function
Include reset ability  “allow operator to reset”
Transport…  not a function of your design
Appear aesthetically  not really a function… more about”form”
Adjust to the different…  may want “allow operator to adjust to different ability
levels” (this might be an optional function that you may/may not do)
Also, what about:
Allow operator/user to select song