>87.5: 1, >75: 2, >62.5 : 3, >50: 4, ≤50: 5
Please note that the above schema MAY be subject to a grading curve for individual tests or assignments.
| 1/3 | written test (computer (offline)) - must be passed |
| 1/3 | programming project |
| 1/3 | programming assignments |
| participation | contributions are rewarded with a "+"for students with a positive grade, each " +" improves the
average term grade by 0.1
(10 + improve one full grade)
|
To avoid plagiarism and prevent cheating, all grades (including tests, projects and assignments) require a short oral defense to be valid.
Late assignment policy: the points for each assignment
filed after its due date are multiplied by 0.8 for each started week after
the due date.
For example: a student files an assigment one day late and would receive
97 points if filed before the due date. The student gets 97 * 0.8 = 77.6
points instead. Another student files an assignment with 100 points 16 days
after the due date. 16 days means the third week after the due date has
started. Hence the student is awarded 100 * 0.8 * 0.8 * 0.8 = 51.2 points.
Please consult our discord group for the assignment links.
The best way to learn programming is to write code. Have fun!
The project has to be done with git (any public git hosting is ok). The repository URL has to be shared w/ the teacher. The teacher must be granted read access (in case of non-public closed source projects).
| 50% | properly working software |
| 20% | autotests (proper coverage of everything that is not GUI code) |
| 10% | README.md (project description; compile instructions; user manual with images) |
| 5% | build files (cmake, meson or make) |
| 5% | consistent coding style |
| 5% | wireframe |
| 5% | proper license in repository |
Curriculum in the Legal Information System (see attachment 1/9 B.1 according to subject table I.2)