CITS3200 Project

Marking Criteria for Deliverable C

Deliverable C will be assessed both by the client, who will be primarily interested in the final product, and the unit coordinator, who will be more focused on the process.

As before, when marking the project the following scheme will be used as a guide. Maximum marks for a criterion, eg 5/5, will only be awarded sparingly. The marks for Deliverable C will be the sum of the individual criteria, the project mark being a weighted sum of totals for each deliverable.

The coordinator's criteria and the marks each attracts are:

Analysis of Time (Actual vs Expected) (/3)

Quality of Meeting Minutes (/3)

Testing Documentation (/4)

Version Control (/4)

Issue Tracking/Communication (/3)

Ethics checklist (/2)

The client's criteria and the marks each attracts are:

The overall quality of user/system documention (/5)

Acceptance Tests (/20)

Additional Features (/5)

These marks will only be awarded if more than 60% of the acceptance tests have passed. This is an opportunity for your group to show real virtuosity, but bells and whistles should never be at the expense of solidly implementing the basic functionality.

Professionalism (/5)

---

School of Computer Science & Software Engineering The University of Western Australia Last modified: June 30 2015 Modified By: Michael J Wise