Processes and methods for User-centered design (UCD)
Note: Recently, some prefer the term Human-Centered Design in
order to consider all stakeholders. In either case, the goal is
to meet the needs of people as opposed to designing the system
around technological capabilities.
Emphasis of Preece, Rogers and Sharp
- Called Interaction Design
- Multidisciplinary team
- Basic steps (see p. 12 and section 6.2.1)
- Identifying needs and establishing requirements
- Developing alternative designs that meet requirements
- Building interactive versions
- Evaluatings design versions
The authors note that the second item can be broken up into two
sub-activities: conceptual design and
physical design.
Rosson and Carroll (Usability Engineering, former text for HCI 440)
- Scenario-based design -- develop concrete stories to describe users and needs and motivate the design
- Explicitly list trade-offs when developing an interactive system
- Steps in the design process
- Requirements analysis: create problem scenarios (R&C chapter 2)
- Activity design (chapter 3)
- Information design (chapter 4)
- Interaction design (chapter 5)
- Prototyping (chapter 6)
- Evaluation (chapter 7)
The software life cycle (presented in Human-Computer
Interaction by Dix, Finley, Abowd and Beale
- Requirements specification
- Architectural design
- Detailed design
- Coding and unit testing
- Integration and testing
- Operation and maintenance
Hewlett Packard's Human Factors Activities (reported in
Handbook of Usability Testing by Jeffrey Rubin)
- Needs analysis
- Requirements specification
- Conceptual design
- Prototype, development and test
- Product evaluation
Principles for User-centered design (adapted from Gould and Lewis)
- Early focus on users and tasks
- Empirical measurement (and testing) of product usage
- Iterative design
Note how this last list corresponds with the list our text has
on p. 13 and p. 170:
- Focus on users
- Specific usability and user experience goals
- Iteration
Discussion items:
- How do these processes correspond to each other? Are they
consistent with each other? Are there any implied differences
among the processes?
- How do these processes match the HCI curriculum?
- How are these processes actually practiced?
- The following are titles for professional positions related
to HCI. Assuming we can identify the responsibilities of each
position, how can they be described in terms of activities for
developing an interactive system?
- Web developer
- Graphic designer
- Information architect
- Usability engineer
- Usability specialist
- User interface engineer
- User interface analyst
- Usability test engineer
- Director of User Experience
- Web Accessibility Outreach Coordinator
- Experience planner
- The following are disciplines that contribute to HCI. In
what way do they contribute to activities in the development
process?
- Computer science
- Psychology
- Art and Graphic design
- Psychology (and which areas?)
- Anthropology
- Linguistics
- Engineering (software, ergonomics, human factors)
- Philosophy
Last modified: Wed Sep 15 16:29:59 Central Daylight Time 2004