This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Usage-centered design" – news ·newspapers ·books ·scholar ·JSTOR(September 2007) (Learn how and when to remove this message) |
Usage-centered design is an approach touser interface design based on a focus on user intentions and usage patterns. It analyzes users in terms of the roles they play in relation to systems and employs abstract (essential)use cases[1] fortask analysis. It derives visual andinteraction design from abstractprototypes based on the understanding of user roles andtask cases.
Usage-centered design was introduced byLarry Constantine and Lucy Lockwood. The primary reference is their book.[2]
Usage-centered design is largely based on formal, abstract models such as models of interaction between user roles,UML workflow models andtask case and role profiles.Usage-centered design proponents argue for abstract modelling while many designers use realisticpersonas,scenarios and high-fidelityprototypes. The techniques have been applied with particular success in complex software projects, some of which have been reported in case studies.[3]
Usage-centered design share some common ideas withactivity-centered design. It is concerned more with the activities of users but not the users per se. Constantine (2006) presents an integrated framework where the models of Usage-centered design are enriched with concepts from theactivity theory.
Thissoftware-engineering-related article is astub. You can help Wikipedia byexpanding it. |