Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-04-15T21:37:28Z

Brjadha2: /* UI and Instructor Workflow */

__TOC__

== Introduction ==

This wiki page presents the design for Expertiza project '''E2605: Specialized Rubrics for Different Topic Types''' for CSC/ECE 517 Object-Oriented Design and Development, Spring 2026.

The goal of this project is to let instructors use different review rubrics for different project topics within the same assignment. Expertiza currently uses the same review rubric for all submissions in an assignment, unless the assignment is configured to use different rubrics in different review rounds. This works for assignments where every topic should be evaluated with the same criteria, but it does not work well when topics require different kinds of evaluation.

For example, an assignment might include topics related to user-interface design, machine learning, and security. A security topic may need rubric questions about threat modeling or vulnerability analysis, while a user-interface topic may need rubric questions about usability and design quality. Topic-based rubric selection allows the rubric to match the topic of the submission being reviewed.

This document describes the motivation for the change, the proposed data model, the instructor workflow, and how Expertiza will resolve the correct review rubric based on assignment, topic, and review-round information.

== Overview ==

This design adds topic-based review rubric selection while keeping existing behavior for assignments where topic-based rubric selection is not enabled. Instructors will associate review rubrics with topics directly from the Topics tab of Assignment creation, using dropdowns. If an assignment is configured to vary by topic, the review rubric is chosen based on the topic of the submission that is being reviewed. If topic variation is not enabled, rubric selection follows the current assignment and round logic.

A [[Response maps|ReviewResponseMap]] identifies the team whose submission is being reviewed. The [[Signed up teams|signed_up_teams]] table identifies which topic that team selected. The [[Assignments questionnaires|assignments_questionnaires]] table will then identify which review rubric should be used for that assignment and topic.

== Problem Statement ==

Different project topics can require different evaluation criteria, but currently all submissions for an assignment use the same review rubric unless round-based rubric variation is configured. The current tables do not yet store which review rubric should be used for each topic, and there is no assignment flag for topic-based rubric variation. Because of this, reviewers can receive rubrics that do not match the reviewed team's topic.

== Design Goals ==

The goal is to let instructors define topic-specific review rubrics without changing the overall review workflow. The design must preserve backward compatibility for existing assignments, continue to support round-based variation, and keep rubric resolution deterministic when both round and topic variation are enabled.

== Non-Goals ==

This change does not redesign topic signup or waitlist behavior, questionnaire authoring or import, or review mapping strategies. It only changes how the system stores and resolves rubric selection for reviews.

== Current State ==

The existing data model already includes the relationships needed to determine a reviewee team's topic. The [[Signed up teams|signed_up_teams]] table identifies which team has selected which topic, and review mappings already identify the reviewee team. Rubric resolution currently happens in several places, including response and scoring code paths, and is mainly driven by assignment and round context.

The current tables do not yet store all the information needed for topic-based rubric selection. Assignments currently include <code>vary_by_round</code> but no equivalent <code>vary_by_topic</code> flag, and [[Assignments questionnaires|assignments_questionnaires]] records do not have a <code>project_topic_id</code> foreign key.

== Proposed Data Model ==

This design introduces minimal extensions to the existing schema while reusing the current rubric infrastructure. A new <code>vary_by_topic</code> boolean field is added to the assignments table with a default value of false. This ensures that existing assignments continue to function without any changes, and instructors can explicitly enable topic-based rubric variation only when needed.

In addition, an optional <code>project_topic_id</code> foreign key is added to the [[Assignments questionnaires|assignments_questionnaires]] table. A null <code>project_topic_id</code> represents the default review rubric for the assignment. This approach allows topic-specific mappings to coexist naturally with round-based mappings through <code>used_in_round</code>.

Indexes should be added on the new topic field and on the fields used for rubric lookup so that Expertiza can efficiently find the correct rubric for an assignment, topic, and round.

The [[Assignments questionnaires|assignments_questionnaires]] table already indicates which rubrics are used for an assignment. Adding <code>project_topic_id</code> allows one of those rubric records to apply to a specific topic instead of applying to the whole assignment. A project topic will normally have at most one review-rubric mapping, or one per round if round-based variation is enabled.

No new questionnaire type is introduced. The new <code>project_topic_id</code> field only connects an existing assignment-rubric record to a topic, and the rubric itself remains the existing questionnaire referenced by <code>questionnaire_id</code>.

== Rubric Resolution Behavior ==

Rubric selection remains within existing Expertiza code paths. The workflow proceeds by resolving the assignment from the response map, determining whether topic variation is enabled, and, if so, resolving the reviewee team's topic. The system then looks for the best matching assignment questionnaire for that assignment, topic, and round context.

When both round and topic variation are active, matching is deterministic. The precedence is: assignment/topic/current round, then assignment/topic/default round, then assignment/default topic/current round, and finally assignment/default topic/default round. In this precedence rule, the default topic corresponds to <code>project_topic_id</code> being null, and the default round corresponds to <code>used_in_round</code> being null.

If no topic-specific mapping is found, the system falls back according to the defined precedence, including default round-specific rubrics for the assignment when applicable, before using the default review rubric for the assignment.

Only the reviewee team's confirmed topic signup for the current assignment is considered, and waitlisted topic signups do not determine rubric selection.

== UI and Instructor Workflow ==

[[File:E2605architecture.png|800px|center|Figure: Rubric resolution architecture]]

Instructors configure topic-based rubrics directly in assignment setup on the Topics tab. For each topic, the UI exposes dropdowns for selecting the review rubric, and when <code>vary_by_round</code> is enabled, round-specific rubric choices are also supported. This approach keeps all configuration within the standard assignment authoring flow and avoids introducing any external components.

The existing default review rubric for the assignment remains available as the fallback when a topic-specific rubric is not configured. Reviewers do not choose the rubric themselves; instead, they receive the questionnaire resolved automatically for the team they are reviewing.

== API and Validation ==

Assignment create and update flows persist <code>vary_by_topic</code> cleanly, and parameter naming is normalized so that there is a single canonical internal field. Assignment questionnaire updates accept an optional <code>project_topic_id</code> and validate that the topic belongs to the same assignment.

Validation ensures that <code>project_topic_id</code> references an existing topic and does not cross assignment boundaries. The system also prevents duplicate review-rubric mappings for the same assignment, topic, and round combination, ensuring that rubric resolution always produces a single correct result.

Only instructors or administrators who can edit the assignment are allowed to enable topic-based rubric variation or modify topic-rubric mappings.

== Migration and Rollout ==

Migration first adds <code>vary_by_topic</code> to assignments, followed by adding a nullable <code>project_topic_id</code> to the [[Assignments questionnaires|assignments_questionnaires]] table along with the necessary foreign key and indexes. Existing rows remain valid with a null topic id and continue to represent default review rubrics for assignments.

After deployment, instructors can enable topic variation gradually on a per-assignment basis using the existing user interface.

== Testing Strategy ==

Tests verify that assignments without topic variation remain unchanged, while topic-enabled assignments correctly select topic-specific rubrics when configured. They also ensure that fallback behavior functions properly when a team has no topic or no topic-specific rubric mapping.

Additional tests confirm deterministic precedence when both topic and round variation are enabled and ensure that scoring behavior remains consistent with the selected questionnaire.

== Risks ==

The main risk is ambiguity in precedence when both topic and round variation are present. This is mitigated by defining a strict lookup order and enforcing it through testing. Another risk is partial configuration, where topic variation is enabled but mappings are incomplete; this is mitigated by safe fallback behavior and validation in configuration paths.

== Open Questions ==

If an instructor changes a topic-rubric mapping after reviews have begun, existing responses could resolve to a different rubric unless the selected mapping is preserved. The implementation should either store the selected assignment questionnaire on the response or prevent mapping changes once reviews are underway.

== Implementation Notes ==

Implementation focuses on schema changes, shared internal rubric lookup logic, integration at current rubric selection call sites, user interface support on the Topics tab, and regression coverage for response and scoring paths.

Known integration points include response questionnaire lookup, scoring maximum-score calculation, and any review form initialization path that currently assumes assignment-level rubric selection.

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-04-15T21:37:13Z

Brjadha2: /* UI and Instructor Workflow */

__TOC__

== Introduction ==

This wiki page presents the design for Expertiza project '''E2605: Specialized Rubrics for Different Topic Types''' for CSC/ECE 517 Object-Oriented Design and Development, Spring 2026.

The goal of this project is to let instructors use different review rubrics for different project topics within the same assignment. Expertiza currently uses the same review rubric for all submissions in an assignment, unless the assignment is configured to use different rubrics in different review rounds. This works for assignments where every topic should be evaluated with the same criteria, but it does not work well when topics require different kinds of evaluation.

For example, an assignment might include topics related to user-interface design, machine learning, and security. A security topic may need rubric questions about threat modeling or vulnerability analysis, while a user-interface topic may need rubric questions about usability and design quality. Topic-based rubric selection allows the rubric to match the topic of the submission being reviewed.

This document describes the motivation for the change, the proposed data model, the instructor workflow, and how Expertiza will resolve the correct review rubric based on assignment, topic, and review-round information.

== Overview ==

This design adds topic-based review rubric selection while keeping existing behavior for assignments where topic-based rubric selection is not enabled. Instructors will associate review rubrics with topics directly from the Topics tab of Assignment creation, using dropdowns. If an assignment is configured to vary by topic, the review rubric is chosen based on the topic of the submission that is being reviewed. If topic variation is not enabled, rubric selection follows the current assignment and round logic.

A [[Response maps|ReviewResponseMap]] identifies the team whose submission is being reviewed. The [[Signed up teams|signed_up_teams]] table identifies which topic that team selected. The [[Assignments questionnaires|assignments_questionnaires]] table will then identify which review rubric should be used for that assignment and topic.

== Problem Statement ==

Different project topics can require different evaluation criteria, but currently all submissions for an assignment use the same review rubric unless round-based rubric variation is configured. The current tables do not yet store which review rubric should be used for each topic, and there is no assignment flag for topic-based rubric variation. Because of this, reviewers can receive rubrics that do not match the reviewed team's topic.

== Design Goals ==

The goal is to let instructors define topic-specific review rubrics without changing the overall review workflow. The design must preserve backward compatibility for existing assignments, continue to support round-based variation, and keep rubric resolution deterministic when both round and topic variation are enabled.

== Non-Goals ==

This change does not redesign topic signup or waitlist behavior, questionnaire authoring or import, or review mapping strategies. It only changes how the system stores and resolves rubric selection for reviews.

== Current State ==

The existing data model already includes the relationships needed to determine a reviewee team's topic. The [[Signed up teams|signed_up_teams]] table identifies which team has selected which topic, and review mappings already identify the reviewee team. Rubric resolution currently happens in several places, including response and scoring code paths, and is mainly driven by assignment and round context.

The current tables do not yet store all the information needed for topic-based rubric selection. Assignments currently include <code>vary_by_round</code> but no equivalent <code>vary_by_topic</code> flag, and [[Assignments questionnaires|assignments_questionnaires]] records do not have a <code>project_topic_id</code> foreign key.

== Proposed Data Model ==

This design introduces minimal extensions to the existing schema while reusing the current rubric infrastructure. A new <code>vary_by_topic</code> boolean field is added to the assignments table with a default value of false. This ensures that existing assignments continue to function without any changes, and instructors can explicitly enable topic-based rubric variation only when needed.

In addition, an optional <code>project_topic_id</code> foreign key is added to the [[Assignments questionnaires|assignments_questionnaires]] table. A null <code>project_topic_id</code> represents the default review rubric for the assignment. This approach allows topic-specific mappings to coexist naturally with round-based mappings through <code>used_in_round</code>.

Indexes should be added on the new topic field and on the fields used for rubric lookup so that Expertiza can efficiently find the correct rubric for an assignment, topic, and round.

The [[Assignments questionnaires|assignments_questionnaires]] table already indicates which rubrics are used for an assignment. Adding <code>project_topic_id</code> allows one of those rubric records to apply to a specific topic instead of applying to the whole assignment. A project topic will normally have at most one review-rubric mapping, or one per round if round-based variation is enabled.

No new questionnaire type is introduced. The new <code>project_topic_id</code> field only connects an existing assignment-rubric record to a topic, and the rubric itself remains the existing questionnaire referenced by <code>questionnaire_id</code>.

== Rubric Resolution Behavior ==

Rubric selection remains within existing Expertiza code paths. The workflow proceeds by resolving the assignment from the response map, determining whether topic variation is enabled, and, if so, resolving the reviewee team's topic. The system then looks for the best matching assignment questionnaire for that assignment, topic, and round context.

When both round and topic variation are active, matching is deterministic. The precedence is: assignment/topic/current round, then assignment/topic/default round, then assignment/default topic/current round, and finally assignment/default topic/default round. In this precedence rule, the default topic corresponds to <code>project_topic_id</code> being null, and the default round corresponds to <code>used_in_round</code> being null.

If no topic-specific mapping is found, the system falls back according to the defined precedence, including default round-specific rubrics for the assignment when applicable, before using the default review rubric for the assignment.

Only the reviewee team's confirmed topic signup for the current assignment is considered, and waitlisted topic signups do not determine rubric selection.

== UI and Instructor Workflow ==

[[File:E2605architecture.png|800px|center|Figure: Rubric resolution architecture]]
Instructors configure topic-based rubrics directly in assignment setup on the Topics tab. For each topic, the UI exposes dropdowns for selecting the review rubric, and when <code>vary_by_round</code> is enabled, round-specific rubric choices are also supported. This approach keeps all configuration within the standard assignment authoring flow and avoids introducing any external components.

The existing default review rubric for the assignment remains available as the fallback when a topic-specific rubric is not configured. Reviewers do not choose the rubric themselves; instead, they receive the questionnaire resolved automatically for the team they are reviewing.

== API and Validation ==

Assignment create and update flows persist <code>vary_by_topic</code> cleanly, and parameter naming is normalized so that there is a single canonical internal field. Assignment questionnaire updates accept an optional <code>project_topic_id</code> and validate that the topic belongs to the same assignment.

Validation ensures that <code>project_topic_id</code> references an existing topic and does not cross assignment boundaries. The system also prevents duplicate review-rubric mappings for the same assignment, topic, and round combination, ensuring that rubric resolution always produces a single correct result.

Only instructors or administrators who can edit the assignment are allowed to enable topic-based rubric variation or modify topic-rubric mappings.

== Migration and Rollout ==

Migration first adds <code>vary_by_topic</code> to assignments, followed by adding a nullable <code>project_topic_id</code> to the [[Assignments questionnaires|assignments_questionnaires]] table along with the necessary foreign key and indexes. Existing rows remain valid with a null topic id and continue to represent default review rubrics for assignments.

After deployment, instructors can enable topic variation gradually on a per-assignment basis using the existing user interface.

== Testing Strategy ==

Tests verify that assignments without topic variation remain unchanged, while topic-enabled assignments correctly select topic-specific rubrics when configured. They also ensure that fallback behavior functions properly when a team has no topic or no topic-specific rubric mapping.

Additional tests confirm deterministic precedence when both topic and round variation are enabled and ensure that scoring behavior remains consistent with the selected questionnaire.

== Risks ==

The main risk is ambiguity in precedence when both topic and round variation are present. This is mitigated by defining a strict lookup order and enforcing it through testing. Another risk is partial configuration, where topic variation is enabled but mappings are incomplete; this is mitigated by safe fallback behavior and validation in configuration paths.

== Open Questions ==

If an instructor changes a topic-rubric mapping after reviews have begun, existing responses could resolve to a different rubric unless the selected mapping is preserved. The implementation should either store the selected assignment questionnaire on the response or prevent mapping changes once reviews are underway.

== Implementation Notes ==

Implementation focuses on schema changes, shared internal rubric lookup logic, integration at current rubric selection call sites, user interface support on the Topics tab, and regression coverage for response and scoring paths.

Known integration points include response questionnaire lookup, scoring maximum-score calculation, and any review form initialization path that currently assumes assignment-level rubric selection.

File:E2605architecture.png

2026-04-15T21:33:43Z

Brjadha2:

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:16:08Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
* <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
* <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
* Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
* Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
* The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
* <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
* <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
* <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
* <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
* <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
* <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
* <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
* <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
* Topic-specific rubric assignment with fallback to default for unassigned topics.
* Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
* Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==

* '''Frontend Integration''' — Implement the Topics tab UI with per-topic rubric dropdowns in the reimplementation frontend.
* '''Signup Sheet Display''' — Show the assigned rubric for each topic on the signup sheet so students know which rubric applies to their project.
* '''Additional Questionnaire Types''' — Extend topic-specific rubric support beyond <code>ReviewQuestionnaire</code> to metareview and author feedback questionnaires.
* '''Query Optimization''' — Reduce per-topic database queries during rubric resolution using eager loading for assignments with many topics and rounds.

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* https://github.com/PositivelyBookish/reimplementation-back-end
* https://drive.google.com/file/d/1mUPfoA5QLeuYI8_lcDCf1mx56yEg9XJq/view?usp=sharing

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)
'''Mentor''' — Sree Tulasi Shevva

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:15:46Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
* <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
* <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
* Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
* Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
* The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
* <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
* <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
* <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
* <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
* <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
* <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
* <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
* <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
* Topic-specific rubric assignment with fallback to default for unassigned topics.
* Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
* Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==

* '''Frontend Integration''' — Implement the Topics tab UI with per-topic rubric dropdowns in the reimplementation frontend.
* '''Signup Sheet Display''' — Show the assigned rubric for each topic on the signup sheet so students know which rubric applies to their project.
* '''Additional Questionnaire Types''' — Extend topic-specific rubric support beyond <code>ReviewQuestionnaire</code> to metareview and author feedback questionnaires.
* '''Query Optimization''' — Reduce per-topic database queries during rubric resolution using eager loading for assignments with many topics and rounds.

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
* https://drive.google.com/file/d/1mUPfoA5QLeuYI8_lcDCf1mx56yEg9XJq/view?usp=sharing

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)
'''Mentor''' — Sree Tulasi Shevva

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:14:08Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
* <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
* <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
* Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
* Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
* The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
* <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
* <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
* <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
* <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
* <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
* <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
* <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
* <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
* Topic-specific rubric assignment with fallback to default for unassigned topics.
* Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
* Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==

* '''Frontend Integration''' — Implement the Topics tab UI with per-topic rubric dropdowns in the reimplementation frontend.
* '''Signup Sheet Display''' — Show the assigned rubric for each topic on the signup sheet so students know which rubric applies to their project.
* '''Additional Questionnaire Types''' — Extend topic-specific rubric support beyond <code>ReviewQuestionnaire</code> to metareview and author feedback questionnaires.
* '''Query Optimization''' — Reduce per-topic database queries during rubric resolution using eager loading for assignments with many topics and rounds.

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
*

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)
'''Mentor''' — Sree Tulasi Shevva

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:12:51Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
* <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
* <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
* Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
* Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
* The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
* <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
* <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
* <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
* <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
* <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
* <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
* <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
* <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
* Topic-specific rubric assignment with fallback to default for unassigned topics.
* Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
* Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==

* '''Frontend Integration''' — Implement the Topics tab UI with per-topic rubric dropdowns in the reimplementation frontend.
* '''Signup Sheet Display''' — Show the assigned rubric for each topic on the signup sheet so students know which rubric applies to their project.
* '''Additional Questionnaire Types''' — Extend topic-specific rubric support beyond <code>ReviewQuestionnaire</code> to metareview and author feedback questionnaires.
* '''Query Optimization''' — Reduce per-topic database queries during rubric resolution using eager loading for assignments with many topics and rounds.

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
*

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:10:22Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
* <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
* <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
* Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
* Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
* The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
* <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
* <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
* <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
* <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
* <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
* <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
* <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
* <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
* Topic-specific rubric assignment with fallback to default for unassigned topics.
* Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
* Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==
* Improve frontend integration
* Optimize queries

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
*

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:05:38Z

Brjadha2:

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
* If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
* Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
* Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
* This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
* This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
** <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
** <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
** Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
** Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
** The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
** <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
** <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
** <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
** <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
** <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
** <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
** <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
** <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
** Topic-specific rubric assignment with fallback to default for unassigned topics.
** Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
** Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==
* Improve frontend integration
* Optimize queries

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
*

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)

CSC/ECE 517 Spring 2026 - E2605. Specialized Rubrics for Different Topic Types

2026-03-31T03:04:50Z

Brjadha2: Created page with "= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types = == 1. Overview == In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment. == 2. Motivation == Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different lear..."

= CSC/ECE 517 Spring 2026 – E2605: Specialized Rubrics for Different Topic Types =

== 1. Overview ==
In the current Expertiza system, each assignment uses a single rubric. This project enables assigning different rubrics to different topics within the same assignment.

== 2. Motivation ==
Expertiza supports a wide range of project types in CSC/ECE 517, including refactoring, testing, design, and documentation assignments. Each of these project types has different learning objectives and evaluation criteria. However, the current system restricts each assignment to a single rubric, forcing instructors to evaluate all topics using the same criteria regardless of their differences.

This limitation reduces the effectiveness and fairness of assessment, as a single rubric cannot accurately capture the expectations of diverse project types. For example, a testing-focused project requires evaluation of coverage and correctness, while a design-focused project emphasizes architecture and clarity.

By enabling specialized rubrics for each topic, instructors can align evaluation criteria with the specific goals of each project. This leads to more accurate grading, better feedback for students, and an overall improvement in the quality of assessment within the system.

== Functional Requirements ==

* By default, each assignment uses the rubric configured on the Rubrics tab (the assignment-level default rubric).
* On the Topics tab of the Assignment Edit page, instructors can assign a different rubric to each topic.
** If no topic-specific rubric is selected, the assignment's default rubric is automatically applied as a fallback.
** Rubric assignments can optionally vary per review round when the assignment has multiple rounds of review enabled.
* The rubric-selection logic must not reside in any controller.
** Resolution logic is implemented as model instance methods on <code>Assignment</code> and <code>ProjectTopic</code>.
* A new column, <code>topic_id</code>, is added to the <code>assignment_questionnaires</code> table.
** This links a questionnaire to a specific topic within an assignment.
* A new boolean column, <code>vary_by_topic</code>, is added to the <code>assignments</code> table.
** This controls whether topic-specific rubric resolution is active for a given assignment.

Supported rubric resolution cases:
* No variation — assignment default rubric used for all topics and rounds.
* Round-only variation — different default rubrics per round, no topic distinction.
* Topic-only variation — each topic can have its own rubric, same across all rounds.
* Topic + round variation — each topic can have a different rubric per round.

== Implementation Details ==

* Added two new API routes on the <code>Assignment</code> resource:
** <code>GET /assignments/:assignment_id/topics/rubrics</code> — returns the full rubric payload for the assignment, including default rubrics, available rubrics, and per-topic rubric assignments.
** <code>PATCH /assignments/:assignment_id/topics/rubrics</code> — accepts rubric mapping updates and persists topic-specific rubric assignments.
** Both routes are handled by the <code>rubrics</code> action in <code>assignments_topics_controller.rb</code>.
** Access is restricted to instructors, admins, and TAs with a mapping for the assignment.
* Added <code>topic_id</code> (bigint foreign key) to the <code>assignment_questionnaires</code> table and <code>vary_by_topic</code> (boolean) to the <code>assignments</code> table via migration <code>add_vary_by_topic_and_topic_id_to_assignment_questionnaires</code>.
** The migration is idempotent — it checks for existing columns and foreign keys before adding them, ensuring compatibility with different database states.
* Implemented rubric resolution methods in <code>assignment.rb</code>:
** <code>rubric_mapping_for</code> — resolves the effective rubric for a given questionnaire type, round, and topic; returns topic-specific mapping if one exists, otherwise falls back to the default.
** <code>specific_rubric_mapping_for</code> — returns a topic-specific <code>AssignmentQuestionnaire</code> record, or <code>nil</code> if <code>vary_by_topic</code> is disabled or no mapping exists.
** <code>default_rubric_mapping_for</code> — returns the assignment-level rubric mapping (where <code>topic_id</code> is <code>nil</code>).
** <code>assign_topic_rubric!</code> — upserts a topic-specific rubric mapping; destroys the mapping if <code>questionnaire_id</code> is blank, preserving all other records.
** <code>clear_topic_rubric!</code> — removes a specific topic-rubric mapping without affecting other mappings.
* Implemented topic-level rubric methods in <code>project_topic.rb</code>:
** <code>rubric_for_review(round: nil)</code> — returns the resolved questionnaire for this topic for a given round, delegating to <code>assignment.questionnaire_for</code>.
** <code>has_specific_rubric?(questionnaire_type:, round:)</code> — returns whether this topic has an explicit rubric mapping.
** <code>assign_rubric!</code> and <code>clear_rubric!</code> — convenience methods that delegate to the assignment model.
* Created <code>spec/requests/api/v1/assignments_topics_controller_spec.rb</code> with request specs covering:
** Topic-specific rubric assignment with fallback to default for unassigned topics.
** Persistence of topic-specific mappings without recreating or modifying the default assignment rubric.
** Independent per-topic, per-round rubric assignments with round-aware fallback behavior.
* Added <code>spec/factories/assignment_questionnaires.rb</code> and <code>spec/factories/signed_up_teams.rb</code> to support test setup.

== 3. Future Work ==
* Improve frontend integration
* Optimize queries

== 4. LLM Design Conversation ==
* Artificially intelligent LLM models (ChatGPT, Claude.ai) were leveraged to streamline development and consult regarding critical design decisions.
Here is the link: https://chatgpt.com/share/69c807c8-aa54-8328-bbe0-8bbe7ce89561

== 5. Useful Links ==
* [https://github.com/PositivelyBookish/reimplementation-back-end
*

== 6. Team Information ==
* Vanaja Binay Agarwal (vagarwa3)
* Himanshu Agarwal (hagarwa4)
* Bhargavi Jadhav (brjadha2)