The assignment will be marked using various categories.
Each category will be assigned a mark from 0 to 4 as
detailed in the table below.
½ marks may be awarded for close calls.
| 0 | Entirely absent, or there but essentially worthless. |
| 1 | Done poorly. |
| 2 | A reasonable try, but lacking in some manner. |
| 3 | An overall good job. |
| 4 | Done very well: one of the best in the class. |
| weight | category |
|---|---|
| 3 | Overall design documentation: tier responsibilities, boundaries, requirements. Object model documentation. Servlet Documentation. Discussion of login and roles and how the tiers interact to enforce them. Discussion of test creation and how tiers interact etc. (ie page flow, session objects and transactions). Discussion of user interaction. Map diagram. All documentation is marked for brevity and clarity and completeness. Elaboration of interesting design decisions. Design is marked for simplicity, transparency and extensability. |
| 2 | HTML page layout, visual appeal, minimal data entry, ease of navigation |
| 1 | javascript timer on test page |
| 2 | enforced roles (admin/participant) |
| 3 | session management and concurrency |
| 2 | transaction processing (for entry of test into database) |
| 3 | relational model, data dictionary |
| 3 | servlet database interaction |
| 6 | overall impression (runtime) - includes build and deploy working properly |
| 25 | × 4 = 100% |