MathJax

Showing posts with label sprint. Show all posts
Showing posts with label sprint. Show all posts

18 October 2011

Version 0.2

By and a large, the past two weeks have been a success. Admittedly, I tested the boundaries of sanity along the way.

The highlights are that
  • XML templates with linked Python for logic and PNG or ASCIIsvg files for images are now stored in SQL database and can be interpreted by Monassis;
  • templates have tags (based on the chapters and sections of the FHSST books) which can be used to filter the questions the user would like to practice;
  • student, teacher and author accounts exist, with students potentially belonging to class lists, each associated with a teacher.

The only bits that didn't make it in during the sprint are the reporting bits.

I'm about to show a demo to a group of teachers (in about 1 hour) and again some time tomorrow or Thursday to another group. Hoping to get some feedback from that.

04 October 2011

Sprint: Structure and User Management

The time has come for the next round of all-out coding to push the exam practice system to the next stage of usefulness. The goal is to make it possible for a small number of teachers to have their classes practice for the upcoming exams, and to monitor their students' progress. The target date for showing this v0.2 prototype to a group of teachers is 18 October — exactly 2 weeks from now.

List of features to implement:
  • Structured format for questions. The question templating is still too haphazard and not all question metadata is stored in a way that's easy to extract and process. The logic of questions will still be specified using Python. The question presentation and metadata will go into XML.
  • Hierarchical labels for questions, to make filtering manageable. The tags will be along the following dimensions: topic (e.g. Physics::Mechanics::2d motion::Projectile motion), concepts (e.g. interpreting linear graphs, quadratic equations, rearranging equations), grade level.
  • Many more questions. The structure format should make it easier for other people to help add templated questions. I should focus on whatever will be covered in the grade 10 final exams for mathematics and physics.
  • Teacher and student accounts. Each teacher can set up a class list of students.
  • Reporting to students: total problems completed, percentage answered correctly overall and filtered by topic, ranked list of topics that need practice.
  • Reporting to teachers: same as students, but at both individual student level and average class level.

P.S. The project now has a name: Monassis.

13 September 2011

Sprint: Creating an exam drill system in 2 weeks


In 45 days the first paper for the national senior certificate exam will be written by grade 12 learners across South Africa. That gives me 2 weeks to create a web-based system that will allow learners to practice their exam skills so that they can actually use the system for the last month.

There are, of course, larger goals and I'll write more about these later. In short, this is a really good opportunity to get a bunch of grade 12 learners to provide feedback on an automated assessment and progress tracking system that we can roll out on a larger scale in future.

Components:
  • Templated questions
    • process past papers
    • develop templating language (Python + LaTeX/AsciiMath/MathML + AsciiSvg)
    • build concept map from FHSST TOC and link questions to concepts
  • UI: web-based, using Python + Pyramid + MathJax + AsciiSvg
  • Back-end:
    • Templated question database + API, eventually morphing into the FullMarks API
    • User account management, user history tracking. The user history will be vital in future, for finding correlations between user performance on various concepts and for suggesting revision material based on a user's performance.
  • Community feedback
    • The purpose of the pilot is to build a better system for the following school year.
    • Q&A forum where I can address their issues, and they can help one another. Use www.question2answer.org
    • Notify users of new features or questions on the system.
    • Explicitly solicit post-exam user feedback on how to improve the system.
  • Hosting (Siyavula, Rackspace?), branding, domain. Maybe the last two are not so important for now.