Latest update Nov 28, 2023.

Lab Handin Checklist

As lab handins are part of the examination in the course, there are some things that you should account for before handing in the solutions to make the process smooth for everyone involved. Please ensure that:

• You are the one who have figured out, designed and written the solution. We have strict guidelines related to plagiarism.
• Lab skeletons and code snippets from lectures may of course be used, but it is your responsibility to ensure that you understand how they work as part of the solution.
• The guidelines regarding hand-ins for examination have been followed.
• The lab assistants will not review or provide thorough feedback on partial solutions, or solutions that are not handed in. This allows us to handle feedback in a transparent manner.
• The code works and covers all of the functionality asked for in the lab. and it has been tested using automated tests/concrete examples that must be included in the upload.
• Please double-check that the code does what is expected! Please note that we also have non-functional requirements on the solutions - hence a solution that works may still require some work to pass.
• Tests may be written using proper test frameworks, but you may also have some examples. The important thing is that you have thought about different cases in your solution.
• As a recommendation, think about big data! How would your solution work if you tried it with huge input values or data sizes?
• You have thoroughly read and understood the lab instructions.
• The later labs are increasingly open-ended w.r.t. to the possible solutions. This is by design, to allow you to show your understanding of how to model and implement solutions in a functional-style manner.
• If you get stuck or have doubts about something, please first check the existing course material, lab skeletons or the Q/A documents. If you still have issues, feel free to ask in class or during lab sessions.
• For issues that cannot wait until lab sessions, send a mail (to all assistants). However, to avoid unnecessary email loops, please be detailed describing what the issue is and what you have already investigated to solve it. This helps us identify the issue and give you a prompt response.