Project Criteria - jwyatt1999/CITS3403_Cartographers GitHub Wiki
CITS3403 Unit Page
https://teaching.csse.uwa.edu.au/units/CITS3403/
CITS3403 Project Marking Criteria
https://teaching.csse.uwa.edu.au/units/CITS3403/projects/Project2Criterion.pdf
Criteria
- Online daily “puzzle” (puzzle is defined pretty loosely, eg. guess the sound or guess the grocery from its carbon footprint are example ideas provided by the unit coordinator)
- Short daily exercise
- Users receive a score / rank / feedback
- Users can track progress / statistics in a separate view and compare to friends and general population
- Engaging, so that it looks good and users want to play it daily
- Challenging, so the user feels a sense of achievement
- Intuitive, so that it is easy for a user to access
- Effective, so that it promotes a positive message or modifies users behavior in a positive way
- Users can share their performance via social media
- The website can function on PC, tablet, and mobile devices
Marked On
- HTML (10%) - Valid code, Wide range of elements, Excellent navigation
- CSS (10%) - Valid, Maintainable code, Wide range of custom selectors and classes, Reactive to device
- JS (15%) - Valid, Well formatted code, Includes validation and DOM manipulation / AJAX
- Style (10%) - Well considered distinctive style, Uses coherent images and fonts
- Content (5%) - Excellent and engaging choice of material and mechanism, Application has value
- Flask Code (10%) - Well formatted, commented and organised code, No errors and nontrivial elements
- Data Models (10%) - Well considered database schema, Good authentication, Maintainable model, Some evidence of DB migration
- Testing (10%) - Comprehensive unit tests, Large test database, User tests with good coverage
- Design (10%) - Complex engaging mechanism, Fully implemented
- Collaboration (10%) - Comprehensive git logs, Shows persistent contributions, branching, merging, and migrations, Shared contribution to demonstration