Self-assessment activity using the question bank: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
I have gone through the Ideas page and I have also read the information about the same on Tim Hunt's blog which depicts how the project should look like. | I have gone through the Ideas page and I have also read the information about the same on Tim Hunt's blog which depicts how the project should look like. | ||
[http://tjhunt.blogspot.in/2011/09/what-i-want-to-build-next.html | [http://tjhunt.blogspot.in/2011/09/what-i-want-to-build-next.html What I want to Build Next] | ||
== Schedule == | == Schedule == | ||
Revision as of 18:24, 2 June 2013
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
| Self-assessment activity using the question bank | |
|---|---|
| Project state | Community bonding period |
| Tracker issue | CONTRIB-4334 |
| Discussion | XXX |
| Assignee | Jayesh Anandani |
GSOC '13
Introduction
Self-assessment is the ability of a student to observe, analyze, and judge one’s performance on the basis of criteria and determine how one can improve it.
I have gone through the Ideas page and I have also read the information about the same on Tim Hunt's blog which depicts how the project should look like. What I want to Build Next
Schedule
- Timeline
- I have divided the entire coding period into two main phases.
- The first phase spans from (17th June 2013- 29th July, 2013).
- The second phase from (2nd August, 2013 – 15th September, 2013).
- There is also a pre-phase and a post-phase.
- Pre-phase (27th May 2013-17th June 2013)
- I plan on reading the documentation regarding Quiz module, interacting with the community and gathering all the pre-requisites about the project in the Pre-phase. I also plan on making a user documentation about the project which would be exposed to community in order to get feedback. Also a track of all day to day activities would be kept through a blog.
- First-phase (17th June 2013 - 29th July 2013)
- 17th June-30th June: Design Student User Interface
- 1st July-15th July: Hardcode student's side and test it for various cases.
- 16th July-28th July: Implement feedback mechanism at Student's side.
- 29th July-31st July: Preparing for midterm evaluation.Reserved period for any final discussion and changes to the project before the mid evaluation.
- Second-phase (2nd August 2013-15th September 2013)
- 2nd August-11th August:Create a UI at teacher’s side and add functionalities for the same.
- 12th August-25th August: Create Database tables and change to code to dynamic.
- 26th August-8th September: Start testing of the project for various possible options and complete the user documentation.
- 8th September-15th September: Reserved time period for finalizing the project.
- Post-phase (15th September 2013-22nd September 2013)
- This is the period before the final submissions. This period is reserved for final testing, minor bug fixes, user documentation of the entire project, review from the mentors and minor changes to the code. Finalize all the implementation and submit the code to both Moodle and Google.
