CSC/ECE 517 Fall 2016 E1676 Role-based reviewing: Difference between revisions
| Line 6: | Line 6: | ||
== Task Description== | == Task Description== | ||
There are generally three aspect we would accomplish in order to achieve the Role-based reviewing function. | There are generally three aspect we would accomplish in order to achieve the Role-based reviewing function. | ||
1) | 1) | ||
2) | 2) | ||
3) | 3) | ||
Revision as of 02:10, 9 November 2016
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
There are generally three aspect we would accomplish in order to achieve the Role-based reviewing function.
1)
2)
3)
Design
Database Design
Updates
Below are the key files modified: