TDP013 Web Programming and Interactivity

Examination and deadlines

In this course, the student's knowledge is examined through two lab assignments, a project, and an ethics task. For the lab assignments and the project, students are expected to work in groups of two, but the examination in the course is individual. If for some reason you want to work individually, you must notify the course examiner. Each individual carries out their own oral presentation of the project part and must then be able to run the code on their own and answer questions about the lab assignments and project. Students who work together must therefore take responsibility for being able to present and explain all parts and aspects of the lab assignments and project. It has happened that students who have worked together have received different final grades in the course.

Sign up via Webreg

Sign up via Webreg as early as possible, for both lab part (LAB2) and project part (PRA1). Shortly after registering in Webreg, you will be given access to a project/repo on gitlab.liu.se. Please also register with gitlab.liu.se.

Criteria for examination

• Demonstrated quality in the implementation of laboratory exercises and projects. Quality in this context means the application of appropriate web technologies, well-tested and well-organized code.
• Demonstrated knowledge and ability to reflect on web technologies through laboratory exercises and projects.

Grading criteria

• For grade 3: All laboratory exercises completed according to applicable instructions and a functioning project that meets the basic requirements.
• For grade 4: Same as for grade 3 + one of the extensions on the project page.
• For grade 5: Same as for grade 4 + implementation of both extensions on the project page.

Deadlines

The deadlines for the labs above should be seen as general guidelines for you to know whether you are in phase or not. Labs submitted after the deadline are corrected with lower priority, but current labs always have higher priority.

Before completing a lab, it should be presented to a lab assistant during a scheduled lab session or by emailing a short screencast (see instructions for each lab). The purpose of the presentation is to check that you understand and can talk about your code, but also to catch the most common errors. However, an approved presentation does not mean that the code is approved.

When presenting the project, it is expected that most things work as intended, but minor bugs can be fixed before the final submission. If you are aiming for a higher grade, it is important that the extension(s) work during the presentation. In case of major bugs, if a function is missing or if for some reason you miss the report, you can supplement it by emailing a screencast according to the instructions on the project page.

The final deadline for the course (2026 HT) is October 24th, 2026. Any supplements and first-time submissions that arrive after the final deadline will be corrected at the upcoming examination dates unless otherwise decided in contact with the examiner.

The first upcoming examination date for HT26 is the last day of the re-examination period for VT1 2027, i.e., January 9th, 2027.
The second upcoming examination date for HT26 is the last day of the re-examination period for VT2 2027, i.e., March 19th, 2027.

Ethics seminar and project report

If you know that you will miss the ethics seminar or the project report, it is good if you notify the examiner in advance, as this may affect the group division.

Examination during the course instance for incomplete elements

If you have not been approved for an element after upcoming examination dates (see above), it means that you have to finish the element according to the next course opportunity. Note that labs can be changed between course instances and examiners may be changed. It is always the labs for the current course instance that apply when reporting, unless otherwise decided in contact with the examiner.

Rules for examination of computer lab assignments at IDA

You are expected to do lab assignments in group or individually, as instructed for a course. However, examination is always based on individual performance.

It is not allowed to hand in solutions copied from other students, or from elsewhere, even if you make changes to the solutions. If there is suspicion of such, or any other form of cheating, teachers are obliged to report it to the University Disciplinary Board.

Be prepared to answer questions about details in specific code and its connection to theory. You may also be asked to explain why you have chosen a specific solution. This applies to all group members.

If you foresee problems meeting a deadline, contact your teacher. You can then get some help and maybe the deadline can be set to a later date. It is always better to discuss problems, instead of, e.g., to cheat.

Any kind of academic dishonesty, such as cheating (e.g., plagiarism, use of unauthorized assistance, and use of prohibited AI-based assistants) and failure to comply with university examination rules, may result in the filing of a complaint to the University Disciplinary Board. The potential penalties include suspension, warning.

Policy for handing in computer lab assignments at IDA

For all IDA courses having computer lab assignments there will be one deadline during or at the end of the course. If you fail to make the deadline, you must retake the, possibly new, lab course the next time the course is given.

If a course deviates from this policy, information will be given on the course web pages.

Page responsible: Huanyu Li
Last updated: 2026-08-28