Collect and process documentation into the final files
All our documentation and other files needs to be processed and put into the correct files and folders.
Final report as a PDF file (PROG1004_2022_Submission_groupno.pdf)
- Final submission should be delivered as a single PDF file according to the templates provided.
- Each team must deliver a final submission with all the attachments (see below). This should also include an evaluation of the teamwork (team reflection). Here, the team must summarize experiences dealing with the project-work and cooperation within the team.
Attachments to the Final report should include the following three templates previously provided on BlackBoard:
- Main report without its appendixes (15-20 pages)
- Don't forget to include an evaluation of the teamwork (team reflection) in your main report.
- Project manual including attachments
- Vision document
Wiki export is delivered as a PDF file (PROG1004_2022_Wiki_groupno.pdf)
- Include all wiki pages into one single pdf named PROG1004_2022_Wiki_groupno.pdf
- The wiki pages in the wiki structure can be found in the figure in the project description.
Program code is provided as a zip file (PROG1004_2022_code_groupno.zip)
- Be sure to include all the files you have. Highly recommend to include an executable file which you refer to in your user manual for running the program.
Post a link to the team's GITLab here - (code, issue board and wiki pages)
- URL to the teams GITLab repo - (code, issueboard and wiki-pages)
- If you have been using another tool than issue-board (ie Jira, Trello..) Make sure to give the teachers necessary access and URLs.
Remember: give the teachers reporter access to your gitlab-project - so that they can inspect your source code (guest gives only access to wiki) Seyed Ali Amirshahi Deadline for last push/ merge on git: Product including code must be finalized by Friday 29. April 15.00 this means no push/ merging after this deadline