Self-assessment activity using the question bank

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 throught the IDEAS page and have read the information regarding the same, on Tim Hunt's blog about the layout/structure of a project. What I want to Build Next

Schedule

Timeline

• I have divided the entire coding period into two main phases.

1. The first phase spans from (17th June 2013- 29th July, 2013).
2. The second phase from (2nd August, 2013 – 15th September, 2013).
3. 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.

Requirements

Moodle 2.6 is required.

Community Bonding Period

Milestones

1. In Progress-Refine the project proposal with Tim,Jean-Michel and Community.
2. In Progress-Feature Discussion.
3. In Progress-Create mockups.
4. In Progress-Create a Practice Interface Overview.
5. DONE-Attend Orientation meeting.
6. DONE-Add GSOC timeline to moodle calendar(iCal).

Features

The practice module will consist of mainly two interfaces.

Student User Interface

Student will be allowed to:

• Create a new practice session and select choices accordingly(shown in mock-ups).
• See their report of all practice sessions in either tabular manner or graphical manner.
• Download a report of all their practice sessions course wise.

Teacher User Interface

Teacher will be able to:

• Create a new practice accessible by all students.
• Add and update Questions to practice created by teacher.

Coding Period

Milestones

1.Finalize the Interface for student's side.

2.Implement the User Interface for student login.

• Implement the Interface for generating a new practice Session.
• Implement the Interface in which Student's can see details of past sessions in tabular or graphical way.

3.Perform Testing of Student Interface with help of some predefined values.

4.Prepare of mid-term evaluation and look for errors if any.

5.Implement Interface for teacher's side.

• Implement the interface through which teacher can add new practice module.
• Implement the interface through which teacher can add or update the questions in a practice module.

6.Perform Testing of Teacher's Interface with some predefine values.

7.Implement the database for student as well as teacher's Interface.

8.Perform Final Testing.

9.Submit Project.

Practice User Interface Overview

This diagram summarises the various pages that make up the practice user interface.

Credits

• Mentors: Tim Hunt and Jean-Michel Vedrine.

Tracker

• CONTRIB-4334 Practice Module

See also

• Moodle GSoC projects for 2013
• Moodle GSoC Overview page
• Forum Discussion
• GSOC Proposal
• Orignal Idea