Part 2c: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding Out about Tasks and Work Chapter 5: Requirements Gathering: Knowledge of the User Interface Design Chapter 6: Thinking about Requirements and Describing Them Chapter 7: Case Study on Requirements, Part 1 Video: Paper Prototyping

Two Types of Knowledge Needed for User Interface Design 1.Knowledge about user, tasks, domain 2.HCI concepts, principles, standards, guidelines –Cognitive psychology –Heuristics –Experience

Cognitive Psychology Memory Perception and Attention Categorization Problem-solving Language Recognition is easier than recall People see what they expect to see Easier to perceive a structured layout People have difficulty multi-tasking

Recognition & Structured Layout

Don Norman Visibility –It should be obvious what the control is used for Affordance –It should be obvious how a control is used Feedback –It should be obvious when a control is used

Requirements Functional Non-functional Data Social –Physical Environment –Context of Use –Ethical, societal, privacy, security User –Computer literacy of user –Abilities of user –Frequency of use Usability –Easy to learn –Easy to remember –Pleasing to the eye