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 specifically for front-end. You've worked on optimizing the production environment of the application. For example, implementing a build or asset pipeline or optimizing modularity of the code by using preprocessors. Another example is optimizing for performance by minifying assets or compressing images.
A teacher will try out your feature and look at the code. You will show you can create a quality project in which you apply the subject matter of this course and that you understand it. 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 front-end.
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.
- 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鈥檚 done.
| Conditions |
|---|
| Source code is publicly available on GitHub in a repository |
The project is documented in the wiki and has a readme.md |
Cites the sources used; APA style in readme.md |
| A live version of the application is deployed |
| 1-2 | 3-4 | 5-6 | 7-8 | 9-10 | |
|---|---|---|---|---|---|
| Application | There is no production optimization | The production optimization isn't implemented in code or partially implemented but gives errors and is buggy | There is a production optimization and the technical implementation works. The set-up is integrated into the project and merged. | There is a production optimization, the implementation works and team members benefitted of code you've written | The production optimization is technically advanced and complex. It has a modular set-up and is resilient by streamlining the asset pipeline. |
| Research | There is no research in the wiki | There is research in the wiki but very limited, not enough to understand your process | There is research about what production topic you've implemented in the team repo, you've documented your process and ideas and you've researched your topic. You've written about how you implemented your production topic. | The research is in-depth, you've technically described how you wrote your code and did research on alternativates | The wiki reads like a book. Your production topic is toroughly researched and you've technically but clearly documented your progressive enhancement and code. |
| Quality | There is no cohesion in the front-end code of the application. All features are individually made and don't work together. | There was an attempt to unify the front-end in a single application, but it's buggy or not consistent. | Front-end architecture has been normalised among all team members. There are basic guidelines each team member follows. The HTML, CSS and JavaScript are written using previous standard. | The application is really well integrated. There's a single strategy chosen and code is modular and applies only when needed. | This application has production-ready code. It works flawlessly and could have been made by a professional development agency. |
Note:
You'll need a > 5.5 for each row to pass: you can't compensate between rows.
Each of this rubric鈥檚 rows is cumulative: for example, to get a 5-6 on concept, you also need to have a 1-2 and 3-4.
- We don鈥檛 like plagiarism and report it to our assessment committee (examencommissie in Dutch).For more on plagiarism read our statement of academic integrity.
- Grades will be published and communicated trough MS Teams and Brightspace. We also publish grade lists on Brightspace based on student numbers.