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

2017-07-10T17:44:17Z

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

Melonakos at 21:45, 5 November 2008

2008-11-05T21:45:58Z

Andy: Update from Wiki

2006-12-18T13:19:09Z

Update from Wiki

New page

= Project =

Design a new interface for Slicer3

[[Image:2006_Programming_Half_Week_Slicer3UI.ppt|Image:2006 Programming Half Week Slicer3UI.ppt]]

Please look [[Slicer3:Interface_Design|here]] for details about the UI design effort.

= Goals =

# Build a UI for Slicer that is technically excellent, that users love to use, and developers find easy to implement.
# Be able to describe a process for incorporating user-centered design and usability engineering into an open-source extreme programming software development effort.

== sub-goals for the AHM ==

# Get some hands-on experience with KWWidgets
# Agree on what supporting technology to use (GUI toolkit, in particular) as these will impact UI design and engineering
#* Currently favored toolkits are KWWidgets and Qt
# Begin discussion about how user-centered design and usability engineering can be integrated with Slicer3 engineering. For instance:
#* How do developers feel about conforming to design guidelines (see [http://developer.gnome.org/projects/gup/hig/ GNOME HIG 2.0])?
#* How do developers feel about submitting tools for user-testing, and refining tools to address user feedback?
#* What are developers' priorities about the UI tools they'll be using?
#* Do users at the AHM have usability comments or requirements they want to offer?
#* Should we develop a mechanism to track usability bugs, as distinguished from functionality bugs?
#* Should we develop a mechanism (mailing list) for users to communicate usability comments?
#* Can/should we develop a mechanism for channeling user-testing results back to particular developer(s)?
#* Should we develop "bare-bones" floating design consultancy, providing early user studies, user modeling, UI design and testing?
#* How do we measure or assess the productive benefits of our efforts?
# Learn about existing design processes / usability efforts inside other NA-MIC affiliated projects (''i.e.'' LONI)
# Begin defining interaction framework for Slicer3's overall UI and qualify ways to support and reflect developing data model and scene description language.
# Begin compiling a formal set of Slicer3 technical requirements
# Begin compiling a formal set of Slicer3 user requirements

= Challenge: OSS, user-centered design and usability engineering =

In commercial software development, user-centered design and usability engineering are strongly integrated into the product development cycle, and they strongly shape the form and behavior of the software artifact. Interface, interaction and usability testing processes are well defined. It's accepted that technically excellent and usable software that promotes a good user experience wins a broader devoted user community.

Processes for incorporating user-centered design and usability engineering into OSS efforts, on the other hand, are still young and developing. Recent successful efforts (like GNOME, KDE, Mozilla, ''etc.'') illustrate the good results that come from promoting usability concerns in their projects. For the most part, these projects began by developing usability guidelines and by performing some usability testing and channeling the results back to developers.

We'd like to leverage what these projects have learned in the Slicer3 effort, specifically in the context of a '''medical image analysis and visualization''' software package, with '''highly specialized users''' and also '''highly specialized developers'''.

The initial challenge for the Slicer3 UI effort is to understand Slicer users and developers, and to evolve a user-centered design and usability engineering processes that serve the interests of ''both'' the Slicer development effort and end-user artifact.

Since the Slicer3 project is scheduled on a tight timeframe, some of the ongoing challenges will be:

* finding ways to target user testing and constructively use the resulting feedback;
* measuring the impact these efforts have on usability and user experience.

We intend to publish our processes and experiences in appropriate journals so that other OSS efforts may leverage what we find to be productive.

= Preliminary approach =

# Get some hands-on experience with KWWidgets; work with broad UI team to make GUI toolkit choice.
# We're developing a prototype design process
# Begin discussion about how user-centered design and usability engineering can be integrated with Slicer3 engineering. For instance:
# Wiki-based forum for collecting developer's responses to design guidelines, submitting tools for user-testing, working with UI designer, and refining tools using user feedback.
# Wiki-based forum for users to submit their broad comments on Slicer3 usability.
# Work with Slicer web-presence team to discuss mechanisms for usability comments and bugs, for channeling user-testing results back to developers.
# Not sure how to measure or assess productive benefits of our usability/design effort.
# Learn about existing design processes / usability efforts inside other NA-MIC affiliated projects (''i.e.'' LONI)

= Technical Requirements =

this space to capture all suggestions

= User-requirements =

this space to capture all suggestions

= Developer requirements =

this space to capture all suggestions

@@ Line 5: / Line 5: @@
 [[Image:2006_Programming_Half_Week_Slicer3UI.ppt|Image:2006 Programming Half Week Slicer3UI.ppt]]
-Please look [http://www.slicer.org/slicerWiki/index.php/Slicer3:Interface_Design_and_Usability here] for details about the UI design effort.
+Please look [https://www.slicer.org/wiki/Slicer3:Interface_Design_and_Usability here] for details about the UI design effort.
 = Goals =

AHM 2006:ProjectsSlicerUI - Revision history

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

Melonakos at 21:45, 5 November 2008

Andy: Update from Wiki