GE 1110 Lecture Notes - Lecture 2: Information Overload, Stereotype
● Not just one representation of process
Problem Statement
● Clear and concise description of the issue that needs to be solved
○ Not multiple problem statements
○ No broad or overly ambitious problems
● Important communication tools with customer and team
● Good
○ Efforts toward a common goal
Problem Definition
● Problem statement → Identify errors, biases, implied solutions → What is the real
problem → Objective functions → New problem statement
Errors, Biases, and Implied Solutions
● Errors
○ Incorrect info
● Biases
○ Presumptions about the situation that may prove inaccurate because the client or
the users may not fully grasp the entire situation
● Implied Solutions
○ The client’s best and current guess at the answer
○ Frequently appear in the problem statement
Defining the Real Problem
● Techniques
Understanding User and Client
● User → person who will operate what is designed
● Client → hires engineer
● Engineer → hired by client
Understanding Objectives, Functions, and Constraints
● Objective → feature design should have
● Function → what device is supposed to do
● Constraint → constraint on design behaviors or attributes
New Problem Statement
● The problem is (the issue). This problem impacts (the user) and they need …
find more resources at oneclass.com
find more resources at oneclass.com