Construction

1
Chapter 4

• Construction

Slide extracts from text book GUI design
essentials,Authors Susan Weinschenk, Pamela
Jamar, Sarah C. Yeo PublisherWiley
2
Purpose
Deliverables

• At the end of construction you will have
• A hi-fi computer prototype of your interface
• A user interface design description

Preparation
3
Process

• Develop a hi-fi computer prototype
• Test the hi-fi computer prototype and revise it
• Document the complete, final interface design

4
Process

• Develop a Hi-Fi Computer Prototype
• A means to communicate the design to other
  project team members
• A way for nonprogrammers to make design
  contributions
• A tangible means to evaluate and tradeoff
  alternative design solutions
• A dynamic, living specification of the design,
  subject to less misinterpretation than paper
  mockups

5
Process

• Develop a Hi-Fi Computer Prototype (cont)
• Creating the Prototype
• Decide on exact location for each control on each
  screen
• Decide on exact wording and names of buttons
• make changes in how much is on each screen
• incorporate all your corporate guidelines and
  standards

6
Process

• Develop a Hi-Fi Computer Prototype (cont)
• Apply intelligent interface design decisions
  about visual search, cognitive demands and so on

7
Process

• Apply intelligent interface design decisions
  about visual search, cognitive demands and so on

8
Process

• Apply intelligent interface design decisions
  about visual search, cognitive demands and so on

9
Process

• What is and Is not a Prototype
• Use an interface prototyping tool
• Dont misrepresent system capabilities and create
  unrealistic expectations
• Dont lose control of the prototype
• Prioritizing the Prototyping
• High frequency tasks
• The parts of the interface where there is the
  most uncertainty about usability
• Alternative design solutions
• Portions of the design that represent design
  approaches or features used repeatedly

10
Process

• Test
• Design Reviews
• A comparison against human factors guidelines and
  checklists
• A review by colleagues not involved in the design
  of this particular interface
• A review by an interface design expert
• A review by users and key stakeholders

11
Process

• Design Reviews
• Confusing organization of the interface into
  windows and dialog boxes
• Missing or unclear window, menu, control labels
• Unfriendly, unhelpful wording or messages
• unnecessary steps that slow user interaction and
  task performance

12
Process

• Design Reviews
• Confusing, cluttered layout
• Misuse of visual coding techniques that hinder
  visual searching and interpretation
• Lack of continuous and clear feedback for all
  user actions
• Noncompliance with the selected interface
  standards and guidelines

13
Process

• When soliciting feedback ensure
• You do not discourage participants from providing
  valuable feedback by appearing defensive or
  argumentative
• The meeting isnt used to revise the interface
  design
• Usability Testing

14
Process

• Document the Interface Design
• Prototypes Alone are not Enough
• The problem with Typical Interface Documentation

15
Process

• The problem with Typical Interface Documentation
  (cont.)

16
Process

• The User Interface Design Description
• Anyone can write
• Anyone can read
• Completely specifies the appearance and behavior
  of the user interface and fills in any gaps
• Breaks the interface into meaningful pieces that
  can be used to track development
• Fist into the organizations standard world of
  project documentation, distribution and control

17
Process
18
Process
19
Process
20
Process
21
Process
22
Process
23
Process
24
Process
25
Process

• Document screen objects
• Document events and responses
• About System Implementation

26
Summary