Student projects/Usability issues/T3: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This project can benefit from the Fluid project in three ways: solving the usability issues mentioned at Fluid project and that have not already been solved, solution of usability errors descrived at [https://docs.moodle.org/en/Student_projects/Usability_issues/T1 Usability issues], design patterns of Fluid which must be considered when adding new functionalities and asking Fuid community about its opinion about Moodle usability problems. | |||
= Moodle's usability issues found in Fluid report = | |||
It has been realized a study about Moodle [http://wiki.fluidproject.org/pages/viewpageattachments.action?pageId=328019 Moodle "UX Walkthrough Procedures and Findings"] | It has been realized a study about Moodle [http://wiki.fluidproject.org/pages/viewpageattachments.action?pageId=328019 Moodle "UX Walkthrough Procedures and Findings"] | ||
In this study, there are some issues that will be solved | In this study, there are some issues that will be solved. The issues found can be classified by some principles. Here a recount of this issues will be made and they will be order by priority in order to solve some of them (the most critical ones): | ||
# Consistency and standards: 5 | |||
# Mixture of errors: 1 | |||
# Match between the system and the real world: 5 | |||
# Recognition rather than recall help: 5 | |||
# Recognition: 1 | |||
# Aethetic and minimalist design: 2 | |||
# Visibility of system status: 2 | |||
# Error prevention: 2 | |||
# User control: 4 | |||
# Flexibility and efficiency: 7 | |||
# Help and documentation: 10 | |||
It must be considered that the issues are explained in detail in the document mentioned above. | |||
= Moodle's usability issues with information of Fluid project = | |||
Moreover, in the fluid project it can be found [http://build.fluidproject.org/ source code] that can be used to solve some usability problems. | |||
= New developments = | |||
The new Moodle functionalities should followed the Fluid design patterns menttioned at the [http://wiki.fluidproject.org/display/fluid/Design+Patterns design patterns page] at they must be considered in Moodle's new developments. | |||
= New developments = | |||
It can be useful to ask Fuid community about its opinion about Moodle usability problems using [http://fluidproject.org/index.php/mailing-lists Fluid mailing lists]. |
Revision as of 18:54, 10 July 2008
This project can benefit from the Fluid project in three ways: solving the usability issues mentioned at Fluid project and that have not already been solved, solution of usability errors descrived at Usability issues, design patterns of Fluid which must be considered when adding new functionalities and asking Fuid community about its opinion about Moodle usability problems.
Moodle's usability issues found in Fluid report
It has been realized a study about Moodle Moodle "UX Walkthrough Procedures and Findings"
In this study, there are some issues that will be solved. The issues found can be classified by some principles. Here a recount of this issues will be made and they will be order by priority in order to solve some of them (the most critical ones):
- Consistency and standards: 5
- Mixture of errors: 1
- Match between the system and the real world: 5
- Recognition rather than recall help: 5
- Recognition: 1
- Aethetic and minimalist design: 2
- Visibility of system status: 2
- Error prevention: 2
- User control: 4
- Flexibility and efficiency: 7
- Help and documentation: 10
It must be considered that the issues are explained in detail in the document mentioned above.
Moodle's usability issues with information of Fluid project
Moreover, in the fluid project it can be found source code that can be used to solve some usability problems.
New developments
The new Moodle functionalities should followed the Fluid design patterns menttioned at the design patterns page at they must be considered in Moodle's new developments.
New developments
It can be useful to ask Fuid community about its opinion about Moodle usability problems using Fluid mailing lists.