• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Introduction to CS60171 (2009)
 

Introduction to CS60171 (2009)

on

  • 1,199 views

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

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

Statistics

Views

Total Views
1,199
Views on SlideShare
1,062
Embed Views
137

Actions

Likes
0
Downloads
23
Comments
0

1 Embed 137

http://hedtek.com 137

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Introduction to CS60171 (2009) Introduction to CS60171 (2009) Presentation Transcript

    • CS60171 Interactive System Design Mark van Harmelen
    • 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
    • What’s interactive system design?
      • A process where we
        • Start with multiple, often conflicting, requirements and constraints user requirements system capabilities
        • Make tradeoffs usability and engineering tradeoffs
        • Produce ‘something’ at the end of the process a design for / a prototype of an interactive system
    • Tradeoffs in interactive system design functionality user interface scope
    • How not to do it
      • Big fat requirements documents ‘never mind the quality or usability, feel the weight!’ Leads to …..
    •  
    • How to do it: Mutual learning Goals, roles, tasks, results, things to do work with Tech stuff: code, datbases, internet, standards, …. Designers’ world Users’ world
    • 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
    • How to do it: Rapidly at low cost
    • How to do it: The cycle Design Test Redesign / improve
    • Learn
      • Background theory
      • Practical time-efficient design methods
      • People skills, how to work in groups how to work in industry (the most important bit?)
    • The method
      • The Bridge-UML
      • A multistage process
      • We involve users and designers in a 3 to 5 day workshop and produce a validated interactive system design before writing any code
    •  
    • test and improve
    • resize
    • Hey, we are developers, we like a nice design process (won’t the users mess it up?) requirements / specification process
    • Producing UML from the Bridge Use case Model (Use case Diagrams) Dynamic model (Activity Diagrams, …) Logical model (Class Diagrams)
    • A well-founded method
    • Past course: Computer prototype
    • Led to……
    • This year…..
      • Web app design
      • Mobile app design
    • Scope for
      • Very technical students
      • Human-interested students
    • Finally…..
      • Experiential learning = learning by doing
      • Authentic learning = real project experience
      • Fun !
      • ‘ Best course I have ever attended’
      • ‘ All courses should be like this’
    • Check us out
      • http://hedtek.com
      • MSc projects in an internship framework
      • Looking for one or more graduates from this course