Course Management System (Fall 2002)

Course Management Software System (Fall 2002)

Introduction

1. Systems Architecture

1.1 Security
1.2 Reliability
1.3 Scalability

2. Features

2.1 Course Management
2.2 Group Management
2.3 Homework Submissions
2.4 Grade Management

3. Future Developments

Introduction

This document outlines the current Course Management Software (CMS) system deployed for use within the Computer Science department at Cornell University. The content is based on Course Management Software System: Requirements , first drafted in May 2002 by Jayavel Shanmugasundaram.

The CMS system development team for Fall 2002 consists of the following people:

Students: Ilya Rifkin, Chavdar Botev, and Christopher Re
Administrative Staff: Kathy Carpenter
ADM Staff: Dora Abdullah
Faculty: Jayavel Shanmugasundaram, David Schwartz

While still in its preliminary testing stage, the following courses have volunteered to use the CMS system and have provided us with many useful feedbacks:

CS 211, CS 212 (David Schwartz)
CS 414, CS 415 (Jeanna Matthews)
CS 432 (Jayavel Shanmugasundaram)
CS 433 (Johannes Gehrke)

1. Systems Architecture

1.1 Security

Firewall protection: The CMS system runs inside CSUGLab firewall -- MS SQL database server runs on a Windows 2000 Server with all ports closed to outside CS/CSUGLab networks. The Apache web server runs on a Linux host with only http and https ports opened to outside CS/CSUGLab networks.
Kerberos authentication: All users of the system are authenticated using Web Kerberos authentication mechanism (CUWebAuth), using Cornell NetID and password..
Support for different roles: The system supports different roles for users: profs, staff, TA, students. A user logged in with a given role allowed to access consistent with that role. For example, a student is allowed to see his or her grades, and not the grades of others.

1.2 Reliability

Reliability of data: Since all course-critical data (such as grades) will be stored in the CMS system, the reliability of the system is of paramount importance. To meet this requirement we use a commercial database system, Microsoft SQL Server for all data management tasks. Computer Science department already has licenses for Microsoft SQL Server, thus the choice.
Backup: The database is backed up using Microsoft SQL Management tool with full backup scheduled every morning and hourly incremental until midnight. The static DB backup-file is then backed up onto tape via CSUGLab Networker backup system, which runs everyday between midnight and early morning. The homework submission files on the Web server are also backed up onto tape every night via CSUGLab Networker backup system.

1.3 Scalability

Scaling to a large number of users: With the new web server hardware, the system should be able to handle the load for a large number of students' homework submissions, especially near assignment deadlines.
Scaling to a large number of courses: If the course management system is successful, it is conceivable that a large number of CS courses will end up using the system. If the current web server cannot handle the load for large courses, it is possible that we will dedicate each large course with its own web server but using the same database backend.

2. Features

This section describes some of the features available in the current system. If you would like to find more detailed options in each feature, please contact one of us and we will set you up on the development/test system and assign you different roles using the test course web and database.

2.1 Course Management

Admin course setup: This is the web front-end for ADM to setup a course and assign "prof" access type to instructor of the course.
Roles Management: User with acess type "prof" can assign staff or TA appropriate roles, as necessary.
Class enrollment: User with access type "prof" or "staff" can add or delete students from the course list.
Assignment Setup: In order for the students to submit homework, the instructor must first create an assignment and configure homework submissions. Only "prof" access type can setup an assignment.

2.2 Group Management

Group management feature is especially important for courses with group projects. The following features are currently available:

Ability to create groups: The system allows students to automatically create groups which are mutually agreed upon. It also enforces the condition such that each student is a member of exactly one group for a given assignment.
Integration with homework submissions: Any member of a group can submit homework.
Integration with grade management: The system supports grade management for groups, and track how the group grade translates into individual student grades.
Group Maintenance: Invariably, students either switch groups, or drop out from a group altogether. The system supports group deletion prior to submitting homework.

2.3 Homework Submissions

The system supports the following features:

Submissions file format: The system accepts homework submissions as it is, i.e. it supports multiple file formats. However, we recommend that instructors ask students to submit files in tarred or zipped format.
Automatically validate submissions: The system validates submission by listing the file size and date, however it doesn't give immediate feedback on faulty submissions.
Submissions before deadline: The system disallow submissions after a set deadline. A grace period can be used to allow homework submission shortly after the deadline without penalty.
Online web access to submission files: The system allows prof/staff/TAs to download assignment submissions from the web.

2.4 Grade Management

Some of the grading options available in the current system are given below:

Roles and grading: Grading options are enabled for the following roles (access type):

prof - enter and modify grades for all groups and assign TAs to groups
staff - enter and modify grades for all groups
TA - enter and modify grades for assigned groups
student - view his/her group scores and own scores/grades for all assignments
Graded and Ungraded Assignments: The system separates the listing of Graded and Ungraded Assignments. "prof" and "staff" can view the new (Ungraded) Assignments only after the deadline so grading can be done in a consistent manner. All Graded Assignments scores listings are available by groups as well as individuals.
Grade Comments: Comments can be typed right into the comments field or uploaded.
Grade History: Individual and Group grades history are logged and viewable by prof/staff/TA.
Regrade Requests: Students regrade requests go into a regrade table, viewable by prof/staff/TA.

3. Future Developments

Here are wish lists from various sources in random order:

add sorting capability to all fields (it's important to be able to sort by grade for a specific assignment/exam)
add count and median to grade statistics in student grade screen
add mechanism for students to report grade discrepancies
add "graded by" field so the student would know who actually graded the assignment
email notification to the prof., TA or staff when a student puts in a Regrade request
allow the program to collect an assignment, even if it is past the deadline. This leaves the option for the prof. to count the assignment if the student has an acceptable excuse.
allow manual group and membership creation. This is related to the late submission issue. However, the problem becomes more complicated if the students didn't create and join a group prior to the deadline. Not only that they can't submit homework online, prof/staff/TA can't give the non-existing group a score. The work-around is entering the group and members manually into the database.

Compiled by: Dora Abdullah, October 2002.