1 / 22

SE 204, IES 506 – Human Computer Interaction

SE 204, IES 506 – Human Computer Interaction. Lecture 5: Class Practice on the Design Process Lecturer: Gazihan Alankuş. Please look at the end of the presentation for assignments (marked with TODO ). Outline. Announcements Weekly show and tell about interfaces that you use

miriam
Télécharger la présentation

SE 204, IES 506 – Human Computer Interaction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SE 204, IES 506 – Human Computer Interaction Lecture 5: Class Practice on the Design Process Lecturer: GazihanAlankuş Please look at the end of the presentation for assignments (marked with TODO)

  2. Outline • Announcements • Weekly show and tell about interfaces that you use • Talking about homework • Class practice on requirements & prototypes

  3. Announcements (in TODO @ end, too) • Midterm exam: • 9 April 2012, in class • 4:30 - 6:30 • Locations: to be announced • Don’t be fooled by the syllabus on ECTS… • Questions will be about things that we learned here. • Not memorization • Concepts • Both SE 204 and IES 506

  4. Announcements (in TODO @ end, too) • Staring paper summaries for IES 506 students • Homework about improving your paper prototypes

  5. Show and Tell • What good/bad interfaces have you seen lately?

  6. Homework • Identified requirements • How did you do it? • Created a paper prototype to address those requirements

  7. Homework • Identified requirements • How did you do it? • Created a paper prototype to address those requirements

  8. Collecting Requirements • So, how did you do it? • NO COMMENT! • I thought this is necessary • Identified users • Imagined what they would need • “for my application i think myself like guest and i make what i want to see in that application” • Said “we need to talk to users” but didn’t do it • Assumed that users would be students (VISITORS!) • Looked at other mobile applications • Looked at university web page

  9. Collecting Requirements • Nice! Some people actually asked potential users! • Ece • Seçil • Melda • And some other people asked their friends • However, no real ethnographic observation

  10. A sample iteration to start collecting requirements We don’t know much, yet. Maybe we should observe them while they are in the tasks These must be the users These seem to be the tasks IDEAS If our software did this, it would help them! LEARN BUILD Create an environment to put users in this situation There is a problemthat needs to be solved with software DATA CODE We saw that this and thathappens during the task MEASURE Use the situation to learn what is going on Observe Ask questions

  11. A sample iteration to start collecting requirements We don’t know much, yet. Maybe we should observe them while they are in the tasks These must be the users These seem to be the tasks IDEAS If our software did this, it would help them! LEARN BUILD Create an environment to put users in this situation There is a problemthat needs to be solved with software DATA CODE We saw that this and thathappens during the task Ethnographic Observation: MEASURE Use the situation to learn what is going on Observe Ask questions

  12. Ethnographic Observation • Get somebody from outside to actually visit our campus • Walk around with him/her • Observe • Interview

  13. Creating the Design • Hypotheses based on requirements • Use guidelines document

  14. Today we will practice in class! • Fake ethnographic observation • Volunteers needed to act like visitors to our campus • We will theatrically perform a visit to the campus, accompanied by a user interface designer • Observe • We will conduct interviews

  15. Volunteers • Anyone good at acting? • Volunteers for • Users (visitors) • Designers • Users • I will tell you who you will pretend to be • Designers • You will accompany them in their visit and learn about how a mobile application could help them

  16. Other people • Everybody will take notes • You will get to ask questions to the users • Write down requirements that you identify • I will randomly choose three people that will design prototypes on the board • We will evaluate them later

  17. Let the acting begin!

  18. I hope this was good exercise • Requirements for the application is just the first step • Designing the interface and making it intuitive is next

  19. What’s left? (next week) IDEAS LEARN BUILD DATA CODE MEASURE

  20. TODO: Homework due next week • Create another prototype, with actual ethnographic observation • Remember our iterative loop! • Bring a guest to IEU! • Observe what they want to find/do/see • Interview them • (optionally) participatory design • Form hypotheses based on your observations, make the prototype(s) accordingly

  21. TODO: Homework for IES 506 only, due two weeks from now • Find 1-3 scientific paper(s) that are the most relevant to your project • If I find one that is more relevant, I will deduct %30! You will have a chance to defend yourself. • Summarize the main points in at most a page for each paper • Send me weekly reports about your projects

  22. TODO: Prepare for the midterm • Mark your calendars for the midterm exam • 9 April, 4:30 – 6:30 • Location: to be announced

More Related