24
CS60171 Interactive System Design Mark van Harmelen

Introduction to CS60171 (2009)

Embed Size (px)

DESCRIPTION

An introduction to my postgraduate-level course in the University of Manchester's School of Computer Science

Citation preview

Page 1: Introduction to CS60171 (2009)

CS60171 Interactive System Design

Mark van Harmelen

Page 2: Introduction to CS60171 (2009)

What’s design?

• Design is a process where we – Start with multiple, often conflicting,

requirements and constraints– Make tradeoffs– Produce ‘something’ at the end of the process

Page 3: Introduction to CS60171 (2009)

What’s interactive system design?

• A process where we – Start with multiple, often conflicting,

requirements and constraintsuser requirementssystem capabilities

– Make tradeoffsusability and engineering tradeoffs

– Produce ‘something’ at the end of the processa design for / a prototype of an interactive system

Page 4: Introduction to CS60171 (2009)

Tradeoffs in interactive system design

functionality

user interfacescope

Page 5: Introduction to CS60171 (2009)

How not to do it

• Big fat requirements documents‘never mind the quality or usability, feel the weight!’

Leads to …..

Page 6: Introduction to CS60171 (2009)
Page 7: Introduction to CS60171 (2009)

Goals, roles, tasks, results, things to do work with

How to do it: Mutual learning

Tech stuff: code, datbases, internet, standards,….

Designers’world

Users’world

Page 8: Introduction to CS60171 (2009)

What the users add

• Front end design factors, roles, tasks, etc• Validation of our developing design for– Scope– Functionality– User interface

• Before we write a single line of code– Less code change, less refactoring

Page 9: Introduction to CS60171 (2009)

How to do it: Rapidly at low cost

Page 10: Introduction to CS60171 (2009)

How to do it: The cycle

Design

Test

Redesign / improve

Page 11: Introduction to CS60171 (2009)

Learn

• Background theory

• Practical time-efficient design methods

• People skills, how to work in groupshow to work in industry

(the most important bit?)

Page 12: Introduction to CS60171 (2009)

The method

• The Bridge-UML• A multistage process • We involve

users and designers in a 3 to 5 day workshop and produce avalidated interactive system design before writing any code

Page 13: Introduction to CS60171 (2009)
Page 14: Introduction to CS60171 (2009)

test and improve

Page 15: Introduction to CS60171 (2009)

resize

Page 16: Introduction to CS60171 (2009)

Hey, we are developers, we like a nice design process(won’t the users mess it up?)

requirements / specification process

Page 17: Introduction to CS60171 (2009)

Producing UML from the Bridge

Use caseModel(Use caseDiagrams)

Dynamic model(ActivityDiagrams, …)

Logical model(ClassDiagrams)

Page 18: Introduction to CS60171 (2009)

A well-founded method

Page 19: Introduction to CS60171 (2009)

Past course: Computer prototype

Page 20: Introduction to CS60171 (2009)

Led to……

Page 21: Introduction to CS60171 (2009)

This year…..

• Web app design

• Mobile app design

Page 22: Introduction to CS60171 (2009)

Scope for

• Very technical students

• Human-interested students

Page 23: Introduction to CS60171 (2009)

Finally…..

• Experiential learning = learning by doing

• Authentic learning = real project experience

• Fun !

• ‘Best course I have ever attended’

• ‘All courses should be like this’

Page 24: Introduction to CS60171 (2009)

Check us out

• http://hedtek.com

• MSc projects in an internship framework

• Looking for one or more graduates from this course