Grading for Part 4 - CMPUT301F16T01/Carrier GitHub Wiki
Grading Schema (How to get a full 10 marks):
#Addressing Feedback: (0) Excellent: All addressed, well addressed, consistent (0) Good: Mostly addressed, well addressed, some inconsistency
Code Base:
(3) Excellent: Excellent effort, relatively consistent, at least ½ of requirements implemented, clean code (2) Good: Good quality, some inconsistency, about ½ of requirements implemented
Tangible Demo:
(1) Excellent: Demoable, clear (1) Good: Demoable, rough edges
Code Documentation:
(1) Excellent: Consistent, easy to interpret (1) Good: Mostly Consistent, 3rd party could understand
Test Cases:
(2) Excellent: Test exist and run, clearly comprehensive. (1) Good: Tests exist and run, some inconsistency
OOD:
(2) Excellent: Model Class Obvious, data Classes Obvious, smells MVCish, clearly models important entities, diagrams well labelled, design patterns obvious. (1) Good: Model Class Obvious, data Classes Obvious, smells MVCish, clearly models important entities, some inconsistency, design patterns used
Release Planning:
(0.5) Excellent: Clear planning, realistic / Achievable (0.5) Good: Obvious planning with inconsistency
Reuse Statement:
(0.5) Excellent: Complete, consistent, approved reuse (0.5) Good: Some incompleteness, some inconsistency, approved reuse