SUMS-Feedback

Feedback

History

Version (most recent first)

Date

Changer

Change

v1.0

2012-02-27

 

First draft

Introduction

Aim

Feedback is the part of SUMS where by the markers comments and results are fed back to the student. Only one view of feedback need be given to the student this is to be synthesized out of the multiple comments and results given.

Key personnel

Responsible owner

Jim Briggs

Design authority

Jim Briggs

Development team

 

Requirements

Entities and attributes

Entity

Attributes

Relationships

Marks

 

  1. Synthesize marks out of all feedback

Email

 

  1. Cohort Coordinator to email feedback

Submit

 

  1. Identify if project was late

Feedback

  1. Key
  2. Student viewed feedback Date
  3. Feedback created Date
  4. Feedback last Modified Date

 

Functionality for students

Requirement

Type

Status

Change request(s)

1

Supervisor or cohort co-ordinator (or moderator?) to set feedback by: synthesising the comments (and/or mark category attributes) from the marks submitted by the supervisor, moderator and (if present) the third marker.

Synthesis of feedback is the union of the 2/3 marks (attributes, comments or both).

User can then edit text on-screen.

M1

 

 

1.1

CC sends email to student with link to feedback

Template for this email should be stored in database.

Email only to be sent to students for whom feedback has been set.

M2

 

 

1.2

Indicate if work was handed in late showing:

  • Potential score
  • Capped actual mark

M1

 

 

2

View feedback

Include whether hand-in was late, etc.

Record timestamp of when this was done.

M1

 

 

2.1

 

M2

 

 

3

Anyone involved with the marking (i.e. supervisor, moderator, third marker, CC) should be able to view feedback table but not the student

M1

 

 

3.2

 

M1

 

 

4

CC, supervisor, moderator, etc. can view to see whether the student has accessed their feedback

M2

 

 

5

Cohort coordinator views list of:

  • students whose feedback has not yet been set
  • students who have not yet been told that their feedback is available
  • students who have been informed, but not yet read their feedback

M3

 

 

5.1

 

M3

 

 

Functionality for external examiner

 

Requirement

Type

Status

Change request(s)

1

When at least one result has been confirmed, produce a spreadsheet per unit to be imported into Jupiter containing:

  • Student ID
  • Name
  • Agreed Mark
  • Unit Code

M1

 

 

2

External Examiner should be able to review entire marking process

For a single FinalProject:

  • Display marks and comments from all markers in a single view – one column per marker, one row per mark category

Timestamp External Examiner looking at a project

M2

 

 

3

Cohort Co-ordinator to list projects in a cohort that have been audited by External Examiner

M3