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
- Students should be done with the implementation of their projects.
- To take out more from the discussions, we encourage students to be open minded even to unfamiliar topics.
| Title | Duration |
|---|---|
| Status About the Projects | 10 minutes |
| Experience Based Activity | - |
| Advanced Topics | - |
Notes for tutors:
1: Status About the Projects (10 minutes)
- 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.