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 (20%)
These component grades are awarded for individual performance.
| Component | What it addresses | Grade |
|---|---|---|
| Quizzes | 5 quizzes covering lecture and lab content. | 5 x 2% = 10% |
| Participation | Contributions to the team project. | 10% |
Quizzes
There are five quizzes, each worth 2%. See Lectures > 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. See Best Practices > Tracking Work
Team Grade (80%)
The following are project components that the team will work on together; everyone is expected to contribute equally to these deliverables. A single grade will be assigned, and everyone will receive the same grade (assuming they participate, see below).
| Item | What it addresses | Grade |
|---|---|---|
| Proposal | Project identified, requirements captured. | 5% |
| Sprint 1: Architecture | Features complete; process followed. | 10% |
| Sprint 2: User Interface | Features complete; process followed. | 10% |
| Sprint 3: Databases | Features complete; process followed. | 10% |
| Sprint 4: Final Review | Features complete; process followed. | 10% |
| Software Release | Completed project, including documentation. | 35% |
All of these components except the software release include an in-person demo. Demos are your primary avenue for project feedback and are extremely important! Team members are expected to attend and participate in every demo.
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 project 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.
Software 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.