Assessment
Most activities in this course are tied to the course project. You will be assessed on both your individual work and the team project. The course schedule lists the due dates for each of theses components.
Individual Grade (30%)
| Component | What it addresses | Grade |
|---|---|---|
| Quizzes | Understanding lecture content. 5 quizzes. | 5 x 4% = 20% |
| Participation | Level of contributions to the project. | 10% |
These course components are graded individually.
Quizzes
There are five quizzes, each worth 4%. See Quizzes.
Participation
At the end of the project, we will assess your individual contributions to the project, based on your development journal, completeness of your issues and your Git commit history.
Team Grade (70%)
| Item | What it addresses | Grade |
|---|---|---|
| Proposal | Project identified, requirements captured. | 5% |
| Sprint 1: Architecture | Features complete; process followed. | 5% |
| Sprint 2: User Interface | Features complete; process followed. | 5% |
| Sprint 3: Databases | Features complete; process followed. | 5% |
| Sprint 4: Final Review | Features complete; process followed. | 5% |
| Software Release | Completed project, including documentation. | 45% |
Everyone on the project team is expected to contribute equally to these project components. A single grade is assigned to each component, and everyone that participates will receive the same grade.
For components that include a demo, all team members are expected to attend in-person and participate. Failing to attend or participate in a demo will result in a grade of zero for that deliverable. See Syllabus > Policies > Course Project.
Proposal
You are required to submit a written proposal, and present it to your TA in-person. Your proposal should answer the question of what you are designing and how it addresses the requirements. See Project > Stages > Proposal.
Sprints
A sprint is a two week project iteration. At the end of the sprint, you and your team will demo your progress to your TA in-person. Your grade will be based on your presentation, as well as the progress that you made during the sprint. See Project > Stages > Sprints for a detailed breakdown.
Release
After your final demo, you will submit a software release: a formal release of your product, with expanded documentation. There is no demo required. See Project > Stages > Release.