Design in HCI It is a process: a goal-directed problem solving activity informed by intended use, target domain, materials, cost, and likelihood a creative activity a decision-making activity to balance trade-offs
Question 10 List the Interaction Design activities
Interaction Design activities 1. Identifying needs and creating requirements 2. Developing alternative designs 3. Building interactive versions of the designs like a prototype 4. Evaluating designs
USERs/STAKHOLDERs 1. those who interact directly with the product 2. those who manage direct users 3. those who receive output from the product 4. those who make the purchasing decision 5. those who use competitor’s products
User’s Needs Look at existing tasks: 1. their context, eg. background, situation, … 2. what information do they require? 3. who collaborates to achieve the task? 4. why is the task achieved the way it is?
Question 26 What’s the difference between requirements and design
Answer 25 RequirementsDesign Statements of what the system should do (or what qualities it should have) A description of how we will implement a solution
Question 26 What’s the difference between verification and validation
Verification and Validation VerificationValidation designing the product right designing the right product
Question 26 What are the Flaws (FAULTS) of the Waterfall
Flaws (FAULTS) of the Waterfall Need iteration and feedback Inflexible Doesn’t emphasis risk, quality, and prototyping
Question 26 What’s the advantage of spiral model over waterfall model
Spiral Model Spiral model emphasize the following: Risk analysis Prototyping Iterative framework allowing ideas to be checked and evaluated
Question 27 What are the techniques used for prototyping?
Techniques for Prototyping Storyboards need not be computer-based can be animated Limited functionality simulations some part of system functionality provided by designers Warning about iterative design design inactivity – early bad decisions stay bad diagnosing real usability problems in prototypes….
Question 28 What is the definition of Design Rationale
Design Rationale Design Rationale is information that explains why a computer system is the way it is.
Question 29 Design for usability goal is to know how easy is the design for people to use, learn to use, recall how to use the system
Usability Objectives 1. Identify Usability and User Experience goals. 2. Apply usability rules and guidelines for designing human-computer interaction. 3. Discuss the advantages and disadvantages and design considerations of four types of user interaction mechanism: menus, form fill- in, command language, and direct manipulation.
Question 31 What are the principles of usability
Principles of Usability Learnability Flexibility Robustness
Question 32 What are the principles of learnability?