Interaction Design Chapter 9 notes <ul><li>http://www.id-book.com/chapter_index.htm # </li></ul><ul><li>focus on users and...
 
<ul><li>design fundamental activities </li></ul><ul><li>understanding the requirements </li></ul><ul><li>produce a design ...
importance of involving users <ul><li>importance of involving users not proxy users early and throughout expectation manag...
user centred approach <ul><li>user centred approach real users and goals early focus on users and tasks - itentify real us...
<ul><li>needs – requirements what trying to achieve how they currently achieve how to improve experiences and expectations...
Structure <ul><li>What?  (and how do you know...) </li></ul><ul><li>Questionnaires, focus groups, interviews, observation,...
 
 
lifecycle models <ul><li>aim to be able to react to change quickly and embed principles of iteration communication and fee...
Agile <ul><li>eXtreme programming, ASD, Scrum </li></ul><ul><li>early and continuous delivery of valuable sw demanding cus...
agilemanifesto.org <ul><li>better ways of developing sw by doing it and helping others do it </li></ul><ul><li>individuals...
Upcoming SlideShare
Loading in...5
×

Interaction Design ch9 notes

1,706

Published on

Cues to remember Chapter 9 of Interaction Design

Published in: Design
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,706
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Interaction Design ch9 notes

  1. 1. Interaction Design Chapter 9 notes <ul><li>http://www.id-book.com/chapter_index.htm # </li></ul><ul><li>focus on users and their goals </li></ul><ul><li>4 basic activities of interaction design identifying needs and establishing requirements for user experience who - user and what – requirements data gathering and analysis developing alternative designs that meet requirements conceptual design physical design building interactive versions of the designs paper based simulated prototypes evaluate what is built throughout and the user experience it offers usability and acceptability how easy to use how error prone how fulfills requirements fit for purpose </li></ul>
  2. 3. <ul><li>design fundamental activities </li></ul><ul><li>understanding the requirements </li></ul><ul><li>produce a design that satisfies requirements </li></ul><ul><li>evaluating the design </li></ul><ul><li>produce a version of design users can interact with </li></ul><ul><li>capture design in form can be communicated to user - review revision improvement sketches natural language prototypes </li></ul><ul><li>Stages requirements design a solution produce interactive proto evaluate </li></ul><ul><li>generate alternatives brainstorm sharpen the focus playful rules get physical </li></ul><ul><li>the value of prototyping define requirements design refine evaluate </li></ul>
  3. 4. importance of involving users <ul><li>importance of involving users not proxy users early and throughout expectation management - realistic less likely to be disappointed ownership training </li></ul><ul><li>level of user involvement best throughout important for input loose touch with user base without touch cycle different users design workshops evaluation sessions data gathering generating ownership </li></ul><ul><li>activity based planning - microsoft </li></ul>
  4. 5. user centred approach <ul><li>user centred approach real users and goals early focus on users and tasks - itentify real users requirements tasks and goals driving force not technology behaviour and context of use studied - how user works characteristics - of user and work environment consulted throughout process and responses acted on respected design decisions in context of user empirical measurement - observe users reactions to design usability and user experience goals iterative design - fix problems and refine early cycles of design test measure redesign innovation takes time,evolution trial and error and patience Design interaction around what people want and need Do not force users to change to accommodate system </li></ul><ul><li>users and stakeholders who should be involved and to what degree primary - hands on users of system secondary - occasional system users or through intermediary tertiary - affected by intro of system or who influeence purchase </li></ul>
  5. 6. <ul><li>needs – requirements what trying to achieve how they currently achieve how to improve experiences and expectations </li></ul><ul><li>alternative designs - internal and external cross-fertilisations evolution copying experience balancing constraints quality </li></ul><ul><li>usability goals effectiveness efficiency safety utility learnability memorability </li></ul><ul><li>user experience satisfying enjoyable motivating rewarding aesthetics </li></ul>
  6. 7. Structure <ul><li>What? (and how do you know...) </li></ul><ul><li>Questionnaires, focus groups, interviews, observation, .... </li></ul><ul><li>Use cases, task analysis, scenarios, user profiles, ... </li></ul><ul><li>How? </li></ul><ul><li>Sketches, wireframes, card sorting, storyboards, </li></ul><ul><li>prototyping, information architecture, navigation scheme, </li></ul><ul><li>input/output devices, ... </li></ul><ul><li>Whether? </li></ul><ul><li>White/black box testing, system testing, usability testing, </li></ul>
  7. 10. lifecycle models <ul><li>aim to be able to react to change quickly and embed principles of iteration communication and feedback </li></ul><ul><li>set of activities and how related </li></ul><ul><li>when and how to move from 1 activity to next and deliverables </li></ul><ul><li>overall view of development </li></ul><ul><li>stable framework for creativity </li></ul><ul><li>sync and stabilise – microsoft planning phase vision statement specification document schedule and feature team formation development phase 3 or 4 subprojects each has milestone release stabilisation phase internal test external test release prep - golden masters </li></ul>
  8. 11. Agile <ul><li>eXtreme programming, ASD, Scrum </li></ul><ul><li>early and continuous delivery of valuable sw demanding customer input often </li></ul><ul><li>handle emergent requirements </li></ul><ul><li>balance between flexibility and structure </li></ul><ul><li>emphasise collaboration face-to-face communication, streamlined processes </li></ul><ul><li>avoid unnecessary activities - practice over process - getting work done </li></ul><ul><li>how much field study data is needed before product development starts </li></ul><ul><li>how much time should be spent on prototyping and getting user feedback </li></ul>
  9. 12. agilemanifesto.org <ul><li>better ways of developing sw by doing it and helping others do it </li></ul><ul><li>individuals and interactions over processes and tools </li></ul><ul><li>working sw over documentation </li></ul><ul><li>customer over contract </li></ul><ul><li>responding to change over following a plan </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×