Exam 1
Exam Format
The exam will be on Moodle. You must be IN CLASS to take the exam, and must show me you have submitted the exam in Moodle BEFORE you leave class. Moodle will be the ONLY tab you have open and full screen at all times. Switching application may result in failing the exam.
MAKE SURE YOUR LAPTOP IS CHARGED, WORKING, AND WON’T START AND UPDATE DURING THE EXAM! If you need and to use a power adapter, have it out and sit near a wall/floor outlet.
Question Types and Point Distributions
25 Questions - 60 total points
- 7 Short answer - 27 total points (45%)
- Six questions are limited to 10 lines of input
- Most questions request no more than 4 sentences for an answer
- One question is applied knowledge and may requres >=6 sentences
- Rambling or vague answers will not receive full credit
- 2 Matching Questions - 15 total points (25%)
- 10 Multiple Choice - 12 total points (20%))
- 6 True/False - 6 total points (10%)
Exam Content
Majority of the content comes from The Design of Everyday Things Book (DOET) unless otherwise noted. You will not be asked questions from the “User Stories and Tasks” or “Needfinding” slides.
Topics may include…
- Process(es) for finding the right problem
- What is activity-centered design?
- Advantages/Disadvantages
- How/Why do accidents happen?
- What is the model we use for accidents and it’s meanining/purpose?
- Method of Error Reduction
- The Legacy Problem
- What is it?
- Challenges it poses to design.
- How can we overcome or mitigate it?
- Slips vs. Mistakes
- YOU DO NOT NEED TO MEMORIZE ALL THE DIFFERENT TYPES AND SUBTYPES
- The Stages of Action
- The Chapter 1 terminology
- Discoverability
- Affordances / Anti-Affordances
- Human-Centered Design
- Signifiers / Perceived Affordances
- Constraints
- Know the categories and implications
- Forcing Functions
- Mapping
- System Image
- Conceptual Model
- Feedback
- etc.
- Three levels of processing
- What are they?
- Level of consciousness they operate
- Memory
- Short term
- Long term
- Procedural
- Declarative
- Concepts and Complexity (GUI Bloopers)