Line 1: |
Line 1: |
− | ''Please also see [http://karmaproject.wordpress.com/2009/07/06/assessment-is-the-killer-app/ Bryan's blog post] on this topic.'' | + | <noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> |
| + | ''Please also see [http://karmaproject.wordpress.com/2009/07/06/assessment-is-the-killer-app/ Bryan's blog post] on this topic and [http://lists.sugarlabs.org/archive/sugar-devel/2009-July/017281.html NoiseEHC's e-mail] for some related information. |
| + | |
| + | == Types of Assessment implementations == |
| + | === [1] direct feedback === |
| + | |
| + | * direct on-screen feedback (e.g. how many quesions have been solved correctly and incorrectly, how long it took to complete an exercise, etc.) |
| + | |
| + | === [2] stored locally === |
| + | |
| + | * assessment stored on user's system |
| + | * available from within each lesson |
| + | * overview available in Chakra ('''nice to have''') |
| + | * assessment also available for other activities via Journal ('''very nice to have''') |
| + | |
| + | ==== [2.5] ==== |
| + | |
| + | * teacher activity that collects and displays pupil's assessment |
| + | |
| + | === [3] stored centrally === |
| + | |
| + | * assessment stored centrally |
| + | * either on per class / per grade / per school basis |
| + | * storage on XS or in Moodle |
| + | * teacher's view allows for quick look at class / grade / pupil performance |
| + | |
| + | == To-Dos == |
| | | |
| * '''user interface''': | | * '''user interface''': |
Line 8: |
Line 34: |
| ** browser | | ** browser |
| *** cookies (?) | | *** cookies (?) |
| + | *** localStorage |
| *** Google Gears | | *** Google Gears |
| ** Journal | | ** Journal |
| ** Moodle | | ** Moodle |
− | => how can teachers access a students' assessments?
| |