9 software projects totaling $96.

7 million: Where The Money Went

[Report to Congress, Comptroller General, 1979]

Delivered, but never

successfully used
45%

Used as delivered
2%
Usable w. rework
Paid for, but
3% not delivered
Used w. extensive rework, 30%
but later abandoned
20%
20
 Deliverable 0
Deliverable 1 Deliverable 2 Deliverable 3 Deliverable 4 Deliverable 5 Deliverable 6

Requirements Requirements System Object Implemen-

Testing
Elicitation Analysis Design Design tation

Implemented
Expressed in By
Structured By Realized By
Terms Of Verified
By

class...
class...
class... ?
class.... ?
Use Case Application Solution
Domain SubSystems Source Test
Model Domain
Objects Code Cases
Objects

Each activity produces one or more models

Characteristic Description
Windows Multiple windows allow different information to be
displayed simultaneously on the user’s screen.
Icons Icons different types of information. On some systems,
icons represent files; on others, icons represent
processes.
Menus Commands are selected from a menu rather than typed
in a command language.
Pointing A pointing device such as a mouse is used for selecting
choices from a menu or indicating items of interest in a
window.
Graphics Graphical elements can be mixed with text on the same
display.
 Analyse and Produce paper- Evaluate design
understand user based design with end-users
activities prototype

Produce
Design Evaluate design
dynamic design
prototype with end-users
prototype

Executable Implement
prototype final user
interface
Principle Description
User familiarity The interface should use terms and
concepts which are drawn from the
experience of the people who will make most
use of the system.
Consistency The interface should be consistent in that,
wherever possible, comparable operations
should be activated in the same way.
Minimal surprise Users should never be surprised by the
behaviour of a system.
Recoverability The interface should include mechanisms to
allow users to recover from errors.
User guidance The interface should provide meaningful
feedback when errors occur and provide
context-sensitive user help facilities.
User diversity The interface should provide appropriate
interaction facilities for different types of
system user.
Interaction Main advantages Main disadvantages Application
style examples
Direct Fast and intuitive May be hard to Video games
manipulation interaction implement CAD systems
Easy to learn Only suitable where
there is a visual
metaphor for tasks
and objects
Menu Avoids user error Slow for experienced Most general-
selection Little typing users purpose systems
required Can become complex
if many menu options
Form fill-in Simple data entry Takes up a lot of Stock control,
Easy to learn screen space Personal loan
processing
Command Powerful and Hard to learn Operating systems,
language flexible Poor error Library information
management retrieval systems
Natural Accessible to Requires more typing Timetable systems
language casual users Natural language WWW information
Easily extended understanding retrieval systems
systems are unreliable
Title JSD. example Grid Busy

Method JSD
OUIT
Type Network Units cm

Selection Process Reduce Full

PRINT

NODE LINKS FONT LABEL EDIT

 NE W BOOK

Title ISBN

Author Price

Publication
Publisher date
Number of
Edition copies

Classification Loan
status
Date of
Order
purchase
status
 Command
Gr aphical user
language
interface
interface

Command
GUI
language
manager
interpreter

Operating system
Information to Presentation
be displayed software

Display
 View state view modification Controller state
messages User inputs
View methods Controller methods

Model queries
and updates Model edits
Model state

Model methods
 Jan Feb Mar April May June
2842 2851 3164 2789 1273 2835

4000

3000

2000

1000

0
Jan Feb Mar April May June
 1
0 10 20
4 2

Dial with needle Pie chart Thermometer Horizontal bar

 Pressure Temper atu re
0 100 200 300 400 0 25 50 75 100
!
The filename you have chosen h as been
used. Please choose an other name

Ch. 16 User interface design

OK Cancel
 Application

Help Error message

interface system

Message
presentation
system

Help Error message

frames texts
Context The user guidance system should be aware of what the user is
doing and should adjust the output message to the current
context.
Experience As users become familiar with a system they become irritated
by long, ‘meaningful’ messages. However, beginners find it
difficult to understand short terse statements of the problem.
The user guidance system should provide bothtypes of message
and allow the user to control message conciseness.
Skill level Messages should be tailored to the user’s skills as well as their
experience. Messages for the different classes of user may be
expressed in different ways depending onthe terminology which
is familiar to the reader.
Style Messages should be positive rather than negative. They should
use the active rather than the passive mode of address. They
should never be insulting or try to be funny.
Culture Wherever possible, the designer of messages should be familiar
with the culture of the country where the system is sold. There
are distinct cultural differences between Europe, Asia and
America. A suitable message for one culture might be
unacceptable in another.
Please type the patient name in the box then click ok

Bates , J .

OK Cancel
 User -or iented er ror message
System-oriented err or message

Error #27

?
Patient J . Bates is not r egister ed
Invalid patient id entered C k l ai o ct o ni r e Pn a t s l i f s
Click on Retry to re-input a patient name
Click on Help for more information

O K Cancel
Patients Help Retry C a n
 Top-level
entry

Entry from
application

Entry from error

message system

Help frame network

Help frame map Mail redirection

Mail may be redirected to another

network user by pressing the
redirect button in the control
panel. The system asks for the
name of the user or users to
whom the mail has been sent

You are here more next top ics

Help history

1. Mail
2. Send mail
3. Read mail
4. Redirection
 System System Novice Experienced System
evaluators administrators users users administrators

Functional Installation Introductory Reference Administrator’s

description document manual manual guide

Description of How to install Getting Facility Operation and

services the system started description maintenance
Attribute Description
Learnability How long does it take a new user to
become productive with the system?
Speed of operation How well does the system response match
the user’s work practice?
Robustness How tolerant is the system of user error?
Recoverability How good is the system at recovering from
user errors?
Adaptability How closely is the system tied to a single
model of work?