User-Centered Design - Revision history

Tkokotas at 17:43, 16 November 2018

2018-11-16T17:43:47Z

← Older revision		Revision as of 17:43, 16 November 2018
Line 1:		Line 1:
			''Developed by Cetin Arslan''


	==Abstract==		==Abstract==

Arslance: /* Limitations of User Centered Design */

2018-02-28T22:32:34Z

Limitations of User Centered Design

← Older revision		Revision as of 22:32, 28 February 2018
Line 109:		Line 109:
	==Limitations of User Centered Design==		==Limitations of User Centered Design==

	The UCD process described above may seem easy to follow, however it is difficult to implement, while offering certain advantages e.g. as a higher ~~customer~~ satisfaction or less service costs and hours. Besides that some prominent problems for project managers are mentioned below:		The UCD process described above may seem easy to follow, however it is difficult to implement, while offering certain advantages e.g. a higher user satisfaction or less service costs and hours due to adaption to user abilities. Besides that some prominent problems for project managers are mentioned below:

	<ol>		<ol>

Arslance at 22:31, 28 February 2018

2018-02-28T22:31:28Z

Show changes

Arslance at 21:28, 28 February 2018

2018-02-28T21:28:17Z

← Older revision		Revision as of 21:28, 28 February 2018
Line 5:		Line 5:
	The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.		The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==~~Application~~ ==		==Big idea==

	The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.		The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.
Line 18:		Line 18:
	Further the UCD process can be connected to ISO 21500 "DIN ISO 21500:2016-02"<ref>Guidance on project management, ''https://www.beuth.de/en/standard/din-iso-21500/207461260 '', (Accessed on 28th of February), </ref>. The five process groups described in ISO 21500 " Initiating, Planning, Implementing, Controlling and Closing" can be seen as the typical tasks which are necessary to be done during the implementation of the UCD process according to DIN EN ISO 9241-210 "Human-centred design for interactive systems" as described in the following chapter <ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.		Further the UCD process can be connected to ISO 21500 "DIN ISO 21500:2016-02"<ref>Guidance on project management, ''https://www.beuth.de/en/standard/din-iso-21500/207461260 '', (Accessed on 28th of February), </ref>. The five process groups described in ISO 21500 " Initiating, Planning, Implementing, Controlling and Closing" can be seen as the typical tasks which are necessary to be done during the implementation of the UCD process according to DIN EN ISO 9241-210 "Human-centred design for interactive systems" as described in the following chapter <ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==User-Centered Design Process==		==Application: The User-Centered Design Process==

	Having a closer look at classic development models shows that the focus of development does not respect the needs of the end users. As technologies advance and become more deeply integrated into human lifes, products or services must become more intuitive and user-friendly. Therefore, the goal is to design easy-to-learn and easy-to-use interactive products that provide the user with an optimal interface and an enjoyable user experience. For this, the development process must be geared towards the users and their needs, abilities and expectations must be taken into account<ref name="Beier">Beier, M. ''Usability'',(Springer Berlin Heidelberg, 2002) </ref>. These criteria are fulfilled by the User Centered Design approach. Through the usage of the UCD developments of a wide range of products and services are conceivable. Principles of the approach are an iterative proceeding, an early focus on user and organizational requirements and the empirical verification of users' designs<ref name="Gould">Gould, J. D. & Lewis, C. ''Designing for Usability: Key Principles and What Designers Think'', "https://www.research.ibm.com/compsci/spotlight/hci/p300-gould.pdf",(Accessed on 28th of February </ref>. The UCD process is presented in the standard DIN EN ISO 9241-210: 2011 " Human-centred design for interactive systems." Since the development of a human-friendly product is in the foreground, the term "human-centered design" is used. The procedure with five distinct phases essentially characterizes the process, whose phases are shown in Figure 1.		Having a closer look at classic development models shows that the focus of development does not respect the needs of the end users. As technologies advance and become more deeply integrated into human lifes, products or services must become more intuitive and user-friendly. Therefore, the goal is to design easy-to-learn and easy-to-use interactive products that provide the user with an optimal interface and an enjoyable user experience. For this, the development process must be geared towards the users and their needs, abilities and expectations must be taken into account<ref name="Beier">Beier, M. ''Usability'',(Springer Berlin Heidelberg, 2002) </ref>. These criteria are fulfilled by the User Centered Design approach. Through the usage of the UCD developments of a wide range of products and services are conceivable. Principles of the approach are an iterative proceeding, an early focus on user and organizational requirements and the empirical verification of users' designs<ref name="Gould">Gould, J. D. & Lewis, C. ''Designing for Usability: Key Principles and What Designers Think'', "https://www.research.ibm.com/compsci/spotlight/hci/p300-gould.pdf",(Accessed on 28th of February </ref>. The UCD process is presented in the standard DIN EN ISO 9241-210: 2011 " Human-centred design for interactive systems." Since the development of a human-friendly product is in the foreground, the term "human-centered design" is used. The procedure with five distinct phases essentially characterizes the process, whose phases are shown in Figure 1.

Arslance: /* Application */

2018-02-28T21:25:29Z

Application

← Older revision		Revision as of 21:25, 28 February 2018
Line 16:		Line 16:

	Besides the classic usage of the UCD in software development process a project manager can use the UCD as method to design and produce several products, goods and services. It shows characteristics of Iterative and Incremental Life Cycles as discussed by the Project Management Institute<ref name="guide">Project Management Institute, ''A Guide to Project Management Body of Knowledge'', (Project Management Institute, 2013), </ref>.		Besides the classic usage of the UCD in software development process a project manager can use the UCD as method to design and produce several products, goods and services. It shows characteristics of Iterative and Incremental Life Cycles as discussed by the Project Management Institute<ref name="guide">Project Management Institute, ''A Guide to Project Management Body of Knowledge'', (Project Management Institute, 2013), </ref>.
	Further the UCD process can be connected to ISO 21500 "DIN ISO 21500:2016-02"<ref>Guidance on project management, ''https://www.beuth.de/en/standard/din-iso-21500/207461260 '', (Accessed on 28th of February), </ref>. The five process groups described in ISO 21500 " Initiating, Planning, Implementing, Controlling and Closing" can be seen as the typical tasks which are necessary to be done during the implementation of the UCD process according to DIN EN ISO 9241-210 "Human-centred design for interactive systems <ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.		Further the UCD process can be connected to ISO 21500 "DIN ISO 21500:2016-02"<ref>Guidance on project management, ''https://www.beuth.de/en/standard/din-iso-21500/207461260 '', (Accessed on 28th of February), </ref>. The five process groups described in ISO 21500 " Initiating, Planning, Implementing, Controlling and Closing" can be seen as the typical tasks which are necessary to be done during the implementation of the UCD process according to DIN EN ISO 9241-210 "Human-centred design for interactive systems" as described in the following chapter <ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==User-Centered Design Process==		==User-Centered Design Process==

Arslance: /* Application */

2018-02-28T21:24:04Z

Application

← Older revision		Revision as of 21:24, 28 February 2018
Line 5:		Line 5:
	The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.		The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==Application ==		==Application ==

	The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.		The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.
Line 15:		Line 15:
	* empirical review of the designs by users		* empirical review of the designs by users

	Besides the classic usage of the UCD in software development process a project manager can use the UCD as method to design and produce several products, goods and services. It shows characteristics of Iterative and Incremental Life Cycles as discussed by the Project Management Institute<ref name="guide">Project Management Institute, ''A Guide to Project Management Body of Knowledge'', (Project Management Institute, 2013), </ref>.		Besides the classic usage of the UCD in software development process a project manager can use the UCD as method to design and produce several products, goods and services. It shows characteristics of Iterative and Incremental Life Cycles as discussed by the Project Management Institute<ref name="guide">Project Management Institute, ''A Guide to Project Management Body of Knowledge'', (Project Management Institute, 2013), </ref>.
			Further the UCD process can be connected to ISO 21500 "DIN ISO 21500:2016-02"<ref>Guidance on project management, ''https://www.beuth.de/en/standard/din-iso-21500/207461260 '', (Accessed on 28th of February), </ref>. The five process groups described in ISO 21500 " Initiating, Planning, Implementing, Controlling and Closing" can be seen as the typical tasks which are necessary to be done during the implementation of the UCD process according to DIN EN ISO 9241-210 "Human-centred design for interactive systems <ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==User-Centered Design Process==		==User-Centered Design Process==

Arslance at 21:08, 28 February 2018

2018-02-28T21:08:43Z

← Older revision		Revision as of 21:08, 28 February 2018
Line 5:		Line 5:
	The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.		The User-Centered Design Approach takes these problems into consideration. The goal is to design understandable and enjoyable solutions for the end customers, while either taking their personal opinions into account or lead the project from an end customer optimized view. Therefore the different processes must be lead towards a user's needs, abilities and expectations in order to guarantee a maximized customer focus. The UCD process consists of five steps, of which the last 4 are following a interative logic. Furthermore, the UCD is defined in the DIN EN ISO 9241-210 "Human-centred design for interactive systems " standard<ref name="Human-centred design for interactive systems">''Human-centred design for interactive systems'', "https://www.beuth.de/en/standard/din-en-iso-9241-210/135399380",(Accessed on 28th of February) </ref>.

	==~~Characteristics & Principles~~ ==		==Application ==

	The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.		The UCD concept was first mentioned by Donald Norman in his publication "User-Centered System Design: New Perspectives on Human-Computer Interaction" in 1986 and further discussed in his book "The Design of Everyday Things"<ref name="Norman"> Norman D. A. ''User-Centered System Design: New Perspectives on Human-Computer Interaction'', (CRC Press, 1986) </ref> <ref name="Norman2"> Norman D. A. '' The Design of Everyday Things: Revised and Expanded Edition'', (Basic Books, 2013) </ref>. Norman shows the importance of a users need in a product and the mistakes caused by unappropriate designs, which aren't user focused and don't take these into account. Therefore he gives recommendations based on the users needs and wishes.
Line 14:		Line 14:
	* Early focus on user and task requirements		* Early focus on user and task requirements
	* empirical review of the designs by users		* empirical review of the designs by users

			Besides the classic usage of the UCD in software development process a project manager can use the UCD as method to design and produce several products, goods and services. It shows characteristics of Iterative and Incremental Life Cycles as discussed by the Project Management Institute<ref name="guide">Project Management Institute, ''A Guide to Project Management Body of Knowledge'', (Project Management Institute, 2013), </ref>.

	==User-Centered Design Process==		==User-Centered Design Process==

Arslance: /* Limitations of User Centered Design */

2018-02-28T20:39:05Z

Limitations of User Centered Design

← Older revision		Revision as of 20:39, 28 February 2018
Line 104:		Line 104:


	==== Limitations of User Centered Design====		==Limitations of User Centered Design==

	The process described above may seem easy to follow, however it is a complex process to follow, which has certain advantages which where discussed before. Besides that some prominent problems for project managers are mentioned below:		The process described above may seem easy to follow, however it is a complex process to follow, which has certain advantages which where discussed before. Besides that some prominent problems for project managers are mentioned below:

Arslance: /* Limitations of User Centered Design */

2018-02-28T20:38:45Z

Limitations of User Centered Design

← Older revision		Revision as of 20:38, 28 February 2018
Line 106:		Line 106:
	==== Limitations of User Centered Design====		==== Limitations of User Centered Design====

	The process described above may seem easy to follow, however it is a complex process to follow, which has certain advantages which where discussed before. Besides that some prominent problems for ~~Project Managers~~ are mentioned below:		The process described above may seem easy to follow, however it is a complex process to follow, which has certain advantages which where discussed before. Besides that some prominent problems for project managers are mentioned below:

	<ol>		<ol>
	<li>'''~~High~~ development costs:'''		<li>'''Higher development costs:''' As a lot of data are the basis for the UCD process, the research which is needed in forehand can cause budget problems for project managers. Not only interviews but also market research, working with an external consulting partner or simply the detailed use of the tools described previously can blow up a budget. Further as the process is iterative, too many circles in the several phases can cause high development costs.

	<li>'''Time consuming development as user ~~interacting takes~~ a ~~lot~~ of time~~:'''~~		<li>'''Time consuming development :''' As not only the costs are affected directly by too many circles in the process, also the development time needs to be considered by project managers. Delays caused by not satisfied user needs and the wish the deliver a 100% perfect product can cause problems with the set schedule of development. Further the different interactions which are needed in order to gain useful data are time consuming, as also the meetings that are needed to discuss the different results.

	<li>'''No guarantee that a user sample will fit into the real world:'''		<li>'''No guarantee that a user sample will fit into the real world:''' In the end there is no guarantee that a project, which is developed under UCD rules will produce a perfect product. The aim is still to deliver a highselling product which satisfies the customers needs, abilities and wishes. There are still high risks that the market will not approved the developed solution although it fits into the preferences of several user groups. History has shown that also products which where not designed under UCD rules, still where successful on the markets and "teached" the users themselves how to use them properly.

	</ol>		</ol>

Arslance: /* Advantages and Limitations */

2018-02-28T20:26:37Z

Advantages and Limitations

← Older revision		Revision as of 20:26, 28 February 2018
Line 104:		Line 104:


	==~~Advantages and~~ Limitations==		==== Limitations of User Centered Design====

	~~====Advantages of User Centered Design====~~		The process described above may seem easy to follow, however it is a complex process to follow, which has certain advantages which where discussed before. Besides that some prominent problems for Project Managers are mentioned below:

	* Increased sales through respecting user wishes and needs		<ol>
	* As users are part of a development ~~process they feel as a part of the project team~~		<li>'''High development costs:'''
	* Less adjustments after a product is released
	* Less user complaints about confusing usability
	* Support savings as users are more likely to understand a product

	~~====Disadvantages~~ of ~~User Centered Design====~~		<li>'''Time consuming development as user interacting takes a lot of time:'''

	* High development costs		<li>'''No guarantee that a user sample will fit into the real world:'''
	* Time consuming development as user interacting takes a lot of time
	* Difficult transition from user data into design		</ol>
	* Uncertain expectations to the real world use of products by a user
	* No guarantee that a user sample will fit into the real world

	==Annotated Bibliography==		==Annotated Bibliography==