Progress of an evaluation

Briefing

The evaluation starts with a short briefing (15 minutes, via MS Teams) about the practical organization of the evaluation. The explanation starts punctually and is projected by the supervisors in the evaluation room, so make sure you arrive in the evaluation room on time. Best to be there at least 5 minutes before the start of the briefing. During the briefing you can ask questions to the supervisors present.

During the briefing you can also digitally sign the following two documents via Dodona:

• Agreements for evaluations (this document)
• Sworn declaration

Digital signing is done by clicking the “Mark as read” button underneath the documents. You can also do this during the evaluation itself. You have only validly participated in the evaluation if you have digitally signed these two documents.

Evaluation

After the briefing you get exactly 2 hours to solve 2 assignments. These assignments are in line with the exercises that we presented you during the hands-on sessions.

At the start of the evaluation you will receive an e-mail informing you that the evaluation has started. This e-mail also contains a link to a hidden series on Dodona with the digital version of the assignments. There you can submit your solutions for the assignments.

During the evaluation you can continuously submit solutions via Dodona. The number of times you submit will not be taken into account during assessment. Only the last solution submitted before the deadline will be assessed. The way in which the final score for the course is calculated can be found under “calculation of examination mark” in the course sheet and in the introduction to the Dodona course.

From five minutes before the deadline expires, you will see a notification on Dodona that the end of the evaluation is approaching. Solutions submitted after the deadline will not be taken into account during assessment.

During the evaluation you can continuously ask questions to the supervisors present in the evaluation room.

If corrections, general announcements or additional clarifications need to be made during the evaluation, this will be done orally in the evaluation room.

Practical agreements

• the evaluation must be completed on your own laptop (byod.ugent.be/en/¹)
• the evaluation is open book / open Internet
• all e-mails will be sent to your UGent e-mail address during the evaluation
• the following resources can be used during the evaluation (non-exhaustive):
  • course book The Practice of Computing using Python (digitally available on Ufora)
  • slide shows of lectures (digitally available on Ufora)
  • recordings of lectures (digitally available on Ufora)
  • own solutions of exercises (digitally available on Dodona)
  • sample solutions of mandatory exercises (digitally available on Dodona)
  • additional manuals, summaries, … (digital and hard copy)
• the following actions are not allowed during the evaluation:
  • communicate with fellow students (verbally, via phone, via paper, via e-mail, via other analog or digital channels)
  • communicate with other persons (verbally, via phone, via paper, via e-mail, via other analog or digital channels)
  • communicate with chatbots and programmer assistants that use artificial intelligence
• in case of doubt whether you may use certain resources or tools, you can always explicitly ask the supervisors
• to submit the evaluation blank, it is sufficient to notify the lecturer by e-mail on the day of the evaluation

Useful tips

• try to plan in advance how much time you initially want to spend on each assignment
• total duration of evaluation: 2 hours
  • the available time to solve the assignments is kept tight deliberately
  • depending on your level of mastering the programming skills, you will be able to solve a larger part of the assignments and earn more points
  • if you have time to spare, check whether there are better (read: shorter or more efficient) solutions than the ones you have worked out so far; better solutions yield extra points (if necessary also comment on the improvements made during the process)
• use comments in your source code
  • give pointers on the structure and non-trivial passages of your code to the person who will review your code
• under “previous editions” in the introduction to the Dodona course, you’ll find links to previous editions of the course, including the assignments that were presented as mandatory exercises or during evaluations and exams
  • use these assignments to get an idea of the kind of assignments you can expect during the evaluations
  • use these assignments to get prepared for the evaluation, because you can also submit solutions for those assignments