Requirements
Submission
| Title | Description |
|---|---|
| Video demonstration | 1. Demonstrate work with clearly working features 2. How does it address the problem (does this need to be in report or video demo) 3. Critical analysis of solution (does this need to be in report or video demo) 4. No longer than 10 min 5. Discuss and explain the features 6. Emphasise the areas of code that are most complex |
| Testing report | 1. Min of 2 users testing the application during and after completion |
Submission format
| Title | Description |
|---|---|
| Code | All project files must be zipped, and well commented |
| Code pdf | A word or pdf file containing all java code (i assume this is for plagiarism) |
| Testing plan | Word doc containing testing plan |
| Declaration form | … |
Grading criteria
| Done | Description |
|---|---|
| All features are implemented | |
| Extensive use of UI components | |
| Good use of technology, baso follow guidelines | |
| User testing with 4 different people, during and post development |
Features
| Title | Done | Description |
|---|---|---|
| Login/register | Gym owners need a login, this is not required for normal users | |
| NFC scanning page | NFC tags can be scanned | |
| Content delivery page | Once an NFC tag is scanned the user can view the content associated with it | |
| Gym owners can create new content | Gym owners can create new contact to assign it to a tag. Should handle cases where a tag is already assigned a value. Tags should be locked. | |
| Tag management | Gym owners can assign multiple tax one content, they can also delete tags. | |
| Gym owners edit existing content | Gym owners can edit existing content. | |
| Gym owners can edit account details. | Owners can edit their account details, such as their name and password. |
