E1936 Specialized Rubrics

E1936. Specialized Rubrics for Different Topic Types

This page provides a description of an Expertiza OSS project.

Problem Statement

In CSC/ECE 517, there are several types of topics that could be covered in a single class assignment.

• Code base
  • Expertiza
  • Mozilla
  • etc.
• Goal
  • Refactoring
  • Testing
  • etc.

However, currently we can only specify one kind of rubric for an assignment. This means that teams working on different topics will be evaluated using the same rubric. With this setup, it's not possible to fine-tune rubrics for different topics - rubrics tend to be overly general.

What Needs to be Done

• In assignment#edit page "Rubrics" tab, add a checkbox to specify whether rubric should vary by topic.
• In assignment#edit page "Topics" tab, add a dropdown next to each topic to specify which rubric is associated with the topic.
  • This dropdown should appear only if rubric should vary by topic, per the Rubrics tab.
  • By default, the rubric for each course project will be the one specified in “Rubrics” tab.
  • The dropdown value can overwrite the default rubric.
• Be careful when making changes to the code
  • The signup_sheet_controller should have as little to do as possible with the selection of rubrics.
  • Anything not germane to selecting topics should be in another controller or (more probably) a helper.
• Create a DB migration to add questionnaire_id in sign_up_topics table to store the dropdown data.

Current Implementation (Relevant to this Project)

• The Questionnaire model keeps questionnaires for assignments (a.k.a. rubrics) as well as other types of questionnaires
• The AssignmentQuestionnaire model keeps track of which questionnaires are used for which assignments

How to Add a New Rubric

• [to be populated after coding is complete]

How to Select a Rubric for a Topic

• [to be populated after coding is complete]

Automated Testing with RSPEC

Our strategy for gaining confidence that our code changes did not break anything was as follows:

• Run all existing RSpec tests on any changed files, after our changes, to ensure that we have not introduced any failures.
• The commands and results are shown below.

  [to be populated after coding is complete]

• Write new comprehensive RSpec tests, for all new methods.
• Run these tests, to ensure that the new code works as intended.
• The commands and results are shown below.

  [to be populated after coding is complete]

• The test suite for a single new method is below.
• There are many such suites in (TODO add filename(s)).
• This example illustrates our general strategy:
  • test missing input
  • test bad input
  • test various acceptable forms of input
  • test scenarios that lead to "true" and to "false" return values

  [to be populated after coding is complete]

Team Members

• Aurora Tiffany-Davis
• Ginger Balmat
• Joe Hutchinson
• Nikolay Titov

Links (Our Work)

1. Project Repository Fork
2. [(add link here) Pull Request]
3. [(add link here) Video Demonstration of Specialized Rubrics]

Links (Previous Attempt by another Team)

1. Pull Request
2. Wiki Page
3. Video Demonstration of Specialized Rubrics

Links (General References)

1. Expertiza on GitHub
2. The live Expertiza website
3. Expertiza project documentation wiki
4. Rspec Documentation