CSC/ECE 517 Fall 2016 E1676 Role-based reviewing

Purpose

In the current version of Expertiza, members among a team can evaluate each other’s contribution and give appropriate scores based on the same questionnaire. However, in the lifetime of software development, members in a team often take on different roles whose works content are vastly differentiated. Like in an agile development environment, such as Scrum, there are typically seven roles group members can take: software engineer, architect, programmer, analyst, QA expert, tester and UI designers . Job description and evaluation entailed are vastly varied among these roles, thus a generic assessment rubric cannot hold reasonably.

The purpose or the rationale of our project is that we want to give project members the option to evaluate each other's work based on the specific role or duty they take in the development process. This can ensure a reasonable assessment for different duties and can also help to improve the utility using members-reviewing in the whole reviewing process.

Task Description

Task Description: There are generally three aspects we would accomplish in order to achieve the Role-based reviewing function.

1) A new option (check box) would be added to the Review Strategy tab from the instructor view when he creates a new assignment. What’s more, the instructor can create different roles or duties available for the assignment by typing into a test filed. The instructor also has the power the allow multiple members to choose for the same duty.

2) In the Rubrics tab from the instructor view, New rubric would be generated by creating different questionnaires for different roles when adding new assignment.

3) A new option (drop box) would be added to the “Your team” page from the student view when an assignment was created to be role-based reviewing. Student can choose their roles or duties from the drop box which were generated by the instructor for this specific assignment. When the instructor enabled the multiple selection option, different members in the team can choose same duties for this assignment.

Tasks can be viewed more clearly by the graph below:

Design

Database Design

We would create a new table called Duty.

Field Name	Type	Description
team_id	int(11)
duty_name	text	It saves student's duty in specific team.
student_id	int(11)
questionnaire_id	int(11)

We should add duty_based, multiple_duty_based and all_duty_name into assignments table to store the duty name

Field Name	Type	Description
duty_based	int(11)	If the assignment's team is duty based, it should be 1. If not, it should be 0.
multiple_duty_based	int(11)	If multiple people could choose one duty in the assignment, it should be 1. If not, it should be 0.
all_duty_name	int(11)	It would save all kinds of duties in the assignment.

Updates

Below are the key files modified:

Controllers

1. expertiza/app/controllers/assignments_controller.rb:
   def edit
       a. add "role based assignment" option to review strategy section.
       b. add roles to current assignment.
       c. add questionnaires to these roles separately. 
   end

2. expertiza/app/controllers/questionnaires_controller.rb

Models

See Database Design section above.

Views

1. expertiza/app/views/assignments/edit/_review_strategy.html.erb 
 1.1. add a "role based" strategy checkbox here.
 1.2. add roles input fields if you check the "role based" strategy checkbox.
2. expertiza/app/views/assignments/edit/_rubrics.html.erb

Testing Details

In our project, we are providing an option of adding duty for different team members in an assignment and giving review options based on their duty. We will add following functionalities: 1. How instructor create assignment with duties/roles 2. How students take duties from a given list of duties 3. How teammate evaluation rubric assign different review questionnaire based on duty.

UI Testing

UI will be tested manually. First, we will test creating an assignment as an instructor with different duties and assign different review questionnaires to each duty. Then we will login in as a student and take a duty from given list of duties. We will try covering all edge case scenarios in test cases section.

Test Cases

Following will be the test cases:

1. Login in as an Instructor:

 1.a] While creating an assignment, in the Review Strategy tab provide the list of roles/duties possible for teammates. There will be one text box to add      
      duty. To add more duties click on "add more". 
 1.b] Mark the check box that says multiple team members can have the same duty.
 1.c] Go to the Rubrics tab and select different questionnaires for different duty.    
 After creating this assignment students should be able to see different duties in "Your Team" page and should be able to select any duty. Multiple students 
 should be able to select same duty.

2. Login in as an Instructor:

 2.a] Repeat steps 1.a and 1.b 
 2.b] This time do not mark the check box that says "multiple team members can have the same duty".
 After creating this assignment students should be able to see different duties in "Your Team" page. This time student should not be able to select a duty if 
 it was already selected.

3. Login in as a Student

  When you login in as a student you should be able to pick different duties assigned by the instructor. If multiple members are not allowed to have same duty 
  then you should not be able to pick a duty if it was already selected by some other member.

4. Login in as a Reviewer

  When you login in as a reviewer you should get the questionnaire based on your duty. For example, if you are a software engineer you should get the review 
  questionnaire assigned to software engineer. 
  Different roles will be assigned different questionnaires for review.

RSpec

For functional testing, we will use RSpec. It uses Behavior Driven Development (BDD) for testing functionality of the system. It provides way to describe specific functionality of the system being tested and helps in better visualization of test cases.

Capybara

We will use Capybara for automating the manual test cases. It is a web-based automation framework and coupled with RSpec. It allow developers to write the test cases which simulate the whole scenario of manual testing.

Factory Girl

We will use Factory Girl for creating data factory. Factory Girl is a Ruby Gem that allow users to create templates for valid and re-usable objects. It allows more customization when user instantiate the objects and it aims to ensure that user have a valid object to work with.

Reference

Expertiza[1]

RSpec [2]

ScrumRoles [3]

CapyBara [4]

FactoryGirl [5]