AC52013_1_Introduction 2013.ppt

8/11/2019 AC52013_1_Introduction 2013.ppt

1/49

Hum an Com puter InteractionUsability Engineering

AC52013

Dr Annalu WallerTutors: Dr Rachel Menzies & Mr Daniel Herron


2/49

School of Computing 2013

Today ...

Introduction: 9 10ish Introductions What the module is about Organisation

Introduction to Usability Engineering:10 12

Lab: 12 2


3/49


Introductions

Who am I Professor in Human Communication

TechnologiesBackground

Computer scientist, rehabilitation engineer

My research Augmentative and alternative

communication (AAC)


4/49


Introductions

Tutors

You name, home, academicbackground, course


5/49


Brainstorm: What is HCI?

CardsSwapIn pairsReport


6/49


Brainstorm: What is HCI?

Theories and MethodsEvaluationUnderstanding UsersBuilding small and large scaledemonstrators / prototypesExtending interactionEthics and implications for society


7/49 School of Computing 2013

Topics covered in the m odule...

Requirements gathering & task analysisPrototyping and visualisationEvaluationHuman and the computer abilitiesUser interface styles and supportHuman factors in design / Inclusive Design

Guidelines, rules and standardsUniversal Access and Digital MediaOrdinary and extraordinary systems and people



Module Organisation

See timetableWarning: May change



Organisation

Contact Project Time

Thursday 9 12 12 - 2


10/49


Organisation

AC52013 Deliverables

Electronic Submission via BlackboardOr [email protected]
mailto:[email protected]:[email protected]:[email protected]:[email protected]


11/49


Learning m ethods

Workshops Lectures Discussions

Coursework Individual Project work (in groups)

Private study, reading, WWW


12/49


Materials

Resources on WWWhttp://www.computing.dundee.ac.uk/staff/pgregor/links.asp

Some handouts Your own notes from lectures project work

Library


13/49


Assessment AC52013

Three items of coursework Lab Journals (15%)

Group Usability Engineering Project (35%)

Portfolio of work

Degree examination (50%) Note AC52013 WAS AC52003


14/49


Coursework (AC52013.1a)

1 st Deliverable HCI & Usability Report (10%)

Choose an unfamiliar piece of software

Undertake a heuristic evaluationSubmit report as a journal seehandout

Due: 9 am, Monday, week 3


15/49


Coursework (AC52013.2b)

2 nd Deliverable Focus group (5%)

Submit a journal report - see handoutsDue: 9 am, Mondays after lab sheet


16/49


Coursework (AC52013.2)

Usability Engineering Project (35%) Weeks 2-9

36 hours of work by each studentexcluding labs & other class time Deliverables:

Interim Deliverable AC52013.2c in Wk 6 Presentation of Project Progress AC52013.2d in Wk 6 Presentation of Final Project AC53013.3e in Wk 9 Submission AC52013.3f due Week 10


17/49

Starting your project...

Teams Undertake usability engineering project Project choice examples Process not end product HCI approaches / techniques


18/49


Multi-disciplinary Teams

Software engineer Develops, operates and maintains software using

systematic approaches.

Software designer Problem solves and plans a software solution.

Usability engineer Focuses on the HCI aspects of interfaces.


19/49


AC52013

Weekly project meetings (Big stick) Arrange with your team

Decide on ground rules Meet with mentor


20/49


Usability engineering

What is usability?ISO Standards

Usability lifecycle


21/49


What is usability?

Ease of learningEase of use

High speed of user task performanceLow user error rateSubjective user satisfactionUser retention over time

adapted from Schneiderman (1992)


22/49


Definition of usabilityISO 9241-210 (ISO 2010)

ISO 9241-210 (ISO 2010):

(the) extent to which a system, product orservice can be used by specified users to achievespecified goals with effectiveness, efficiency and

satisfaction in a specified context of use

.

One of the best methods for achieving goodusability is through User Centred Design (also referred to as Human Centred Design).


23/49


Components of usability

System performanceSystem functionsUser interface

Reading materialsLanguage translationOutreach programmeModification/extendibility

InstallationField maintenance & serviceability AdvertisingSupport-group users


24/49


User-centred design

UCD focuses on involving users at every stage inthe development and evaluation of alternativedesigns.

Users concerns direct the development rather thantechnical concerns.


25/49


Why User-centred design?


26/49


Poor design

Car lights


27/49


Poor design

Video Cassette Recorder


28/49


Poor design

Mouse connector


29/49



30/49


Task - 30 mins

Find your groupNatter

Find a piece of equipmentUse usability guidelines to evaluateReport back using three aspects asheadings


31/49


User Centred Design

UCD focuses on involving users at every

stage in the development and evaluationof designs.

Users concerns direct the developmentrather than technical concerns.


32/49


ISO Document on HCI

ISO TC 159/SC 4 includes 9241Ergonomics of human-system interaction

ISO 9241-210: 2010 Human-centred design processes forinteractive systems.


33/49


Example from ISO 9241 part14

Menu structures

should reflect userexpectations andfacilitate the user

sability to find andselect menu optionsrelevant to the task


34/49


Software DevelopmentLifecycles

Lifecycles are derived from two maincategories: software development and

HCI SoftwareEngineering

Waterfall

Spiral

Agile

Wheel

DSDM Star

UsabilityEngineering

InteractionDesign

HCI


35/49


Traditional developmentlifecycle


36/49


Spiral


37/49


Dynamic SystemsDevelopment Model


38/49


Wheel


39/49


The

Star

view of systemdevelopment

E v a l u a t i o n

ImplementationTask analysis

Functional analysis

PrototypingRequirementsspecification

Conceptual designFormal design

From Hix & Hartson (1992)


40/49


ISO 9241-210 (2010)

Identify Need forHuman-Centred

Design

Understand andSpecify the Context of

Use

Specify the User andOrganisationalRequirements

Produce DesignSolutions

System satisfiesspecified user and

organisationrequirements

IterateUntil

Satisfied

Evaluate Design AgainstRequirements

ISO 9241-210

ISO 13407


41/49


Interaction design

Identify needs /establish

requirements

(Re)design

Build aninteractive

version

Evaluate

ImplementSystem

Adapted from Preece et al, 2001


42/49


Activities needed for UCD

Identifying needs and establishingrequirements

Developing alternative designs

Building interactive versions of thedesigns

Evaluating the designs


43/49


44/49


Usability Engineering process

Collect & synthesise information aboutusers and tasks - understand usersDevelop a conceptual design of interface

Storyboard/ sketches User

s mental model?

Test with users

Set usability goalsPrototype & evaluate usability goalsNext iteration


45/49


Designing Good Interfaces

Sketch out user scenarios (e.g.storyboards)Test ( evaluate ) scenario with users

Design and build prototypeTest ( evaluate ) prototype with usersIteratively incorporate changes and testuntil:

Behavioural targets are met A critical deadline is met (you run out of

time?)


46/49


Why should we be aware ofUCD?

f


47/49


Why should we be aware ofUCD?

There is growing awareness of the importance of usercentred designIn a survey in 2005

82% of respondents thought user centred design improved theusability of a product

44% thought it reduced development costs

The value of good design is also being recognised by

NASA, as a senior NASA researcher from the NASA AmesResearch Center States

Design is starting to change who succeeds and who fails

(Olsen2007)


48/49


What happens without UCD?

Many examples of problems that can occurwithout UCD e.g. NHS IT project.Began in 2002 and was expected to take 10years In 2007 the head of the project resigned

because they have been building a system withFujitsu without listening to what the end userswant

2010 project reported to be close to failure.User concerns over the safety and security ofthe system were not fully addressed (Beckett 2009).

d C l


49/49

How does HCI relate toSoftware Engineering?

Strategies and techniques to ensure usabilityExpert view on human capabilitiesU/I design principlesDesigning for diversityFormative and summative evaluation ofprototyping

Understanding users

AC52013_1_Introduction 2013.ppt

Documents