Chapter 6 - Requirements Gathering, Storyboarding & Prototyping

Question 1

Waterfall Model

Answer 1

low pre-release costs
- short time to develop
- no repeating steps 
high post-release costs
- unstructured and ad hoc correctios 
- aspects of tools being developed ignored

Question 2

UCSD

Answer 2

high pre-release costs
- long time to develop
- steps repeated
low post-release costs
- focus on tool being developed
- users needs must be central to design process
- system evolves through iterative refinement

Question 3

UCSD Process Phases

Answer 3

• requirements gathering
• design & storyboarding
• prototyping

Question 4

Requirements Gathering

Answer 4

• interviews, workplace observation, user surveys, analysis of existing system
• AIM - find out what must proposed system do and how
• output: functional & usability requirements

Question 5

Requirements Types

Answer 5

• functional
• data
• environmental
• user
• usability

Question 6

Design Space Analysis

Answer 6

• Uses QOC notation
• Question
• Option
• Criteria

Question 7

Psychological design rationale

Answer 7

Issues include:

• usefulness
• usability
• accessibility

Question 8

Storyboarding

Answer 8

• rough sketches of what system will look like
• cheap to produce and easy to change
• maps: show how story runs
• narratives: explain how sketches relate

Question 9

Prototyping reasons

Answer 9

• transform abstract design idea into physical form
• communication idea
• iterate and improve

Question 10

Prototype types

Answer 10

• throwaway
• evolutionary
• incremental

Question 11

Prototyping Techniques (5)

Answer 11

• rapid prototyping
• high fidelity and low fidelity
• horizontal
• vertical
• wizard of oz