# Assessment

This course is designed around a single project that you will design and develop with your project team. Most activities are tied to the course project in some way. You will be assessed based on both your individual work, and the project that you collectively produce.

The course schedule lists the due dates for each component.

# Individual Grades (32%)

Grade items earned individually.

Item What it addresses Grade
Quizzes Quizzes covering lecture content (weeks 2-11). 10 x 2% = 20%
Weekly attendance Attending class, participating in activities (weeks 2-13). 12 x 1% = 12%

# Quizzes

You have weekly quizzes that you must complete during the term.

  • Quizzes are hosted in Learn (Submit > Quizzes).
  • Each quiz opens on Monday at 10:00 AM, and stays open until Wed 10:00 AM i.e. you have 48 hours to complete each quiz.
  • Each quiz is 15 minutes long, and you are only allowed one attempt.
  • Quizzes are based entirely on material presented in lecture videos and slides for the week. It's recommended that you write the quiz immediately after reviewing those materials.
  • Quizzes are open-book i.e. you may refer to slides and any notes that you may have taken during class. However, you are not permitted to collaborate or communicate with other students about the quiz content. You must complete quizzes on your own.

# Weekly attendance

We will take attendance in Wed and Fri classes. If you attend one or more of these classes, and sign the attendance sheet, you will get the attendance mark for that week.

# Team Grades (68%)

Team grade items are earned by the team, and everyone on the team receives the same grade. This includes various project milestones.

Item What it addresses Grade
GitLab setup Register team, setup GitLab. 2%
Project proposal Project identified, requirements logged. 6%
Design proposal Detailed design document. 6%
Product releases Three iterations submitted 3 x 8% = 24%
Final submission Final iteration plus documentation 30%

# GitLab Setup

Register your team in Learn, and setup the GitLab project space as documented. See forming a team and creating a GitLab project for details.

# Project Proposal

Provide details on your project idea, including users, and requirements speecifying the features that you plan to implement. See project proposal for details.

# Design Proposal

Present technical decisions that you have made prior to development. This needs to include UML diagrams of your high-level architecture, and other diagrams as indicated. See design-proposal for details.

# Product Releases

There are multiple development iterations, where you will plan and implement features. You will get marks for delivering a product release, including supporting documents and a product installer. See submission for details.

# Submission

You will submit your final product release, along with expanded documented. See final submission for details.