se 204, ies 506 – human computer interaction lecture 5: class practice on the design process...

22
SE 204, IES 506 – Human Computer Interaction Lecture 5: Class Practice on the Design Process Lecturer: Gazihan Alankuş 20.02.2012 1 e look at the end of the presentation for assignments (marked with

Upload: maude-cooper

Post on 25-Dec-2015

217 views

Category:

Documents


1 download

TRANSCRIPT

1

SE 204, IES 506 – Human Computer Interaction

Lecture 5: Class Practice on the Design Process

Lecturer: Gazihan Alankuş

20.02.2012

Please look at the end of the presentation for assignments (marked with TODO)

Outline

• Announcements• Weekly show and tell about interfaces that

you use• Talking about homework• Class practice on requirements & prototypes

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

Announcements (in TODO @ end, too)

• Staring paper summaries for IES 506 students• Homework about improving your paper

prototypes

Show and Tell

• What good/bad interfaces have you seen lately?

Homework

• Identified requirements– How did you do it?

• Created a paper prototype to address those requirements

Homework

• Identified requirements– How did you do it?

• Created a paper prototype to address those requirements

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

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

A sample iteration to start collecting requirements

IDEAS

CODEDATA

BUILDLEARN

MEASURE

There is a problemthat needs to be solved with software

These must be the usersThese seem to be the tasks

We don’t know much, yet.Maybe we should observe them while they are in the tasks

Create an environmentto put users in this situation

Use the situation to learn what is going on

ObserveAsk questions

We saw that this and thathappens during the task

If our software did this, it would help them!

A sample iteration to start collecting requirements

IDEAS

CODEDATA

BUILDLEARN

MEASURE

There is a problemthat needs to be solved with software

These must be the usersThese seem to be the tasks

We don’t know much, yet.Maybe we should observe them while they are in the tasks

Create an environmentto put users in this situation

Use the situation to learn what is going on

ObserveAsk questions

We saw that this and thathappens during the task

If our software did this, it would help them!

Ethnographic Observation:

Ethnographic Observation

• Get somebody from outside to actually visit our campus

• Walk around with him/her– Observe– Interview

Creating the Design

• Hypotheses based on requirements• Use guidelines document

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

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

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

Let the acting begin!

I hope this was good exercise

• Requirements for the application is just the first step– Designing the interface and making it intuitive is

next

What’s left? (next week)

IDEAS

CODEDATA

BUILDLEARN

MEASURE

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

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

TODO: Prepare for the midterm

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