This lab defines what you need to do for final submission. You must follow these steps to receive a coursework grade for the module. We require a copy of your submission for moderation, and therefore you will have to submit your work as defined below. You will also receive your final 20% grade for final delivery based on the completeness and quality of your submission.
We will be performing a pull of your repository at the time of submission using an automated script. If you have not provided your GitHub link do so now. If you miss the cutoff date for link submission your repository will not be pulled and it will be counted as a none submission. This is a one minute task.
We require the following badges on your GitHub repository to determine the status of your submission:
- Build status for
master. - Build status for
develop. - Code coverage of tests for
master. - Release name.
- License.
These badges will be clicked to ensure they are correct. Incorrect badges provided will be penalised appropriately.
There are 32 requirements in total. Your readme should state how many out of 32 have been met, and a percentage. For example:
20 requirements of 32 have been implemented, which is 62.5%.
We then want evidence of each feature being met. This will be in the form of a table (written in Markdown) with a screenshot from your application showing output that meets the requirements. We require the following columns:
- ID of the requirement.
- Name of the requirement.
- Has the requirement been met (Yes or No).
- Screenshot.
For example:
| ID | Name | Met | Screenshot |
|---|---|---|---|
| 1 | All the countries in the world organised by largest population to smallest. | Yes | image |
| 2 | All the countries in a continent organised by largest population to smallest. | No | |
| 3 | All the countries in a region organised by largest population to smallest. | Yes | image |
Your submission will be checked to ensure this information is correct. If incorrect information is provided this will be considered an act of academic misconduct by the group and dealt with accordingly.
We will only assess your master branch. Make sure that branch contains the version of your code you wish to submit.
| Matriculation Number | Code Review 1 | Code Review 2 | Code Review 3 | Code Review 4 | Final Deliverable |
|---|---|---|---|---|---|
| 4000xxxx | 25 | 50 | 0.0 | 0.25 | 0.2 |
| 4000xxxx | 25 | 50 | 0.5 | 0.25 | 0.4 |
| 4000xxxx | 25 | 0 | 0.5 | 0.25 | 0.2 |
| 4000xxxx | 25 | 0 | 0.0 | 0.25 | 0.2 |
| Total | 100 | 100 | 100 | 100 | 100 |
The team need to agree these scores. If the team cannot agree, or a team member believes the spreadsheet submitted does not represent the actual contributions, then email the teaching team. In these circumstances, the metrics and other information provided on GitHub will be used.