Chapter 4 - User-Centered System Design Process

Question 1

Waterfall model stages (6)

Answer 1

• Requirements specification
• Architectural design (focus on how requirements can be achieved, identifying main components and relationships)
• Detailed design (based on feasible option from architectural design)
• Coding and testing (produce and test software)
• Integration and deployment
• Maintenance

Question 2

Waterfall weaknesses (4)

Answer 2

• Traditional approach, excludes user
• Reflects views of designer, excludes stakeholder
• User interfaces designed around technical view
• Problem lies with how systems are designed

Question 3

UCSD key activities (6)

Answer 3

• Task analysis (input: problem statement, analysis of user population. output: hta. gives understanding of what client and user want)
• Requirements gathering (inputs: hta, user models, usability principles. outputs: statement of requirements. provides description of what is required from system, what system should do)
• Design and storyboarding (inputs: statement of requirements. outputs: storyboard design, systems justification. Visualise system design and review designs cost with users)
• Prototype Implementation (inputs: storyboard design. output: working, testable prototype. Provides low cost implementation users can test)
• Evaluation (inputs: prototype, requirements statement. outputs: evaluation transcripts and report. Provides evidence of how system is used)
• Installation (input: prototype. output: finished system)

Question 4

Types of prototypes (4)

Answer 4

• Wizard of Oz (prototype controlled by designer behind the scenes)
• Horizontal (user interface only)
• Vertical (limited functionality)
• Full Prototype (full functionality, low performance)