CS 346 (W23)
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Assessment

This course is designed around a single project that you will design and develop with your project team. Most course components are tied to the course project in some way.

Team Grade (65%)

You will have three different types of deliverables this term.

Item What it addresses %
Project review Review planned features, design issues. 5%
Sprints (4) Demo new features and get feedback. 4 x 5%
Final submission Submit completed project and artifacts. 40%

1. Project Review

In the first few weeks, you and your team will choose a project, define requirements, and determine design issues.

  • You and your team will review your initial requirements and design decisions with a TA.
  • You do not need to submit anything: this is an informal presentation and discussion of your project to ensure that you have done the required preliminary work. You should be able to answer all of the points in the project review checklist, with details (e.g. GitLab issues logged, documentation from user interviews).
  • See the project review checklist (pdf, docx) for guidelines.

2. Sprints

Development is done in two-week iterations called sprints. We will have 4 sprints during the term.

Each sprint will be graded. Everyone on the team is expected to contribute, and everyone that participates receives the same grade for that sprint1.

  • Your initial kickoff will be a planning session with your team.
  • You will demo to a TA at the end of the sprint, and your team will be graded based on that sprint’s activities.
  • See the sprint demo checklist (pdf, docx) for guidelines.

3. Final Submission

There is also a final submission due at the end-of-term. This will be an offline evaluation, where we consider all completed features, how well they work together, application design, source code structure and so on. Everyone on the team will receive the same grade for this component.

  • We will grade this after the end of the term (and after the final sprint/demo has been presented).
  • See project artifacts for more details on what you should have completed.
  • See final checklist (pdf, docx) for marking guidelines.

You will be provided with a project specification that includes both Required Features and Additional Features. You are expected to deliver ALL of the Required Features, and doing so will earn you up to a B on the Final Submission.

If you wish to earn a higher grade on the Final Submission, you need to implement one or more extra features - either from the Additional Features in the specification, or ideas of your own. Check with the instructor if you are uncertain what to add!

Personal (35%)

A portion of your grade is based on quizzes and personal contributions towards the team project.

Item Calculated %
Participation Kickoff & Demo participation; Project contribution. 15%
Quizzes 5 quizzes x 4% each. 20%

You are expected to meet regularly with your team. This includes participating in sprint kickoffs, sprint demos, and in-class working sessions. Your participation grade will be calculated at the end of the term, and will be based on project data (e.g. your relative contribution) and attendance (e.g. did you attend and participate through the term).

Quizzes are a review of the lecture material and need to be done individually. See the quizzes pages for details.


  1. Failing to attend a demo will result in a grade of zero for that component IN ADDITION to any penalty to your participation grade. Under exceptional circumstances e.g. coop interview, documented illness, you may be excused from a demo without penalty, as long as you coordinate with your team and the instructor ahead of time. See the course policies for details. ↩ ↩︎