Students will in groups of three (or two) perform peer review, i.e., assess other students' exercises. The review is written to a file called FEEDBACK.txt, located in the student's exercise directory. Below is a checklist of points to consider when writing a review.
For a program:
- Are the files easy to locate? That is, does the directory has a logical name? Are individual files given names according to the exercise?
- Is the program easy to read? More specifically,
- Are variables given self-explanatory names or names in accordance of the mathematical description?
- Are enough comments in the code?
- Is the code well formatted (use of whitespace etc.)?
- Is the code well organized in terms of functions or classes? (Also consider overuse of functions and classes in simpler problems!)
- Does the program answer the various points in the exercise?
- Does the program work?
- Are there any (automatic) verifications of the code?
- Are you able to run the code?
For a report:
- Is the report easy to locate?
- Is the report well formatted (title, author, sections, paragraphs, right spacings, low amount of typos, nice layout, introduction, conclusions, etc.)?
- Is the text logic and easy to follow? Is there sufficient explanation of what is done?
- Are the results correct?
- Are there any verifications of the results?