|
|
| Line 15: |
Line 15: |
| ==Use Case== | | ==Use Case== |
| | | |
| <div style="padding: 0px 0px 0px 25px">
| |
| [[File:Use_Case_(1).jpg|none|frame|Use Case]]
| |
| </div>
| |
|
| |
| 1. Name: Teams submitting reviews for assignment or topic
| |
|
| |
| 2. Actor: Student (as member of a team)
| |
|
| |
| 3. Other Participants: Team Members
| |
|
| |
| 4. Precondition: Instructor has set up assignment with review strategy as "Team Reviews".
| |
|
| |
| 5. Primary Sequence:
| |
| <li> Log in to Expertiza.
| |
| <li> Select an assignment.
| |
| <li> Select "other's work".
| |
| <li> The student can request a review for the team from here.
| |
| <li> Depending on the number of reviews allowed and number of reviews already performed by the team, they will be allotted a new review
| |
| <li> Begin the review.
| |
| <li> Only one member of the team can edit the review at an given time.
| |
| <li> All restrictions that apply to individual reviewers, also apply to teams (e.g. like a individual reviewer, a team also cannot have more than 2 outstanding incomplete reviews).
| |
| <li> Complete the review and Click Submit.
| |
| <br>
| |
|
| |
| ==UI Changes==
| |
| 1. Currently there is no team reviewing in Expertiza. Thus, we will provide a check-box, in the review strategy tab of edit assignments, for the instructor. Checking this box will set the reviewers to teams, rather than individual participants.
| |
| <div style="padding: 0px 0px 0px 25px">
| |
| [[File:Review_stratergy1.png|none|frame|Current Implementation]]
| |
| </div>
| |
|
| |
| ----
| |
|
| |
| <div style="padding: 0px 0px 0px 25px">
| |
| [[File:New_Review_strat_noselect1.png|none|frame|New Implementation]]
| |
| </div>
| |
| ----
| |
|
| |
| <br>
| |
| 2. By default, the reviewers will be individual students. When they request reviews, they request reviews for themselves. If the instructor changes the reviewers to teams, then each participant (who is member of some team), will request reviews on behalf of the entire team.
| |
| <div style="padding: 0px 0px 0px 25px">
| |
| [[File:Student_review1.png|none|frame|Individual Review Request]]
| |
| </div>
| |
| ----
| |
|
| |
| <div style="padding: 0px 0px 0px 25px">
| |
| [[File:Student_team_review1.png|none|frame|Team Review Request]]
| |
| </div>
| |
| ----
| |
|
| |
| <br>
| |
|
| |
|
| ==Test Plan== | | ==Test Plan== |
| Testing of the new controller methods to check whether all the functionality of reviewing as a participant is also working for the scenario when reviewing is done by a team.
| |
|
| |
|
| ---- | | ---- |
Introduction
Motivation
Changes to be Implemented
Files Involved
Design Principles to be Followed
1. MVC - The project is implemented in Ruby on Rails that uses MVC architecture. It separates an application’s data model, user interface, and control logic into three distinct components (model, view and controller, respectively).
2. Dry Principle - We are trying to reuse the existing functionalities in Expertiza, thus avoiding code duplication. Whenever possible, code modification based on the existing classes, controllers, or tables will be done instead of creating the new one.
3. Polymorphism -
4. Inheritance -
Use Case
Test Plan