Slicer3:Usability - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T17:39:16Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Marianna: Unprotected "Slicer3:Usability"

2008-05-20T19:04:07Z

Marianna: Replacing page with ''''Note:''' We are migrating this content to the slicer.org domain - The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:Usability ...'

2008-05-20T19:03:56Z

Replacing page with '<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:Usability ...'

Show changes

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

Wjp: /* Slicer3 design and usability goals */

2007-11-07T16:48:25Z

Slicer3 design and usability goals

Wjp: /* User-centered design for Slicer3 */

2007-11-07T16:47:51Z

User-centered design for Slicer3

Wjp: /* Community-centered design for Slicer3 */

2007-11-07T16:47:33Z

Community-centered design for Slicer3

← Older revision		Revision as of 17:39, 10 July 2017
Line 1:		Line 1:
−	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [~~http~~://www.slicer.org/~~slicerWiki/index.php~~/Slicer3:Usability here]</font></big>	+	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Usability here]</font></big>

@@ 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 ==

← Older revision	Revision as of 19:04, 20 May 2008
(No difference)

← Older revision		Revision as of 16:48, 7 November 2007
Line 37:		Line 37:


−	Modules that hit these marks should maximize the reach of a developer’s research, design, and programming effort, offer contributing agencies, institutions, and individuals the maximum impact for their investment, and provide the user community with cutting-edge functionality that they find satisfying to use. The Slicer community ultimately leaves the choice about design and implementation process to contributing developers, and the recommendations in this document are not enforced. Since we believe that incorporating ~~community~~-centered design will improve Slicer overall, developers are strongly encouraged to adopt this light-weight and flexible practice, and adapt it to fit their environment and project timeline.	+	Modules that hit these marks should maximize the reach of a developer’s research, design, and programming effort, offer contributing agencies, institutions, and individuals the maximum impact for their investment, and provide the user community with cutting-edge functionality that they find satisfying to use. The Slicer community ultimately leaves the choice about design and implementation process to contributing developers, and the recommendations in this document are not enforced. Since we believe that incorporating user-centered design will improve Slicer overall, developers are strongly encouraged to adopt this light-weight and flexible practice, and adapt it to fit their environment and project timeline.

	== How to apply these recommendations ==		== How to apply these recommendations ==

← Older revision		Revision as of 16:47, 7 November 2007
Line 6:		Line 6:


−	Historically, much of Slicer2's underlying architecture and user interface were developed by a large (and distributed) community over time, lead and framed by strong technology vision, but without a coupled interface/interaction design and usability effort. Wherever possible, we are encouraging a ~~community~~-centered design approach for Slicer3's application and software modules. This approach is built on five principles:	+	Historically, much of Slicer2's underlying architecture and user interface were developed by a large (and distributed) community over time, lead and framed by strong technology vision, but without a coupled interface/interaction design and usability effort. Wherever possible, we are encouraging a user-centered design approach for Slicer3's application and software modules. This approach is built on five principles:

← Older revision		Revision as of 16:47, 7 November 2007
Line 3:		Line 3:


−	= ~~Community~~-centered design for Slicer3 =	+	= User-centered design for Slicer3 =