HCI in the life cycle

1
HCI in the life cycle

• Motivating the class project

2
Agenda

• Questions
• about GVU (Brown Bag)
• SE Life Cycles
• Where do HCI techniques fit in?
• Project info

3
Software Life cycles

• Waterfall

4
Why waterfall fails

• Historical roots
• Batch fallacy

5
The Solution

• Building a system as a means of understanding
  requirements
• Iteration
• Prototyping
• Incorporate evaluation

6
Prototyping

• better understand user requirements through
  exposure to system
• Not (necessarily) your final system
• Authenticity of prototype important

7
Ways of prototyping

• Storyboards
• Limited function

8
Project info

• Group project throughout quarter
• teams of 4
• decide on team composition yourself
• inform TA of teams by August 31
• create Web site (see examples)
• Variety on team is good

9
Grading

• Project counts for 50 of grade
• 5 parts
• Part 0 - 0 (team formation)
• Part 1 - 12.5 (problem exploration)
• Part 2 - 12.5 (design alternatives)
• Part 3 - 12.5 (prototype / eval plan)
• Part 4 - 12.5 (evaluation execution)

10
Regrade policy

• Parts 1-3 only
• Version 1
• graded by instructor
• Version 2
• resubmitted within one week
• regraded by TA
• Final grade is weighted average.

11
Deliverables

• Part 0 team/project selection
• identify team
• create Web project notebook
• Part 1 Understanding the problem
• describe users, tasks, environment

12
Deliverables (contd)

• Part 2 Design alternatives
• storyboard designs for at least 3 different
  solutions
• Part 3 Prototype evaluation plan
• detailed (preferably functional) prototype
• variety of evaluation exercises aimed to validate
  usability criteria

13
Deliverables (contd)

• Part 4 Evaluation
• results of evaluation against design criteria
• Written plus Presentation

14
Presentations

• Informal poster sessions
• whole class period
• prior to due dates for Parts 1 2
• contributes to Parts 1 2 grade
• students and expert gallery
• Formal project presentation
• final week of semester

15
Project themes

• Think off the desktop!
• Mobility, handheld, environmental
• Think everyday
• Home, Car, Office, Campus, Body

16
What I will provide

• necessary equipment
• hardware
• development software
• pointers to expertise
• Just ask me!

17
Programming requirements

• Leverage team expertise
• Full functionality is NOT intention
• But good evaluation requires authentic experience