Problem Statement
The problem statement should be a concise description of the design problem and its context. Be sure to include only the functional requirements of the device and not components of the solution.
The aim of problem definition is:
to clearly define the problem for the team to focus on.
to publicize what the team is working on.
What to do:
be sure that the problem defined is measurable and observable.
address the questions of:
who (the user),
what (the functionality of the device),
where (the environment),
how much (the cost).
quantify the problem with facts and numbers where possible.
What not to do:
do not state the problem as a question.
do no give a solution or cause of the problem in the statement.
do not address why or how.
This page is maintained by Amy Smith,
mmadinot@mit.edu