Slicer3:Usability - Revision history

Wjp: /* Collecting user feedback */

2008-12-17T21:52:19Z

Collecting user feedback

Wjp: /* Public suggestion section: Comments about the practice above */

2008-12-17T21:51:28Z

Public suggestion section: Comments about the practice above

Wjp: /* Collecting user feedback */

2008-12-17T21:51:13Z

Collecting user feedback

Wjp: /* Design & Usability Sessions */

2008-12-17T21:16:03Z

Design & Usability Sessions

Marianna: /* Design & Usability Sessions */

2008-05-20T19:03:20Z

Design & Usability Sessions

Marianna: 135 revisions

2008-05-15T17:53:57Z

135 revisions

Wjp: /* Usability Sessions */

2008-01-24T14:25:32Z

Usability Sessions

Wjp: /* 2. Assess the needs of your target user communities */

2007-11-07T16:49:01Z

2. Assess the needs of your target user communities

Wjp: /* 1. Define your target user communities */

2007-11-07T16:48:50Z

1. Define your target user communities

Wjp: /* Recommended light-weight community-centered design practice */

2007-11-07T16:48:36Z

Recommended light-weight community-centered design practice

@@ Line 157: / Line 157: @@
 = Collecting user feedback =
-Please add usability feedback to Slicer3's [http://www.na-mic.org/Bug/my_view_page.php bug tracker], and choose the "usability" category for your report. At the Mantis bug tracker, login (or create an account) and select Slicer3 as your project.
+Please add usability feedback to Slicer3's [http://www.na-mic.org/Bug/my_view_page.php bug tracker], and choose the "usability" category for your report. At the Mantis bug tracker, login (or create an account) and select Slicer3 as your project. Early feature requests can also be found  '''[[Slicer3:FeatureRequests|here.]]'''
 [[Slicer3:Interface_Design|Return to Slicer3 Interface Design and Usability ]]

← Older revision		Revision as of 21:51, 17 December 2008
Line 153:		Line 153:
	* Check Slicer’s [http://na-mic.org/Mantis/main_page.php bugtracker] periodically to see if any problems with your module are being noted by users. Software bugs obviously get the highest priority, but usablity issues also important to address.		* Check Slicer’s [http://na-mic.org/Mantis/main_page.php bugtracker] periodically to see if any problems with your module are being noted by users. Software bugs obviously get the highest priority, but usablity issues also important to address.

−	~~= Public suggestion section: Comments about the practice above =~~

−	~~Please add your comments and suggestions here~~

	= Collecting user feedback =		= Collecting user feedback =

@@ Line 159: / Line 159: @@
 = Collecting user feedback =
-We are collecting '''[[Slicer3:FeatureRequests|Slicer3 feature, conventions and resource requests]]''' from application users and software developers. Appropriate entries from [http://www.na-mic.org/Bug Slicer2's bug tracker] and [http://na-mic.org/Mantis/main_page.php Slicer3's bugtracker] will be periodically added to this repository also. All usability problems should be reported there.
+Please add usability feedback to Slicer3's [http://www.na-mic.org/Bug/my_view_page.php bug tracker], and choose the "usability" category for your report. At the Mantis bug tracker, login (or create an account) and select Slicer3 as your project.
 [[Slicer3:Interface_Design|Return to Slicer3 Interface Design and Usability ]]

← Older revision		Revision as of 21:16, 17 December 2008
Line 161:		Line 161:
	We are collecting '''[[Slicer3:FeatureRequests\|Slicer3 feature, conventions and resource requests]]''' from application users and software developers. Appropriate entries from [http://www.na-mic.org/Bug Slicer2's bug tracker] and [http://na-mic.org/Mantis/main_page.php Slicer3's bugtracker] will be periodically added to this repository also. All usability problems should be reported there.		We are collecting '''[[Slicer3:FeatureRequests\|Slicer3 feature, conventions and resource requests]]''' from application users and software developers. Appropriate entries from [http://www.na-mic.org/Bug Slicer2's bug tracker] and [http://na-mic.org/Mantis/main_page.php Slicer3's bugtracker] will be periodically added to this repository also. All usability problems should be reported there.

−	~~= Design & Usability Sessions =~~

−	* [[ Slicer3:ApplicationUsabilitySession \| Application GUI sessions ]]
−	* [[ Slicer3:EditorUsabilitySessions \| Editor Module sessions ]]
−	* [[ Slicer3:FiducialsUsabilitySessions \| Fiducials functionality ]]

	[[Slicer3:Interface_Design\|Return to Slicer3 Interface Design and Usability ]]		[[Slicer3:Interface_Design\|Return to Slicer3 Interface Design and Usability ]]

@@ Line 166: / Line 166: @@
 * [[ Slicer3:EditorUsabilitySessions | Editor Module sessions ]]
 * [[ Slicer3:FiducialsUsabilitySessions | Fiducials functionality ]]
 [[Slicer3:Interface_Design|Return to Slicer3 Interface Design and Usability ]]

← Older revision	Revision as of 17:53, 15 May 2008
(No difference)

@@ Line 161: / Line 161: @@
 We are collecting '''[[Slicer3:FeatureRequests|Slicer3 feature, conventions and resource requests]]''' from application users and software developers. Appropriate entries from [http://www.na-mic.org/Bug Slicer2's bug tracker] and [http://na-mic.org/Mantis/main_page.php Slicer3's bugtracker] will be periodically added to this repository also. All usability problems should be reported there.
-= Usability Sessions =
+= Design & Usability Sessions =
 * [[ Slicer3:ApplicationUsabilitySession | Application GUI sessions ]]

@@ Line 70: / Line 70: @@
 Once you’ve identified your target audience(s), take some time to develop an understanding of how each distinct community will use your software. This step is essential for meeting both the technical and usability requirements of a user community. Every user group is unique; empirical study is the only approach to a good understanding of your users – how they think about what they do, how they accomplish their work and what sets of needs reside within that framework.
-A community-centered design approach considers people’s (likely diverse) background and experience, needs and skill levels, tasks that must be accomplished, the environmental conditions, pressures and risks under which users work from the beginning and throughout the design process. With this information framing your design and implementation, you’re very likely to develop a software product that’s more appropriate and usable for your target community, and promote both its potential reach across applications and the longevity of its usefulness.
+A user-centered design approach considers people’s (likely diverse) background and experience, needs and skill levels, tasks that must be accomplished, the environmental conditions, pressures and risks under which users work from the beginning and throughout the design process. With this information framing your design and implementation, you’re very likely to develop a software product that’s more appropriate and usable for your target community, and promote both its potential reach across applications and the longevity of its usefulness.
 It’s most likely that you’ll find your future users very happy to spend time talking with you about their research, what their current tools and workflows are like, the technical challenges they present, and what kinds of tools might address them. You may understand these things at an overview level, but the richest information is often revealed in the details; it’s almost always worth spending time to listen. Moreover, this discovery process often reveals new ideas that you may want to include in this or another project.

@@ Line 48: / Line 48: @@
 ===1. Define your target user communities ===
-The most basic requirement of a user-centered software design practice is a thorough understanding of who the target audience is. Our Slicer3 development funding designates the following communities to be among our core user groups, though the package is used in many other scenarios as well. In design and development of Slicer’s codebase, we're targeting these core communities and types of users (hence community-centered), but we welcome and encourage input from any others.
+The most basic requirement of a user-centered software design practice is a thorough understanding of who the target audience is. Our Slicer3 development funding designates the following communities to be among our core user groups, though the package is used in many other scenarios as well. In design and development of Slicer’s codebase, we're targeting these core communities and types of users (hence user-centered), but we welcome and encourage input from any others.
 '''Core Slicer3 user communities: '''

← Older revision		Revision as of 16:48, 7 November 2007
Line 43:		Line 43:
	Read through the recommended practice described below; it probably won't surprise you. Most of the strategies it promotes are quite common in commercial software development efforts, where unhappy users leads to an outcome more easily measured than in free, OSS efforts. Think about how the process will fit into your project and your project timeline. The basic pattern is scalable, so you can apply it in a manner appropriate to your application.		Read through the recommended practice described below; it probably won't surprise you. Most of the strategies it promotes are quite common in commercial software development efforts, where unhappy users leads to an outcome more easily measured than in free, OSS efforts. Think about how the process will fit into your project and your project timeline. The basic pattern is scalable, so you can apply it in a manner appropriate to your application.

−	== Recommended light-weight ~~community~~-centered design practice ==	+	== Recommended light-weight user-centered design practice ==