Week 12: Fixing Bugs (Imp.)
Goal
During this week's session, students will focus on a set of advanced topics related to implementation and quality assurance. It will the first step towards becoming a more seasoned software engineer, and paw the steps for next semester project works. The session will structured as a series of discussions.
Expected Results Before This Week
Weekly Progress Check rules
- Be prepared to show your results at the beginning of class.
- Presenting teams are selected randomly each week. The same team may be selected repeatedly.
- If your team is selected and there is no relevant work recorded before the session, 3 points will be deducted. Any relevant demonstrable work avoids the deduction: the weekly score is then between 0 and +3 points, depending on quality and completeness.
- A missing expected result can cause a point deduction only once, but you should still catch up: later work may depend on it, and these results usually contribute to the tasks required for your desired grade. More about salary for tasks
How Weekly Progress Checks work · More about penalty and bonus points
This week's expected results
- By the final deadline, have the project in its finished state and make that state easy to understand from GitLab. Close or clearly mark completed work, leave unfinished or deliberately dropped items visible, and make sure the final result can be demonstrated without relying on undocumented last-minute changes.
- Create a GitLab issue about what you enjoyed during the course and project, and why. Point to concrete activities, situations, tools, or ways of working, and link the relevant course webpages when they help illustrate what you are referring to.
- Create a GitLab issue about what you disliked, found frustrating, or would rather avoid in the future, and explain why. Difficult or unpleasant experiences are valid reflections too—even when they later became useful lessons. Link relevant course webpages where possible.
- Create a GitLab issue about what you learned during the semester: about software development, teamwork, and yourself as a developer. Use concrete experiences from the project and link course webpages that help connect those experiences to topics discussed during the course.
- Create a GitLab issue revisiting the motivations and professional goals you described near the beginning of the semester. Describe what stayed the same, what changed, and whether anything during the project strengthened, weakened, or redirected those goals. Link back to relevant early-semester course materials where useful.
- These reflection issues are there to make you stop and think about your own journey, not to judge it. Your opinions, motivations, likes, dislikes, or changes in direction will not improve or reduce your final grade; there is no expected 'correct' conclusion or preferred path.
Notes for tutors:
1: Status About the Projects
- Each team summarizes the current status of their project in a few sentences (1-2 minutes per team).
- Tutor will show the remaining deliverables and deadlines on the Grading page.