Project → v1.4 [week 13]
Overview: final tweaks to docs/product, release product, demo product, test/evaluate peer products
Summary of submissions:
| Team/Individual Item | Name format | Upload to |
|---|---|---|
| Source code | tag as v1.4 |
GitHub |
| Jar file | [team][product name].jare.g. [T09-B1][ContactsPlus].jar |
IVLE |
| User Guide | [TEAM_ID][Project Name]UserGuide.pdfe.g.[T09-B1][Contacts Plus]UserGuide.pdf |
IVLE |
| Developer Guide | [TEAM_ID][Project Name]DeveloperGuide.pdfe.g. [T09-B1][Contacts Plus]DeveloperGuide.pdf |
IVLE |
| Product Website | README.adoc, Ui.png, AboutUs.adoc |
GitHub |
| Project Portfolio Page | [TEAM_ID][Your Name]Portfolio.pdfe.g.[T09-B1][John Doe]Portfolio.pdf |
IVLE |
| Collated files | GitHub |
Deadline for all v1.4 submissions is Week 13 Monday 23.59 unless stated otherwise.
- ❗️ Penalty for late submission: -1 mark for each hour delayed, up to 3 hours. Even a 1-second delay is considered late, irrespective of the reason. Penalty for delays beyond 3 hours are determined on a case
by case basis.
- For submissions done via IVLE, the submission time is the timestamp shown by IVLE.
- When determining the late submission penalty, we take the latest submission even if the same exact file was submitted earlier. Do not submit the same file multiple times if you want to avoid unnecessary late submission penalties.
- The whole team is penalized for problems in team submissions. Only the respective student is penalized for problems in individual submissions.
- ❗️ Please follow submission instructions closely. Any non-compliance will be penalized. e.g. wrong file name, team member photos not suitable, etc.
- For pdf submissions, ensure the file is usable and hyperlinks in the file are correct. Problems in documents are considered bugs too e.g. broken links, outdated diagrams/instructions etc..
- Do not update the repo during the 14 days after the deadline. Get our permission first if you need to update the repo during that freeze period. You can continue to evolve your repo after that.
Grading:
v1.4 Product
Submission: See summary of submissions above
v1.4 Source Code
Submission: Push the code to GitHub and tag with the version number. Source code (including collated .md files; please ensure the collated .md files are up to date; any updates to collated code files
after the deadline will be considered a later submission). Note that the quality of the code in these collated code files accounts for a significant component of your final score, graded individually.
v1.4 User Guide
Submission: Convert the pdf (AB4 dev guide has some instructions on converting project docs to pdf) and upload to IVLE. See summary of submissions above for the file name format.
v1.4 Developer Guide
Submission: Similar to UG
v1.4 Product Website
Submission: Push the code to GitHub
v1.4 Demo
- Venue: Same as the tutorial venue unless informed otherwise.
- Schedule: Your demo timing is same as your tutorial time in week 13.
Starting times:Team B1: 00 minutes, B2: 20 minutes, B3: 40 minutes, B4: TBA
At least some team members need to arrive 15 minutes ahead of the allocated time to set up your computer.
There is an automatic penalty if you are not ready to start on time.
Wait outside the venue until you are called in.
v1.4 Practical Exam
Time/venue: week 13 lecture slot