A software engineering perspective User interface design A software engineering perspective Soren Lauesen Slides for Chapter 2 November 2004 © 2005, Pearson Education retains the copyright to the slides, but allows restricted copying for teaching purposes only. It is a condition that the source and copyright notice is preserved on all the material.
Traditional systems development HCI classic: iterative design Slide 2 Fig 2.1 The development process Analysis Traditional systems development Design Experts? Guidelines? Program Usability test? Scaring results ! Too late to correct Test Operation Design prototype Program Usability test Study users and tasks Analysis HCI classic: iterative design
Fig 2.2 Hotel system Task list Breakfasts 23/9 Book guest Checkin Checkout Change room Record services Breakfast list Breakfasts 23/9 Room Buffet In room 11 1 12 2 13 1 1 15 . . .
Fig 2.3A Hotel system prototype
(Fig 2.3A Cont.)
Fig 2.3B Defect list for hotel system mockup
Fig 2.3C Hit-rate of Hotel System evaluation Heuristic evaluation: 7 false problems 21 predicted problems 8 likely, but not observed 6 hits 20 observed problems 14 missed problems
Fig 2.4 Various prototypes Tool-drawn mockup: Hand-drawn mockup: 15-30 min 30-60 min Which prototype is the best? Screen prototype: Functional prototype: 1-4 hours 2-8 hours
(Fig 2.4 Cont.) Full contents of a mockup Handling a system Empty screens for copying Screens with realistic data Screens to be filled in by user Menus, lists, dialog boxes Error messages Help texts Notes about what functions do Handling a system with 100 screens? Accelerator effect: If the central screens are good, the rest are okay almost automatically
There is to different types of prototyping Lars C. kofod Vertical Horisontal
There is to different types of prototyping Lars C. kofod Horisontal GUI Workflow How do you come from one point to an other Vertical Test the technical design/solution Database design, Communication protocol on a Cisco router Test of an algorithem Sort The traveling salesman