Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Student projects/Usability issues.

Student projects/Usability issues: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
<p class="note">'''Note''': This page outlines ideas for the Usability issues project. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Talk:Student projects/Usability issues|page comments]].''</p>
<p class="note">'''Note''': This page outlines ideas for the Usability issues project. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Talk:Student projects/Usability issues|page comments]].''</p>


Line 4: Line 5:
The main objective of this project is to detect and solve specific usability issues.
The main objective of this project is to detect and solve specific usability issues.


==Index==
== Index ==
 
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Plan Plan]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Plan Plan]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Timeline Timeline]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Timeline Timeline]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Tasks Tasks]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/FAQ FAQ]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/FAQ FAQ]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Downloads Downloads]
* [https://docs.moodle.org/en/Student_projects/Usability_issues/Downloads Downloads]


==Main tasks==
== Objectives ==
 
* Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.
* Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.
* For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.
* For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.
* Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughts).
* Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughts).
* Create usability tests to find new usability issues (optional).
* Take a look at [http://fluidproject.org/ Fluid Project] (who we are involved with already) to see where some of their components can be used in Moodle (optional).
* Take a look at [http://fluidproject.org/ Fluid Project] (who we are involved with already) to see where some of their components can be used in Moodle (optional).


==To do==
== Status ==
*Classify specific usability issues
TO BE UPDATED
*Identify the solutions
*Create code to solve the problem
*Take a look at Fluid Project
 
==Done==
*AI test
*Usability test
*Research in the tracker, forums, and hitlist
*Research the bibliography


==See also==
==See also==
*[[GSOC/2008]]
*[[GSOC/2008]]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=92862 GSOC: Moodle Usability Guidelines] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=92862 GSOC: Moodle Usability Guidelines] forum discussion


[[Category:Project]]
[[Category:Project]]

Revision as of 22:35, 9 May 2008

Note: This page outlines ideas for the Usability issues project. It's a specification under construction! If you have any comments or suggestions, please add them to the page comments.


The main objective of this project is to detect and solve specific usability issues.

Index

Objectives

  • Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.
  • For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.
  • Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughts).
  • Create usability tests to find new usability issues (optional).
  • Take a look at Fluid Project (who we are involved with already) to see where some of their components can be used in Moodle (optional).

Status

TO BE UPDATED

See also