Go to homepage 🏠

###
Scale for project NetPractice

##### You should evaluate 1 student in this team

### Introduction

Please respect the following rules:
- Remain polite, courteous, respectful and constructive
throughout the evaluation process. The well-being of the community
depends on it.
- Identify with the person (or the group) whose work is evaluated the possible
dysfunctions in their project. Take the time to discuss
and debate the problems you may have identified.
- You must consider that there might be some differences in how your
peers might have understood the project's instructions and the
scope of its functionalities. Always keep an open mind and grade
them as honestly as possible. The pedagogy is valid only and
only if peer-evaluation is conducted seriously.

### Guidelines

- Only grade the work that is present in the Git repository of the
student or group.
- Double-check that the Git repository belongs to the student
or the group. Ensure that the project is the one expected
and also check that "git clone" is used in an empty folder.
- Check carefully that no malicious aliases was used to fool you
and make you evaluate something that is not the content of the
official repository.
- To avoid any surprises and if applicable, review together the
scripts used to facilitate the grading (scripts for testing or
automation).
- As an evaluator, if you have not completed the assignment you are
going to grade, you then have to read the entire subject prior to
starting the defence.
- Use the flags available on this scale to signal an empty repository,
a non-functioning program, a norm error, cheating, and so forth.
In these cases, the evaluation process ends and the final grade is 0,
or -42 in case of cheating. However, except for cheating, student are
strongly encouraged to discuss the work that was turned in together,
in order to identify any mistakes that shouldn't be repeated in the
future.

### Attachments

#### subject.pdf

#### net_practice.1.4.tgz

### Preliminaries

If cheating is suspected, the evaluation stops here. Use the "Cheat" flag of the scale. Please do this calmly, wisely and use this button with caution.

#### Simple preliminaries

- Defense can only happen if the student being evaluated is present. This way everybody improves: by exchanging ideas and sharing knowledge with each other.
- Nothing submitted (or wrong file or directory) means 0, and the evaluation process ends.
- In order to grade your peer, you have to clone their Git repository on your machine.

Yes No

### General instructions

- Ensure that 10 files (1 per level) are present at the root of the repository. Ensure that they are not empty.

Yes No

### Mandatory part

- This project is about configuring small-scale networks that have issues to make them run. You have to download the file attached to the project's page (the evaluated student can show you where it is). Then, run the index.html file. A page will open in your web browser. Leave the login field empty to start the 'correction' mode. The evaluated student must solve correctly all of the levels in 15 minutes maximum. Using internet or any external resource to find answers is, of course, forbidden. The use of a simple calculator such as "bc" is tolerated but it will be the limit. You can ask questions about the different levels to the evaluated student.

#### Level 1

If something does not work as expected or is not clearly explained, the
evaluation process ends now.

Yes No

#### Level 2

If something does not work as expected or is not clearly explained, the
evaluation process ends now.

Yes No

#### Level 3

If something does not work as expected or is not clearly explained, the
evaluation process ends now.

Yes No

### Ratings

Don’t forget to check the flag corresponding to the defense

Ok Outstanding project
Empty work Incomplete work Cheat Crash Concerning situation Can’t support / explain code

### Conclusion