[[BackLinksMenu]]

[[TicketQuery(summary=PLATFORM_NFR_USABILITY_R1, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]

= Analysis =
== Overview ==
== Task requirements ==
 * Review and collect tasks that improve usability of the product and link them here
  * List exact improvements that will be accomplished
 * Collect all keyboard shortcuts that are available.
  * A strategy to prevent this "undocumented feature disconnect" is to automatically generate a list of keyboard shortcuts from their definitions in the code.
 * Create a Menu item in Help menu that links to a list of all keyboard shortcuts.
 * Review and update PLATFORM_NFR_USABILITY
  * Add a discoverability section (see Implementation Idea section)
== Task result ==
 * Updated wiki pages
 * List of keyboard shortcuts
 * Code
 * Task list that usability improvement depends on 
== Implementation idea ==
{{{
Discoverability

Even if software is usable as per the above considerations, it may still be hard to learn to use. Other questions that must be asked are:

    * Is the user ever expected to do something that is not obvious? (e.g. Are important features only accessible by right-clicking on a menu header, on a text box, or on an unusual GUI element?)
    * Are there hints and tips and shortcuts that appear as the user is using the software?
    * Should there be instructions in the manual that actually belong as contextual tips shown in the program?
    * Is the user at a disadvantage for not knowing certain keyboard shortcuts? A user has the right to know all major and minor keyboard shortcuts and features of an application.
    * Is the learning curve (of hints and tips) skewed towards point-and-click users rather than keyboard users?
    * Are there any "hidden" or undocumented keyboard shortcuts, that would better be revealed in a "Keyboard Shortcuts" Help-Menu item? A strategy to prevent this "undocumented feature disconnect" is to automatically generate a list of keyboard shortcuts from their definitions in the code.

}}}
Tasks that affect usability
 * Help related tasks (help, tooltip)
 * Keyboard related tasks (shortcuts)
 * Tasks that will simplify GUI/feature
== Related ==
^(Add links to related tasks that could be useful or helpful.)^

== How to demo ==
^(Provide instructions for demonstration of the task.)^

= Design =
^(Describe your design here.)^

= Implementation =
^(Describe and link the implementation results here (from the wiki or the repository).)^

= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)