Difference between revisions of "Math4Team/RIT/Projects/Question Support API"

From Sugar Labs
< Math4Team‎ | RIT‎ | Projects
Jump to navigation Jump to search
(Add milestones)
m
Line 60: Line 60:
  
 
===See Also===
 
===See Also===
[[Math4Team/RIT/Projects/Question_Support_API/Data_Model|Data Model]]
+
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
 
[[Math4Team/RIT/Projects/Question_Support_API/API_Design|API Design]]
 

Revision as of 15:43, 17 April 2009

Question Support API

Project Information

Primary Project Contact Greg Stevens
Project Members Greg Stevens, TODO: Add yourself here...
Source Repository http://git.sugarlabs.org/projects/question-support-api


Motivation

In the RIT class working on the Math4 projects, many proposed activities require a question database of some kind. A common API or library for accessing databases in different formats, stored either locally or remotely, along with a simple mechanism to determine more complex formatting or presentation than simple text (e.g. to include simple graphics or mathematical notation) would cover a majority of the cases where the activity needs some configurable "curriculum data".

Eventually this library could be extended to provide hints, explanations, or walkthroughs for questions, in addition to the basic metadata about level, grouping, difficulty, and subject matter that would be part of the base system.

Envisioned Usage

Consider a simple flash-card-like activity. It presents a question from a list of questions, allows the student to select an answer from the provided answers for the question or to enter their own answer. Then the correct answer is revealed and the student it told whether their answer is correct. If the question has an explanation of the correct answer, the flash-card activity will show the explanation of the correct answer. (Note that this is just a simple usage example, the interaction design of a drilling activity could be very different.)

The flash-card activity would use this proposed Quiz API for the following:

  • Loading the questions from the storage location into memory. This includes any filtering or network lookup to download the questions from a remote resource and select appropriate questions for the student.
  • Determining whether the student has entered a correct answer.

To start with, the library would simply be a time-saving tool for developers needing similar functionality, but as the XS (School Server) becomes more fully developed the library should integrate the functions provided by the XS to enable automated update of course material for the current topic of study so the students can drill material using any tool they prefer, while still reporting progress to the instructor using the XS services.


Milestones

Initial Prototype Phase (1)
Simple implementation, data model not yet nailed down, focus on import and utility to question *consumers*, Like Activities. Initial formats to include MoodleXML, GIFT.
Rigorous Design Phase (2)
Nail down the data model, including developing the 'native' format, probably using a sqlite file mechanism, or other database support, if possible. Freeze the Question object (in terms of required properties, etc.), finalize decisions about URLs for question aquisition. Make sure requirements of other projects *can* be met by the design at this stage.
Full Implementation Phase (3)
Complete the implementation of the import formats, including the 'native' format. Should be usable to other Activity developers at this point (hopefully useful, before now, but all needs should be filled at this point). Export implementation should start now, along with prototyping for an authoring activity. (Collaboration with the reporting team *needs* to happen at this point, as the activity will probably be combined with reporting tools.)
Activity Development Phase (4)
Complete the authoring/reporting activity for the teachers, allowing export to file formats (and possibly *serving* the questions to other XOs; requires support in activities (using the API) to support).

See Also