# Assessment

This course is designed around your team project, and most activities are tied to the course project in some way. You will be assessed on both your individual work and the team project.

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. These must be completed individually.

Quizzes are hosted in Learn (Submit > Quizzes).
Each quiz opens on Monday at 10:00 AM, and stays open until Fri 11:59 PM.
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 (and before the Wed class).
Quizzes are open-book, meaning that you may refer to lecture slides and course materials. However, you are not permitted to collaborate or communicate with other students about the quiz content. You must complete quizzes on your own time, and without assistance.

There are no extensions to the quiz deadlines! If you miss writing a quiz, you get a zero for that quiz. (The only exception is if you join the course too late to write the first quiz - see the instructor in this case).

# Weekly attendance

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

Your teammates are NOT allowed to sign you in - you must be physically present and sign the attendance sheet yourself to get these marks.

# 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
M1. Project setup	Register team, setup GitLab, post team contract.	2%
M2. Project proposal	Project identified, requirements logged.	5%
M3. Design proposal	Detailed design document.	6%
M4-M6. Product releases	Three iterations submitted	3 x 10% = 30%
M7. Final release	Final iteration plus documentation	25%

# Project Setup

Register your team in Learn, and setup the GitLab project space as documented. See Forming a team and Project setup 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 Product releases for details.

# Final Release

You will submit your final release with expanded documentation. See final release for details.