- Weight: 3 ECTS
- Type: Oral test
- Date: 19-10
- Resit: 27-11
- Grade: At least 5.5 to pass this course
Assessment 1 tests your skills for frontend applications.
Note: your project must be a repository on GitHub named
frontend-applications.
We will download and archive your project when it鈥檚 due.
Create a client-side application in JavaScript with a popular framework based on given data. Evaluate the framework in groups.
This assessment focusses on goal 1 (learn how to create with libraries), subgoal 1 (read docs), subgoal 2 (write docs), subgoal 5 (manipulate elements), and subgoal 6 (load external data).
| 1-2 | 3-4 | 5-6 | 7-8 | 9-10 | |
|---|---|---|---|---|---|
| Application of subject matter | Git, npm, and a framework are used; the project runs without errors; data is loaded; there is a representation of data | Data is rendered with a framework; interpreting the representation is easier that interpreting the data itself | Data can be read and changed; changes to data are reflected in the interface; changes persist across page reloads | Representation and use of a framework go beyond an example: there are demonstrable additions like routing or creating data | 馃槺 The way the student applies subject matter is more advanced than what they were taught in class; let鈥檚 switch places |
| Understanding | There is substantial own code; the student can explain the code that exists | The student can explain some parts of their code, how some parts works together, and some technical choices | The student can explain every part of their code, how everything works together, and why software is used instead of alternatives; the project is structured logically | The project is complex but can easily be understood; alternatives to software covered in class was used that were great choices | 馃 The student deeply understands JavaScript and a geeky / nerdy conversation can be held about this |
| Quality | The project is handed in on time, working, documented, and on GitHub | Code style is consistent; code and project are partially documented | Code adheres to standards; docs cover what the project is and does | Code quality is good and enforced; docs are useful and professional | 馃摎 Code and docs both read like great books |
| Process | Process is partially documented | Process is properly documented | Choices are evaluated and documented; progress is demonstrated | Significant progress or iterations are demonstrated | 馃挭 What you did this course is amazing |
Note: each of this rubric鈥檚 rows is cumulative: for example, to get a 5-6 on application, you also need to have a 1-2 and 3-4.