Process for User-centered Development - Revision history

Adamssw: This space for rent.

2009-11-23T20:48:04Z

This space for rent.

← Older revision		Revision as of 20:48, 23 November 2009
Line 101:		Line 101:
	=== Disadvantages ===		=== Disadvantages ===

-	One of the problem of iterative design is it's cost, if you exaggerate the number of iterations. Indeed, each iteration can be time consuming, and time management is critical in software development. Jakob Nielsen has realized experiences about the number of iterations that should be performed by a user interface designer. According to his opinion, developers should realize three iterations to obtain an interface adapted to users needs without spending a lot of time and money.	+	One of the problem of iterative design is it's cost, if you exaggerate the number of iterations. Indeed, each iteration can be time consuming, and time management is critical in software development. Jakob Nielsen has realized experiences about the number of iterations that should be performed by a user interface designer. According to his opinion, developers should realize three iterations to obtain an interface adapted to users needs without excessively spending a lot of time and money.

	== References ==		== References ==

Adamssw: hey look it's not 4 yet. I should save it anyways, just incase the power goes out.

2009-11-23T20:47:02Z

hey look it's not 4 yet. I should save it anyways, just incase the power goes out.

← Older revision		Revision as of 20:47, 23 November 2009
Line 77:		Line 77:
	=== Introduction ===		=== Introduction ===

-	~~When designing~~ a user interface, it is ~~almost impossible~~ to obtain an interface ~~without any~~ usability issues in a single attempt. To solve this problem, the development team can use a method called iterative design. This method is applied in the development of a new ~~product (typically a~~ software ~~with a user interface). It consists of developing it by a succession of iterations~~. Iterations are used to improve the ~~current~~ interface by collecting ~~users~~ feedback from a prototype of the interface~~, correct usability~~ issues raised ~~by them by creating~~ a new prototype, then ~~start a new iteration~~. ~~Thus, this is a summary of what an iteration should be:~~	+	In the design of a user interface, it is not possible to obtain an interface free from usability issues in a single attempt. To solve this problem, the development team can use a method called iterative design. This method is applied in the development of new products in general, and can be applied to software easily. Iterations are used to improve the interface by collecting user feedback from a prototype of the interface. Usability issues raised can be corrected in the creation of a new prototype, which is then evaluated.

-	* Prepare a prototype design ~~of the product~~	+	The steps in an iteration should be:
		+	* Prepare a prototype design
	* Present this design to a set of potential users		* Present this design to a set of potential users
-	* Collect problems ~~noticed~~ by users	+	* Collect potential problems, as reported by users
-	* Refine design based on ~~users point of view~~	+	* Refine design based on user input

-	Iterative design is about refinement~~: Each~~ iteration brings improvements to the whole project by solving usability issues. This method puts quality in the centre of the development process~~. Indeed, by refining step by step the design, you obtain a product totally in appropriateness to its future users needs~~.	+	Iterative design is purely about refinement; each iteration brings improvements to the whole project by solving usability issues. This method puts user assessed quality at the centre of the development process.

-	~~It explains why it fits totally with User Interface development and design. The development~~ of a good user interface is ~~mostly~~ the result of ~~a good~~ understanding ~~of its users~~ needs and ~~behaviour~~. ~~As it's~~ hard for ~~a user~~ interface designer to ~~get~~ a perfect understanding of ~~them,~~ the iterative design method allows ~~him~~ to base ~~his~~ work on ~~users~~ feedback. Thus, usability issues will be ~~corrected easily. These feedbacks can also be used for the development of future projects.~~	+	Development of a good user interface is the result of understanding user's needs and behavior. It is hard for an interface designer to obtain a perfect understanding of user's goals and the iterative design method allows them to base their work on user feedback. Thus, usability issues will be minimized.
-		+
-	Websites are a good example of iterative method usage: Web masters generally propose a new website design and collect user's feedback by email or with a dedicated topic on the website forum to improve it. For software development, it is different as it is impossible to propose an unfinished or unadapted product to the customer. The iterative design method is used to perfect the design before the software release along the development period, especially during testing phases.	+

	=== Benefits ===		=== Benefits ===

-	~~Advantages related to~~ iterative design are ~~numerous.~~	+	Some advantages of iterative design are:
-		+
	* Inconsistencies around application design are detected earlier than with a traditional development method.		* Inconsistencies around application design are detected earlier than with a traditional development method.
-	* Most ~~of the~~ usability issues will be solved: ~~we don't have to patch the application, we~~ release ~~directly a perfectly adapted product.~~	+	* Most usability issues will be solved: less post release patches and upgrades
	* Better understanding of users needs		* Better understanding of users needs
-	* Testing phase is easier to plan as the testing team will proceed by iterations~~: iterative design fits perfectly with AGILE development methods.~~	+	* Testing phase is easier to plan as the testing team will proceed by iterations
	* Better knowledge about the current project status: good visibility of the project advancements		* Better knowledge about the current project status: good visibility of the project advancements
-	* ~~Keep an~~ history of mistakes ~~done in the past~~ to ~~do better on~~ future projects	+	* Provides a history of mistakes made to help with future projects

	=== Disadvantages ===		=== Disadvantages ===

-	One of the problem of iterative design is ~~its~~ cost if you exaggerate the number of iterations. Indeed, each iteration ~~takes a lot of~~ time and time is critical ~~as expensive~~ in software development. ~~It will avoid patching the software in the future but can become really expensive if too many iterations are performed.~~ Jakob Nielsen has realized experiences about the number of iterations that should be performed by a user interface designer. According to his opinion, developers should realize three iterations to obtain an interface adapted to users needs without spending a lot of time and money.	+	One of the problem of iterative design is it's cost, if you exaggerate the number of iterations. Indeed, each iteration can be time consuming, and time management is critical in software development. Jakob Nielsen has realized experiences about the number of iterations that should be performed by a user interface designer. According to his opinion, developers should realize three iterations to obtain an interface adapted to users needs without spending a lot of time and money.

	== References ==		== References ==

Adamssw: frequently saving your work prevents losses due to malfunction and reduces excess frustration

2009-11-23T20:35:15Z

frequently saving your work prevents losses due to malfunction and reduces excess frustration

← Older revision		Revision as of 20:35, 23 November 2009
Line 46:		Line 46:

	=== Purpose of Testing ===		=== Purpose of Testing ===
-	Testing ~~is believed to serve~~ two main purposes. According to Galitz(Galitz 1997, p. 592):	+	Testing serves two main purposes. According to Galitz(Galitz 1997, p. 592):
	*First, it establishes a communication bridge between developers and users. Through testing, the developer learns about the user’s goals, perceptions, questions and problems. Through testing, the user is exposed to the capabilities of the system early on, before design is solidified.		*First, it establishes a communication bridge between developers and users. Through testing, the developer learns about the user’s goals, perceptions, questions and problems. Through testing, the user is exposed to the capabilities of the system early on, before design is solidified.
	*Second, testing is used to evaluate a product. It can identify potential problems in design at a point in the development process where they can be more easily addressed. Testing also enables comparison of alternative versions of a design element, when a clear direction is not immediately evident. How well the interface and screens meets user needs and expectations can also be assessed.		*Second, testing is used to evaluate a product. It can identify potential problems in design at a point in the development process where they can be more easily addressed. Testing also enables comparison of alternative versions of a design element, when a clear direction is not immediately evident. How well the interface and screens meets user needs and expectations can also be assessed.
Line 54:		Line 54:
	=== Key Reasons to Test ===		=== Key Reasons to Test ===
	* Developers and users possess different models		* Developers and users possess different models
-	* Developer’s ~~Intuitions~~ are not always correct	+	* Developer’s intuitions are not always correct
	* There is no average user		* There is no average user
-	* ~~It’s~~ impossible to predict usability from appearance	+	* It is impossible to predict usability from appearance
-	* Design ~~Standards~~ and guidelines are not sufficient	+	* Design standards and guidelines are not sufficient
	* Informal feedback is inadequate		* Informal feedback is inadequate
-	* Products ~~build~~ in pieces almost always have system-level inconsistencies	+	* Products built in pieces almost always have system-level inconsistencies
-	* Problems found late are more difficult and expensive to fix	+	* Problems found late in the development cycle are more difficult and expensive to fix
	* Problems fixed during development mean reduced support costs later		* Problems fixed during development mean reduced support costs later
	* Advantages over a competitive product can be achieved		* Advantages over a competitive product can be achieved

-	~~This is~~ not an exhaustive list ~~of reasons~~ to ~~test~~, ~~but are~~ key ~~ones that~~ Galitz ~~mentions and are certainly relevant in interface design and usability~~ (Galitz 1997, p.592-593).	+	While not an exhaustive list to justify testing, it highlights the key points made by Galitz. (Galitz 1997, p.592-593).

	=== Analyze and Retest ===		=== Analyze and Retest ===
-	Once the first test has been ~~done~~, it is ~~now~~ important to analyze the data and establish benchmarks for further testing. ~~Problems will be discovered and once they~~ have been resolved to the satisfaction of the designers, the prototype must be changed to reflect this resolution. ~~Once~~ the prototype is ready, ~~another test can~~ be ~~done~~ to gather more data ~~and once again adjust~~ benchmarks and the prototype until ~~designers~~ are satisfied. This is a main component of iterative design.	+	The testing process should be cyclic. Once the first test has been performed, it is important to analyze the data and establish benchmarks for further testing. Fixing old problems produces new problems. Once problems have been resolved to the satisfaction of the designers, the prototype must be changed to reflect this resolution. When the prototype is ready, it must be tested to gather more data, adjusting benchmarks and the prototype until involved parties are satisfied. This is a main component of iterative design and makes user centered design much simpler to incorporate.

	=== Limitations ===		=== Limitations ===

-	Although ~~it seems~~ empirical testing can solve many design problems, it ~~should be noted that testing~~ has its limitations. Rubin and Chisnell (Handbook of Usability Testing 2008, p.25-26), point out that testing is always an artificial situation in the sense that the very act of conducting a study can itself affect the results. Test results do not prove that a product works, in that it is not a guarantee, but only a probability that results were not due to chance. Participants are rarely fully representative of the target population. Testing is not always the best technique to use, since at different stages it may be unnecessary to bring in many participants to reveal the obvious. Testing ~~is just that, a test, which~~ only accounts for hours of use. Even with these limitations Rubin and Chisnell (Handbook of Usability Testing 2008, pg. 26) also note that used correctly, testing will almost always bring to light potential problems, when done carefully and correctly.	+	Although empirical testing can solve many design problems, it has its limitations. Rubin and Chisnell (Handbook of Usability Testing 2008, p.25-26), point out that testing is always an artificial situation in the sense that the very act of conducting a study can itself affect the results. Test results do not prove that a product works, in that it is not a guarantee, but only a probability that results were not due to chance. Participants are rarely fully representative of the target population. Testing is not always the best technique to use, since at different stages it may be unnecessary to bring in many participants to reveal the obvious. Testing only accounts for hours of use, subtle or unusual problems may not be revealed in this environment. Even with these limitations, Rubin and Chisnell (Handbook of Usability Testing 2008, pg. 26) also note that used correctly, testing will almost always bring to light potential problems, when done carefully and correctly.

	== Iterative Design ==		== Iterative Design ==

Adamssw: fixed spelling erors, editing continued

2009-11-23T20:25:02Z

fixed spelling erors, editing continued

← Older revision		Revision as of 20:25, 23 November 2009
Line 26:		Line 26:
	==== Systematic Information Gathering and Analysis ====		==== Systematic Information Gathering and Analysis ====

-	~~Consistancy~~ is a ~~desired~~ attribute in a software ~~system~~, and ~~such an~~ approach should be taken during ~~the~~ development ~~stage in order~~ to ~~assure~~ it. When aquiring user input, developers need to take extra care to ensure that the method of extraction is as consistant as possible. This way, comparisons between user input can be directly made, either quantatively or qualitively. This will avoid ambiguity in the analysis and implementation of user feedback.	+	Consistency is a desirable attribute in a software design, and a systematic approach should be taken during development to encourage it. When aquiring user input, developers need to take extra care to ensure that the method of extraction is as consistant as possible. This way, comparisons between user input can be directly made, either quantatively or qualitively. This will avoid ambiguity in the analysis and implementation of user feedback.

	=== Usability Experts ===		=== Usability Experts ===

-	Experts in the field of usability are important ~~people in~~ the user-centred development cycle. They significantly ease the formalization of developer-client communication, and can provide usability training on several tiers of the development ~~heirarchy~~. Usability experts ~~can~~ work with designers, providing feedback as development ~~happens~~; they ~~can~~ also interact with end users in ways that disambiguate their needs, resulting in feedback that is more ~~helpful~~ for developers and designers. This allows team members to remain focused on their particular areas of expertise, preventing inaccurate or redundant usability information or modifications from accruing.	+	Experts in the field of usability are important contributors to the user-centred development cycle. They significantly ease the formalization of developer-client communication, and can provide usability training on several tiers of the development hierarchy. Usability experts work with designers, providing feedback as development occurs; they also interact with end users in ways that disambiguate their needs, resulting in feedback that is more useful for developers and designers. This allows team members to remain focused on their particular areas of expertise, preventing inaccurate or redundant usability information or modifications from accruing.

	== Empirical Testing ==		== Empirical Testing ==

-	Empirical testing of the user-centered development consists mainly of usability testing with tests that can be quantitatively measured, which focus primarily on user feedback from interaction with the product. These tests are mainly based on user interaction with the interface as opposed to non-user based tests. ~~Some non~~-user based tests are expert review, ~~Compliance Reviews~~, ~~Heuristic Evaluations~~, and ~~Cognitive Walkthroughs~~. These tests are based on the review of an ‘expert’ or check ~~to see~~ if usability of the product ~~satisfy a checklist or group of~~ well-known principles~~, such as~~ Shneiderman’s 8 golden rules or Norman’s 4 principles of usability, ~~among others~~. The main concern of non-user based tests is that users are not actually giving feedback about the interface, instead it is the ‘experts’ who are giving feedback who claim to know what users will accept, which of course is not always the case. Whereas, user-based testing ~~could~~ include ~~user~~ surveys, performance~~-based~~, ~~Think~~-aloud protocol, or Co-discovery learning, ~~with each test having its pros and cons~~.	+	Empirical testing of the user-centered development consists mainly of usability testing with tests that can be quantitatively measured, which focus primarily on user feedback from interaction with the product. These tests are mainly based on user interaction with the interface as opposed to non-user based tests. Non-user based tests are ''expert review, compliance reviews, heuristic evaluations,'' and ''cognitive walk-throughs''. These tests are based on the review of an ‘expert’ and check if the usability of the product satisfies certain criteria based on well-known principles. Examples of the criteria include Shneiderman’s 8 golden rules or Norman’s 4 principles of usability, but could include legal requirements for example. User-based testing can include surveys, performance metric evaluations, think-aloud protocol, or co-discovery learning among others. Centers such as IBM's User Centered Design Center in Markham, Ontario attempt to formalize this process to derive empirical rules of software interface design.
	=== User-based Tests ===		=== User-based Tests ===

Adamssw: edited user behaviour modelling

2009-11-23T20:13:01Z

edited user behaviour modelling

← Older revision		Revision as of 20:13, 23 November 2009
Line 6:		Line 6:

	The objectives of end users must be of paramount importance to software developers, as the purpose of developing software is to accomplish the end user's objectives. User objectives should be ascertained and analyzed in the earliest stages of the software development cycle. From this user-centered perspective, developers can maximize avoiding time wasting diversions that do not provide users with more desired functionality.		The objectives of end users must be of paramount importance to software developers, as the purpose of developing software is to accomplish the end user's objectives. User objectives should be ascertained and analyzed in the earliest stages of the software development cycle. From this user-centered perspective, developers can maximize avoiding time wasting diversions that do not provide users with more desired functionality.
		+

	Early user input will bring focus to the project, and keeping users informed of modifications and additions throughout the software development cycle will help retain that focus. Users help developers keep to their original intentions and developers remain focused on the desired feature set. Problems that arise can be solved with the end user's awareness of the state of the project and more awareness of the impact of their decisions on functionality, budgets and timelines.		Early user input will bring focus to the project, and keeping users informed of modifications and additions throughout the software development cycle will help retain that focus. Users help developers keep to their original intentions and developers remain focused on the desired feature set. Problems that arise can be solved with the end user's awareness of the state of the project and more awareness of the impact of their decisions on functionality, budgets and timelines.
Line 18:		Line 19:
	==== User Behaviour Modelling ====		==== User Behaviour Modelling ====

-	~~While the~~ features provided by a piece of software are important, how users interact with these features ~~should be modelled. When designing a project,~~ the ~~circumstances~~ of the ~~user~~ should be ~~analyzed and modelled in order to provide an interface appropriate to~~ the ~~level of comprehension of the end users. Things such as users~~' work environment, their ~~behaviour~~ characteristics, and the nature of the ~~users~~' work ~~itself should~~ be ~~analyzed and considered when making design decisions; such decisions should~~ be ~~run~~ by users to ~~assure~~ effective ~~progress~~.	+	The features provided by a piece of software are important to the customer, and how users interact with these features is important to the design of the interface. It should be modeled as closely as possible on the user's actual work environment, their behavior characteristics and the nature of the user's work.
		+
		+
		+	Appropriate models that take these factors into account will provide interface designers with a framework that will allow for intelligent interface prototypes to be constructed. These prototypes can be quickly tested by real users and further refinements will quickly lead to an effective design.

	==== Systematic Information Gathering and Analysis ====		==== Systematic Information Gathering and Analysis ====

Adamssw: edited methods of focus/end user input section

2009-11-23T20:06:14Z

edited methods of focus/end user input section

← Older revision		Revision as of 20:06, 23 November 2009
Line 13:		Line 13:
	==== End User Input ====		==== End User Input ====

-	Users ~~as a collective are a~~ complex ~~entity, however focus~~ should remain on ~~their explicit needs in order to deliver effective software. Specifically,~~ the people who will ~~physically~~ use the product ~~should be the ones that are consulted, not a "~~proxy" user meant to represent the user base ~~as a whole~~. A "proxy" user could ~~be defined as a licensee~~ who ~~distributes~~ software ~~across a system~~ but ~~does~~ not use it~~, and/~~or a ~~person who manages users of~~ the ~~software~~. Their ~~feedback~~ rarely contains information relevant to end user experience since they do not ~~use the software themselves~~, even though they might be paying for it or distributing it.	+	Users have complex and diverse needs and wants. Focus in interface design should remain on the people who will actually use the product as part of their work. A ''proxy'' user meant to represent the user base should not be used. A proxy user could easily include groups who have an interest in the software project, but do not actually use it. Examples of these people include systems administrators or managers who only need a minimal interaction with the system.
		+	Their input rarely contains information relevant to end user experience since they do not have a first hand perspective, even though they might be paying for or distributing the software.

	==== User Behaviour Modelling ====		==== User Behaviour Modelling ====

Adamssw: created introduction

2009-11-23T19:58:51Z

created introduction

← Older revision		Revision as of 19:58, 23 November 2009
Line 1:		Line 1:
-	~~Write introduction here~~.	+	User centered development is a process in which the motivators ('''''end users''''') of a software project play a central role in the development decisions of the project. The end users will normally play a key role in interface design and provide a reliable testing group for evaluating functionality. This differs from traditional software design methods in which requirements are gathered early in the process and then software is built from completed requirements documents with minimal end user input. Correctness is determined by comparison to the requirements which may have been incorrect or incomplete.

	== Early Focus on Users ==		== Early Focus on Users ==

Adamssw: edited need for user input section

2009-11-23T19:51:33Z

edited need for user input section

← Older revision		Revision as of 19:51, 23 November 2009
Line 5:		Line 5:
	=== The Need for User Input ===		=== The Need for User Input ===

-	The objectives of ~~the~~ end users ~~should~~ be of paramount importance to software developers, as the ~~the mere existance~~ of ~~a developers~~ software is ~~the~~ accomplish the end ~~users said~~ objectives. ~~As such, user~~ objectives should be ascertained and analyzed in the earliest ~~part~~ of the software development cycle. ~~With~~ this ~~approach~~, developers can maximize ~~the conciseness of their software while simultaneously providing more~~ users with more ~~function~~. Early user input will ~~help~~ bring focus to the project, ~~however~~ users ~~must be kept abreast~~ of ~~further~~ modifications and additions throughout the ~~rest of the~~ software development cycle~~. This way users can be assured~~ that ~~features do not digress from~~ their original intentions and developers ~~can~~ remain focused on the desired feature set as the project ~~inevitably evolves~~.	+	The objectives of end users must be of paramount importance to software developers, as the purpose of developing software is to accomplish the end user's objectives. User objectives should be ascertained and analyzed in the earliest stages of the software development cycle. From this user-centered perspective, developers can maximize avoiding time wasting diversions that do not provide users with more desired functionality.
		+
		+	Early user input will bring focus to the project, and keeping users informed of modifications and additions throughout the software development cycle will help retain that focus. Users help developers keep to their original intentions and developers remain focused on the desired feature set. Problems that arise can be solved with the end user's awareness of the state of the project and more awareness of the impact of their decisions on functionality, budgets and timelines.

	=== Methods of Focus ===		=== Methods of Focus ===

Santospr: /* Empirical Testing */

2009-11-23T19:27:07Z

Empirical Testing

← Older revision		Revision as of 19:27, 23 November 2009
Line 27:		Line 27:
	== Empirical Testing ==		== Empirical Testing ==

-	Empirical testing of the user-centered development consists mainly of usability testing with tests that can be ~~quantified~~, which focus primarily on user feedback from interaction with the product. These tests are mainly based on user interaction with the interface as opposed to non-user based tests. Some non-user based tests are expert review, ~~compliance reviews~~, ~~heuristic evaluations~~, and ~~cognitive walkthroughs~~. These tests are based on the review of an ‘expert’ or check to see if usability of the product satisfy a checklist or group of well-known principles, such as Shneiderman’s 8 golden rules or Norman’s 4 principles of usability among others. The main concern of non-user based tests is that users are not actually giving feedback about the interface, instead it is the ‘experts’ who are giving feedback who claim to know what users will accept, which of course is not always the case. Whereas, user-based testing could include user surveys, performance-based, ~~think~~-aloud protocol, or co-discovery learning, with each test having its pros and cons.	+	Empirical testing of the user-centered development consists mainly of usability testing with tests that can be quantitatively measured, which focus primarily on user feedback from interaction with the product. These tests are mainly based on user interaction with the interface as opposed to non-user based tests. Some non-user based tests are expert review, Compliance Reviews, Heuristic Evaluations, and Cognitive Walkthroughs. These tests are based on the review of an ‘expert’ or check to see if usability of the product satisfy a checklist or group of well-known principles, such as Shneiderman’s 8 golden rules or Norman’s 4 principles of usability, among others. The main concern of non-user based tests is that users are not actually giving feedback about the interface, instead it is the ‘experts’ who are giving feedback who claim to know what users will accept, which of course is not always the case. Whereas, user-based testing could include user surveys, performance-based, Think-aloud protocol, or Co-discovery learning, with each test having its pros and cons.
	=== User-based Tests ===		=== User-based Tests ===

Santospr: /* References */

2009-11-23T19:20:30Z

References

← Older revision		Revision as of 19:20, 23 November 2009
Line 114:		Line 114:

	* Chisnell and Rubin (2008). ''Handbook of Usability Testing, Second Edition: How to Plan, Design, and Conduct Effective Tests'', Wiley Publishing.		* Chisnell and Rubin (2008). ''Handbook of Usability Testing, Second Edition: How to Plan, Design, and Conduct Effective Tests'', Wiley Publishing.
		+
		+	* Hix and Hartson (1993). ''Developing User Interfaces: Ensuring Usability Through Product & Process'', Wiley Publishing.