Roadmap of development

This document specifies the currently envisioned steps in the project alongwith the status of various activities.

In progress - blue
Completed - Red


  1. Understanding the Turbine framework (
  2. Design of top level flow diagram between modules (containing actions and screens) for the system.
  3. Implementation of administrator interface - for course creation, and general management.
  4. Instructor interface implementation
  5. Student interface implemenation
  6. testing of subsystems - always ongoing process
  7. Integration of chat and whiteboard server (Babylon).
The features envisioned in the system.
  1. Authentication - provided inherently by Turbine framework.
  2. course content upload facility for instructor. The browsing facility for student - done
    1. Another immidiate requirement is the creation of the representation of whole directory structure (currently not given with the design document) using an xml file where the directories are represented as elements of an xml file. The xml files can be modified and used for creating different directory structure. The same system can still manage a different directory structure since, the directory structure is coded in xml file.
  3. Interface for administrator
    1. creation of new courses
    2. addition of instructors
    3. addition of students
    4. modifying passwords of instructors, students.
    5. backup operations of courses.
    6. deletions of courses
    7. managing logs
  4. Academic Admin Interface (currently this is done by OARS at IIT Kanpur)
    1. managing course registrations
      1. addition of students
      2. deletion of students
    2. Creating Prerequisite definitions.
    3. verification of prerequisites
  5. Instructor interface
    1. creating of content objects
    2. uploading course material (individual files)
    3. uploading of content (zipped format)
    4. publishing of content after selecting from zipped archive
    5. Multiple Upload and publishing separation (via xml descriptors of content object).
    6. creation of metadata information about the content object
    7. Uploading of content object, with its metadata
    8. creating and maintaining metadata about the course material (as per SCORM standard).
    9. Creation of learning path for a course via content objects.
    10. Creation and management of question banks for facilitating the self test.
  6. Calendar tool for time management - personal and course specific.
  7. Integration of chat tool (any tool - open source free ware, should be pluggable)
  8. Integration of whiteboard tool (any open source free ware, should be pluggable)
  9. Integration of local mail system (any open source free ware, should be pluggable)
  10. design and Integration of discussion board system
  11. design and Integration of notification system.
  12. version control system options for instructor for course content development (possible contender -
  13. communication controller design - extending it to multiserver architecture : This will help each collaborating partner to maintain their own server if they wish which together looks as single entity for students. They will be separate entity only for system administrators.
  14. rpm packaging for autoinstallation scripts
  15. Autoinstaller for windows machines.
More things will come on roadmap.

© 2002-2004 ETRG Kanpur
last modified on 05 August 2004, 1103 hrs