You've worked iteratively (formative) on your product and finish with an oral test (summative) where you present your final prototype with your team.
First you'll present the whole project as a team to all the teachers. Then you'll show how you contributed to the project and explain if you reached your own goals you've set at the beginning of the project.
You will answer questions in such a way as to demonstrate sufficient knowledge of our goals.
This is a team assignment but you'll be graded individually! Each prototype contains an individually recognizable contribution of you based on the learning goals and topics of this course. So, you need to show you worked on something for back-end. For example; you can't just work on the CSS of the project because that was your role in the team.
This is an assessment, not another moment for feedback. So you will be graded. There isn't much time for additional feedback or troubleshooting technical issues.
Besides the individual oral test you'll present your application with your team by recording a 8-10 minute video. Which acts as a replacement of a live presentation in front of a classroom. Your teacher will watch the video before the individual assessment.
To give you a suggestion on how to approach this; hop on a MS teams call with all your team members and hit record. Show what the web application can do and then have each team member explain how they contributed. Alternatively you can pre-record your video (use quicktime, loom etc.) and have someone edit it into a coherent video. It's up to your team on how to approach this.
Make sure you hand-in your video in the assignment on Brightspace.
Since we have limited time make sure you come to the assessment prepared:
- Bring your computer and make sure it's charged and connected to Wifi.
- Make sure your webcam, microphone and screen sharing works in MS Teams
- Have the latest version of your feature ready in your browser.
- Have the latest version of your code ready on GitHub.
- Have the latest version of your code ready in your editor.
Make sure your repository stays online after the assessment is finished, we might want to check the code handed in on GitHub after the assessment. We also want to download and archive your project when it’s done.
You can use the peer review document (from A1) as a checklist (AVV) for your assessments to check if everything in your repository and application is in order.
Download a .pdf version of the Rubric
| Improve | Standard | Advanced | |
|---|---|---|---|
| Application | |||
| The topic the student picked is implemented in the matching app and the code is of decent complexity | |||
| Research | |||
| The student documented the research they did for the topic in their wiki, shows relevant decision making and reflects on the quality of the feature contributed | |||
| Understanding | |||
| The student can explain every part of their code, how everything works together and can offer alternatives |
Note:
The column in the middle are the standard criteria for this assessment to pass. If one of these rows isn't sufficient you have failed this assessment.
- A teacher can refuse to take the assessment when you show up late regardless of the reason. That means you go straight to the re-sits and will be graded with a
1.0. Usually teachers give you a small window of time after the assessment(~5 minutes) to show up. - We don’t like plagiarism and report it to our assessment committee (examencommissie in Dutch).
- Grades will be published and communicated trough Email and/or Slack. We also publish grade lists on Brightspace based on student numbers.