Daniel K. Schneider: Text replacement - "$" to " {{edutechwiki}}"

2021-04-10T00:18:08Z

Text replacement - "$" to " {{edutechwiki}}"

← Older revision		Revision as of 02:18, 10 April 2021
Line 67:		Line 67:

	[[Category:Design methodologies]]		[[Category:Design methodologies]]
			{{edutechwiki}}

Daniel K. Schneider: 1 revision imported

2021-04-09T22:18:10Z

1 revision imported

← Older revision	Revision as of 00:18, 10 April 2021
(No difference)

Daniel K. Schneider: Text replacement - "" to ""

2016-08-22T17:25:32Z

Text replacement - "<pageby nominor="false" comments="false"/>" to ""

New page

{{incomplete}}

{{interaction-design|Overview article and menu}}

== Introduction ==

{{quotation | In broad terms, user-centered design (UCD) is a design philosophy and a process in which the needs, wants, and limitations of the end user of an interface or document are given extensive attention at each stage of the design process. User-centered design can be characterized as a multi-stage problem solving process that not only requires designers to analyze and foresee how users are likely to use an interface, but to test the validity of their assumptions with regards to user behaviour in real world tests with actual users. }} ([[Wikipedia:User-centered design | Wikipedia]])

Carr (1997) also makes the distinction between ''user-design'' and user-''centered'' design: {{quotation | In the former, users are engaged in the actual creation of their own systems in negotiation with leaders and designers. In the latter, users are considered
central to the design specifications; however, design control
remains firmly in the hands of professional designers and approval power remains with leadership}}. We are not sure that every UCD theorist or practicioner can identifiy with this distinction

The W3C [http://www.w3.org/WAI/redesign/ucd Notes on User Centered Design Process (UCD)] summarize UCD principles from Jeffrey Rubin (1984):
# Early focus on users and tasks
#* Structured and systematic information gathering (consistent across the board)
#* Designers trained by experts before conducting data collection sessions
# Empirical Measurement and testing of product usage
#* Focus on ease of learning and ease of use
#* Testing of prototypes with actual users
# Iterative Design
#* Product designed, modified and tested repeatedly.
#* Allow for the complete overhaul and rethinking of design by early testing of conceptual models and design ideas.

The same W3C also outlines a typical user-centered design process.

According to David Travis, in [[http://www.userfocus.co.uk/articles/iso-13407-is-dead.html ISO 13407 is dead. Long live ISO 9241-210!] (June 2011, retrived June 6 2011), ISO 9241-210 (formerly ISO 13407) defines 6 key principles for user centred design:
* The design is based upon an explicit understanding of users, tasks and environments.
* Users are involved throughout design and development.
* The design is driven and refined by user-centred evaluation.
* The process is iterative.
* The design addresses the whole user experience.
* The design team includes multidisciplinary skills and perspectives.

See also:
* [[Human-computer interaction]]
* [[Design and usability methods and techniques]] (includes links to various design and usability methods).
* [[Usability]]

== Types of user-centered design methodologies ==

Design methodologies have been developed in various contexts and can be sometimes combined.
Carr (1997) identifies three methods that can help designers get a sense of how involve users in the creation of new systems of learning:
ethnographic field methods, cooperative design and action research-based user-design.

Here is a provisional list of popular design approaches:

* [[Wikipedia:Extreme Programming]]
* [[Participatory design]] and cooperative design
* [[Activity theory]]-based approaches (such as expansive learning or the change laboratory method)
* [[Action research]]
* [[Ethnography]]
* [[Design-based research]]
* [[Human-computer interaction#Story-based design | Story-based design]] (more a design tool than an explicit methodology)
* [[Scenario-based usability engineering]] ([[scenario-based design]])

== Links ==

* [http://wiki.fluidproject.org/display/fluid/Fluid+Project+Wiki Fluid Project Wiki] includes a [http://wiki.fluidproject.org/display/fluid/Design+Handbook Design Handbook] that is {{quotation|is a How-to Guide filled with user-centered design (UCD) techniques you can use to learn from your users and design better user experiences. The handbook includes information on a variety of UCD practices, from performing user research and creating models (such as personas and scenarios) to inform the design process, to performing UX walkthroughs and user testing of your website or application to assess usability and accessibility.}}

* [http://www.userfocus.co.uk/articles/iso-13407-is-dead.html ISO 13407 is dead. Long live ISO 9241-210!] by David Travis, UserFocus, June 2011.

== References ==

* Carr,Alison, User-design in the creation of human learning systems, Educational Technology Research and Development, 45, 3, 9/18/1997, Page 5, [http://dx.doi.org/10.1007/BF02299726 DOI 10.1007/BF02299726] (This is an article [[User:DSchneider|DSchneider]] recommends, e.g. there is a list of user-design decision guiding questions).

* [http://www.iso.org/iso/catalogue_detail.htm?csnumber=52075 ISO 9241-210], Ergonomics of human-system interaction -- Part 210: Human-centred design for interactive systems, (you can buy it for 124 CHF ...)

[[Category:Design methodologies]]

User-centered design - Revision history

Daniel K. Schneider: Text replacement - "$" to " {{edutechwiki}}"

Daniel K. Schneider: 1 revision imported

Daniel K. Schneider: Text replacement - "" to ""