Project hand-in

Writing your report

There are different kinds of reports:

Structured as a research paper
Two-column format (IEEE, ACM for example have templates on Overleaf)
- e.g., https://www.overleaf.com/latex/templates/ieee-conference-template/grfzhhncsfqn
- e.g., https://www.overleaf.com/latex/templates/labreport-ieee-journal-paper-template/ypbfnkbvsyhw
8-16 pages as an indication depending on length of project, additional information can be added as appendices. This is rather a MAXIMUM (but not a hard requirement), you should aim to be concise rather just producing text and repeating yourself to get to a minimum number of pages.
- Note: 8-16 pages for all projects whether you are 1 student or a group of 4
This is a format that works and external examiners like. The ITU guidelines (on this page) do not apply well to computer science papers.
We can have one formal draft (that might not have all results etc yet) review about 2 weeks before the submission deadline. We can make an calendar meeting when Veronika will review your draft, if you email your PDF / Overleaf link before that time, you can get comments shortly afterwards.
You need to have an official ITU cover page. This is not important for the examiners, but SAP wants to have this. Find the guidelines on this on ITUstudent

Write early and often - make your Overleaf at the start of the project, make notes there about the papers you read as soon as you read them. Avoid "I will write the related work at the end of the project”.
Use these slides for some guidelines for writing (these were made for a 1st semester BDS course, but the tips do apply more generally). Please do go through these - often Veronika's first comment on reviewing a draft is "go back to the writing slides".

20230504_writing.pdf
Other tips for writing, and doing research projects in general - these were presented by Luca Aiello for all MSc students

howto_research.pdf
Check the sciwrite Coursera course https://www.coursera.org/learn/sciwrite