SUMS-ideas

History

Version (most recent first) Date Changer Change
v1.2 9th May 2008 Jim Reviewed and signed off on the requirements.
v1.1 9th May 2008 Mathieu Revised draft of requirements based on Javi's work
v1.0 23th November 2006 Javi first draft

Introduction

Aim

SUMS-allocation is the part of the overwall SUMS system that makes the link between the triplet Student - Project - Supervisor. It also assigns a moderator to the project and a cohort to the student.

Key personnel

Responsible owner

Jim Briggs

Design authority

Jim Briggs

Development team

Mathieu Slosar

Future proofing

SUMS-register must integrate with the overall SUMS system.

Requirements

Entities and attributes

Entity Attributes Relationships
Person
  1. Key
  2. Forename
  3. Surname
  4. Username
  1. Supervisor on a project (to User and Final Project)
  2. or Supervised on a project (to User and Final Project)
  3. Moderator on a project (to User and Final Project)
  4. or Moderated on a project (to User and Final Project)
  5. Cohort
FinalProject
  1. Key
  2. Title
  1. Cohort
Cohort
  1. Key
  2. Name
 

Functionality

1 Requirement Type Status Change request(s)  
1

Students can edit their choices for projects allocation until a date defined in the cohort

M1      
1.2 Project ideas can be sorted by title, theme, keywords, owner, etc. M2      
1.3

Students can select one or more project ideas which interest them to make a short list.

M1      
1.3.1

The maximum size of the shortlist can be defined in the cohort.

M3      
1.3.1.1 An initial (default) value of the maximum shortlist size is 6. M3      
1.4

The ideas on a short list are ranked from most interested to least.

The ranking can be changed (e.g. by moving an idea up or down to a particular position)

M2      
1.4.1 If some shortlisted choices are already allocated, the chosen projects are displayed as unavailable and the student has to delete these. M2      
1.5

A similar system is used to maintain a shortlist of preferred supervisors.

M3      
1.4 Moderator Selection :
  • Student can select moderators in order of his preferences (in a maximum quantity defined by cohort coordinator)
P1      
2

The cohort coordinator matches the students choices with the available projects and supervisors.

M1      
2.1 The cohort coordinator can see a projects list, showing characteristics of the project and which students have chosen it (i.e. have it on their shortlist) M2      
2.2 This information can be sorted by title, theme, keywords, selected supervisors, etc.

M2

     
2.2

For each project, the coordinator can allocate a student and/or a supervisor

The allocation of student and supervisor does not have to be done at the same time.

M1      
2.3 When a project is allocated, an email is sent to the student, the moderator and the supervisor (if known) M3