Difference between revisions of "Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Organization"

From Slicer Wiki
Jump to: navigation, search
Line 9: Line 9:
  
 
== workflow-support ==
 
== 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'''.
+
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.
  
 
== better organized module list ==
 
== better organized module list ==

Revision as of 20:17, 18 December 2008

Home < Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Organization

Back to Slicer3 UI design

Back to 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 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.

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.