1.4 Grading guideline - mariusb03/WebAndApplication-group-18 GitHub Wiki
This section describes the grading guideline for examiners (including complaint handling). This information is also presented to the students for transparency. Examiners use the following grading procedure:
- Check all the mandatory (fundamental) requirements of the project. If everything is
covered, the project deserves a C-level grade as a starting point. If something is
missing, the examiner must comment on that, and the starting grade is reduced
accordingly.
- In case the project is having significant faults and is missing several important parts of the mandatory requirements (or the hand-in is missing mandatory information which makes the grading impossible), the examiner can decide that the project does not deserve a passing-grade and is hence evaluated with an F (failed).
- Check all the extra features the students have implemented. These must be clearly visible both from the presentation video, from the deployed system on the servers and in the source code. The extra features can increase the grade from 0 to 2 levels. For example, if the starting grade was a C, the final grade can be C, B or A, depending on how highly the examiner evaluates the extra functionality presented by the students. This also means that a project which is missing some mandatory requirements and hence has D or E as a starting grade, can go up only two grades (to B or C respectively). A project which got an F as a starting grade (too many important elements missing) can’t “be saved” by extra functionality. Grading schema Grading is done in two phases, as described above: Fundamental requirement check and Excellence check. The fundamental requirements differ among the courses (backend and frontend). Therefore, the schemas differ as well. The information wriaen in the grading schemas should be presented to the students (the group) as feedback for the grade (NOR: begrunnelse).
Grading schema
Grading is done in two phases, as described above: Fundamental requirement check and Excellence check.
The fundamental requirements differ among the courses (backend and frontend). Therefore, the schemas differ as well.
The information wriaen in the grading schemas should be presented to the students (the group) as feedback for the grade (NOR: begrunnelse).
Grading of fundamental requirements for IDATA2301 Web technologies
Identified extra features implemented by the group in IDATA2301 Web technologies:
- List the identified features here as bullet points. The features should be presented by the students in the video presentation. The teacher is allowed but not required to identify other features as well (something that the students did not present themselves)
Final grade in IDATA2301 Web technologies: here the examiner writes the final leaer grade for the project (A-F). Unless there is a very clear reason to do otherwise, all the members of the group get the same grade.
Comments: here the examiner can write summarizing comments for the project – something that explains why exactly that grade is chosen as the final evaluation.
Grading of fundamental requirements for IDATA2306 Applica0on development
Identified extra features implemented by the group in IDATA2306 Application Development:
- List the identified features here as bullet points. The features should be presented by the students in the video presentation. The examiner is allowed to (but not required to) identify other features as well (something that the students did not present themselves)
Final grade in IDATA2306 Application Development: here the examiner writes the final leaer grade for the project (A-F). Unless there is a very clear reason to do otherwise, all the members of the group get the same grade.
Comments: here the examiner can write summarizing comments for the project – something that explains why exactly that grade is chosen as the final evaluation.