Difference between revisions of "Karma/Assessment"

From Sugar Labs
Jump to navigation Jump to search
m
 
(One intermediate revision by the same user not shown)
Line 2: Line 2:
 
''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.
 
''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.
  
== requirements ==
+
== Types of Assessment implementations ==
=== basic requirements ===
+
=== [1] direct feedback ===
* store everything the student does in a lesson
 
  
=== advanced requirements ===
+
* 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 ===
  
=== nice to have's ===
+
* assessment stored on user's system
* central teachers access to all available student assessments
+
* 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 ==
 
== To-Dos ==

Latest revision as of 06:23, 18 August 2009

Please also see Bryan's blog post on this topic and 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:
    • within a lesson
    • within Chakra
      • if possible aggregrate assessments from all the currently available lessons
  • places to store the assessment in (non-exclusive):
    • browser
      • cookies (?)
      • localStorage
      • Google Gears
    • Journal
    • Moodle