Week03 user, designer, and user designer


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Week03 user, designer, and user designer

  1. 1. User, Designer, and User Designer<br />IA4340-1[Tue 1,2,3]D121<br />IA4340-2[Tue 5,6,7]D325<br />Visual Design/2011 Fall Semester<br />UI Design/ Week 03<br />
  2. 2. 진행<br />Week 03 수업<br />Newman, W.M., & Lamming, M.G. (1995). Interactive System Design. Reading, Massachussets: Addison-Wesley Publishing Company., Part III System Design<br />http://books.google.com/books/about/Interactive_system_design.html?id=bOdQAAAAMAAJ<br />User Study Methods<br />System Analysis and Design<br />Requirement Definition<br />2<br />
  3. 3. What is Design?<br />Herb Simon:Everyone designs who devises courses of action aimed at changing existing situations into preferred ones.<br />Designing material artefacts is like<br />Prescribing remedies to a sick patient<br />Devising a new sales plan for a company<br />Finding one’s way around a traffic jam…<br />3<br />
  4. 4. Defining the Problem: Overview<br />Goal : ensure we know how to specify the design problem at the outset.<br />Issues:<br />What aspects do we need to define?<br />What if we don’t know all of them?<br />Specifying the user’s needs.<br />4<br />
  5. 5. What do we need to define in order to start designing?<br />a form of solution;<br />the intended users;<br />a context in which the system will be used;<br />an activity, performed by the users, that the system will support;<br />a target performance for the activity.<br />5<br />
  6. 6. How to state all of these in one sentence<br />Design a <form of solution>to enable <users>in <context>to <perform activity>in/with <target performance><br />Example:<br /> Design a ticket machine to enable travelers at a railway station to purchase a ticket in less time than at present.<br />
  7. 7. Arriving at the problem statement<br />We discover the components by degrees<br />Suppose we find we don’t know…<br />The user?<br />The context?<br />The activity?<br />The target performance?<br />These questions force us to think.<br />7<br />
  8. 8. User Study<br />To design an effective interactive system, we must identify the people it is to support –the users- and gain some familiarity with their activities.<br />User-Centered approach to design<br />Be based on real data, not imagination<br />User studies<br />Building and understanding of users and their activities.<br />We observe them at work, we interview them, we get them to fill in questionnaires, we may collect examples of the materials they work with.<br />8<br />
  9. 9. User Study Methods<br />When do we conduct user studies?<br />To define the problem<br />Support of evaluation<br />How do we ensure quality?<br />To plan the studies carefully and to use reliable methods<br />Data Collection Methods<br />Interviews, Observation and user of questionnaires<br />9<br />
  10. 10. Interviews<br />Basic Methods : Structured, Unstructured<br />The interview’s purpose<br />Enumerating activities<br />Work methods<br />Tracing interconnections<br />Performance issues<br />Effective interviews<br />Following up on exceptions<br />Knowledge of the domain<br />Recording the interview<br />10<br />
  11. 11. Observation<br />Video recording<br />Concurrent verbal accounts<br />Passive observation<br />Cf. action research<br />Ethnographic field study<br />Action research<br />Methods of studying activities by taking part in them.<br />11<br />
  12. 12. Questionnaires<br />Questionnaire design issues<br />The need to make things easy for the subject<br />The need for unambiguous questions<br />The need to gather precise data<br />The need to support the intended analysis<br />Questionnaires by electronic mail<br />Subjects’ time and attention<br />Making it easy to reply<br />Lack of subject anonymity<br />12<br />
  13. 13. User-participative methods<br />Selection of participants<br />User members of the team should be representative of the whole user community<br />Training<br />An informal workshop, with talks and discussions on a range of topics surrounding the subject matter of design<br />Facilitation<br />Tools and techniques<br />Modeling <br />Scenario<br />Envisionments, Simulation<br />Analysis is conducted by all members of the team : users analyse scenario and solutions in terms of their own experience, while other may apply more formal techniques such task analysis.<br />13<br />
  14. 14. What is Ethnography?<br />Fieldwork methods for the study and analysis of social settings<br />Draws on methods used in studies of primates and primitive tribes<br />A research activity, increasing our knowledge of the social world<br />Links with philosophy rather than scientific theory.<br />14<br />
  15. 15. EMy’s limitations<br />Looks at fine detail -- influences only the file detail (UI) of design<br />Invalidity of generalizing about social action<br />Generalizing therefore falls on the designer<br />EMists don’t build on each others’ work -- they prefer to demolish it!<br />So there’s work to be done. <br />
  16. 16. Ethnographic study methods<br />Direct observation<br />Interview<br />Video and/or audio recording<br />Diary-keeping<br />Also: participation and action research<br />16<br />
  17. 17. Informing design<br />The ‘correct’ approach:<br />Ethnographer conducts studies<br />Ethnographer relates findings to designers<br />Designers come back with questions<br />Ethnographer does further studies, etc.<br />The field usability testing approach:<br />Ship the product or prototype<br />Find a study site<br />Gather data about design faults, report back<br />Can we do better?<br />The diary study option.<br />17<br />
  18. 18. Individual Homework<br />3 mins about “me and my fun”<br />Self interview recording<br />“Who I am, essentially positive ” and “what makes me feel fun or excited”<br />Place, moment, experience, person, objects, etc.<br />Upload on a Vimeo profile page<br />On description<br />A/B반, 학번, 전공, 이름, 소속팀 <vimeo group link><br />Copy the interview protocol<br />Due : 10월 2일 일요일 자정<br />18<br />
  19. 19. Team Submission<br />Team project proposal<br />30 seconds Animation/Motion graphics about the product<br />On description<br />Title<br />Design statements<br />The user?<br />The context?<br />The activity?<br />The target performance?<br />Participative Design Team Plan<br />Due : 10월 2일 일요일 자정<br />19<br />
  20. 20. Team Submission<br />Recommendation Factors<br />Social Networking Service<br />SmartPhone/iPad/Galaxy Tab Related Apps, <br />LBS/GPS<br />AR/HUD<br />20<br />
  21. 21. Microsoft Vision 2019<br />21<br />