Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Organization - Revision history

Wjp: /* better organized module list */

2008-12-21T18:47:41Z

better organized module list

Wjp: /* better organized module list */

2008-12-19T23:34:55Z

better organized module list

Wjp: /* Priority items: (blocking project progress) */

2008-12-19T21:28:51Z

Priority items: (blocking project progress)

Wjp: /* User Experience */

2008-12-19T21:28:05Z

User Experience

Wjp: /* better organized module list */

2008-12-18T20:18:38Z

better organized module list

Wjp: /* workflow-support */

2008-12-18T20:18:23Z

workflow-support

Wjp: /* workflow-support */

2008-12-18T20:17:58Z

workflow-support

Wjp: /* User Experience */

2008-12-18T20:17:35Z

User Experience

Wjp at 22:22, 17 December 2008

2008-12-17T22:22:17Z

Wjp: New page: Back to Slicer3 UI design Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning | Tractography proj...

2008-12-17T19:46:58Z

New page: Back to Slicer3 UI design Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning | Tractography proj...

New page

Back to [[Slicer3:UIDesign | Slicer3 UI design]]

Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning | Tractography project]]

@@ Line 13: / Line 13: @@
 == better organized module list ==
 The main pull-down menu exposes a pile of functionality that's loosely structured. A few interesting comments to illustrate the point:
-* Under "Segmentation's" cascade menu are a list of tools for automated segmentation, but the Editor module for manual segmentation isn't listed.
-* Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.
+[[Image:Usability.png]] Under "Segmentation's" cascade menu are a list of tools for automated segmentation, but the Editor module for manual segmentation isn't listed.
-* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users. So, how do we communicate well to everyone?
 == Priority items: (blocking project progress) ==

@@ Line 15: / Line 15: @@
 * Under "Segmentation's" cascade menu are a list of tools for automated segmentation, but the Editor module for manual segmentation isn't listed.
 * Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.
-* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users.
+* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users. So, how do we communicate well to everyone?
 == Priority items: (blocking project progress) ==

← Older revision		Revision as of 21:28, 19 December 2008
Line 18:		Line 18:

	== Priority items: (blocking project progress) ==		== Priority items: (blocking project progress) ==
		+
		+
		+	== Proposed plan for addressing issues ==

← Older revision		Revision as of 21:28, 19 December 2008
Line 16:		Line 16:
	* Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.		* Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.
	* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users.		* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users.
		+
		+	== Priority items: (blocking project progress) ==

@@ Line 12: / Line 12: @@
 == better organized module list ==
-The main pull-down menu exposes a pile of fuunctionality that's loosely structured. A few interesting comments to illustrate the point:
+The main pull-down menu exposes a pile of functionality that's loosely structured. A few interesting comments to illustrate the point:
 * Under "Segmentation's" cascade menu are a list of tools for automated segmentation, but the Editor module for manual segmentation isn't listed.
 * Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.
 * As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users.

@@ Line 9: / Line 9: @@
 == workflow-support ==
-Since this kind of analysis is something we want to support, we might support flexible wizards that walk people through a standard but flexible set of steps, and make recommendations about which algorithms to try, as part of the analysis. This mechanism would '''streamline workflow''' and provide a guide for learning Slicer features.
+Since this kind of analysis is something we want to support, we might support flexible wizards that walk people through a standard but flexible set of steps, and make recommendations about which algorithms to try, as part of the analysis. This mechanism would '''streamline workflow''' and maybe provide a guided tour through appropriate Slicer features.
 == better organized module list ==

← Older revision		Revision as of 22:22, 17 December 2008
Line 2:		Line 2:

	Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning \| Tractography project]]		Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning \| Tractography project]]
		+
		+
		+	= User Experience =
		+
		+	DTI analysis involves many of Slicer's provisions, but the overall experience can be like picking through a haystack to find the needles you need. How might we make this easier?
		+
		+	== workflow-support ==
		+	Since this kind of analysis is something we want to support, we might support flexible wizards that walk people through a standard set of steps as part of the analysis. This mechanism would '''streamline workflow'''.
		+
		+	== better organized module list ==
		+	The main pull-down menu exposes a pile of fuunctionality that's loosely structured. A few interesting comments to illustrate the point:
		+	* Under "Segmentation's" cascade menu are a list of tools for automated segmentation, but the Editor module for manual segmentation isn't listed.
		+	* Under "Registration" there are many tools available, but it may not be clear to a user which of these options is appropriate for their datasets.
		+	* As a more general point, module names need to communicate underlying algorithms for some users, and need to communicate what they're best used for to other users.