MarkUs Blog

MarkUs Developers Blog About Their Project

Code Sprinting with MarkUs – Day 3

with 3 comments

The MarkUs team had a meeting yesterday to discuss our tasks for the rest of the semester. As promised, here is a description of the exciting new features that we are planning on adding to MarkUs:

  • Simple Grade Entry
    • Used for entering grades from labs, exams, etc.
    • This will be another type of “assignment” that the instructor can create
    • Considerations and open questions:
      • Permissions (eg. TAs need to be able to modify the table, students are not allowed to see the whole table, etc.)
      • Attaching graders
      • Conditions for releasing marks
      • What’s the workflow for creating the grade entry form? What’s the UI for entering grades? What’s the UI for students? Model?
  • Messages
    • Allow messages about a student’s results (eg. notes about remark requests, concerns, etc.) to be added in the grader view
    • This will be a tab in the grader view
    • Messages are visible to instructors and TAs only
    • Timestamp and mark the user name for annotations
    • Considerations:
      • Ways to aggregate messages for an assignment
      • Ways to download and/or view aggregate
      • Messages per student
      • Viewing messages – notify the instructor / TA about messages since the last time they logged in
  • New Marking Scheme
    • Allow the instructor to specify a description of a criterion and a total number of marks for that criterion
    • Considerations:
      • Ways to create title, description, and weight
      • Ways to upload/download description
      • Format for description
      • Allowing penalties, deductions, bonus marks, etc.
      • UI – the TA will need to enter a number into a box for each criterion
  • Logging
    • Want to find out how students and TAs are using MarkUs
    • Students:
      • Number of submissions and when (can get this information from svn)
      • Who is submitting? (eg. Is one person doing all of the work in a group project?)
      • Who is looking up their grades?
      • Information about groups (eg. accepts, rejects)
    • TAs
      • Number of annotations
      • Tracking setting grades
      • Time spent marking
    • Need to create a log file first and then determine how to visualize the data
    • Considerations and open questions:
      • The size of the log files
      • How should we store this information? DB versus log file?
      • Rotating logs?
      • How many messages might there be?
  • Automated Testing
    • Allow students to run tests against their code
    • Can be used to run style checks, code coverage tests, etc.
    • Considerations:
      • Security
      • UI for the student and instructor
      • Where/how will the tests be run?

After discussing these new features, we split up the tasks based on our interests. Here’s the breakdown:

  • Tara and Fernando will be working together on the messages. Fernando will also do some work on logging first.
  • Melanie, Simon, and Gabriel will work on the new marking scheme. They will be doing test-driven development.
  • Farah will work on the simple grade entry.
  • Severin is going to get started on automated testing.
  • Everyone will be developing tests for their code.

We’re all set for a productive term! Let the fun begin!

Written by Farah Juma

September 28th, 2009 at 10:26 am

Posted in Minutes

3 Responses to 'Code Sprinting with MarkUs – Day 3'

Subscribe to comments with RSS or TrackBack to 'Code Sprinting with MarkUs – Day 3'.

  1. […] the afternoon to discuss our tasks for the rest of the semester. You’ll want to check out the exciting new features that we are planning on adding to […]

  2. […] change submitted through ReviewBoard and figure out how to use SVN with my install of RadRails and we all came up with a list of features that we plan to implement this term. I will be working on messages between TAs (graders) and instructors, along with Fernando who is […]

  3. […] change submitted through ReviewBoard and figure out how to use SVN with my install of RadRails and we all came up with a list of features that we plan to implement this term. I will be working on messages between TAs (graders) and instructors, along with Fernando who is […]

Leave a Reply