Digital Communications in the Modern World Course - 67594
Home
Course Material
Exercises
Guidelines
Administratives
Guidelines
Course Policy and Grading
  • Course grade is composed 10% of exercises, 90% of final exam.
  • There will be 1-2 practical exercises and two theoretical exercises. 2 of the practical exercise can be done in Java, the other in C++.
  • All the exercises can be done in pairs.
  • All exercises submission is mandatory. Student which will get an average of less than 55 in the exercises will not be able to take the exam.
  • Late submission result in 5 points penalty per day. (Not including Friday/ Saturday).
  • Course news forum
  • Course news forum is now open. The forum should be read frequently.
  • Individual Work Policy
    Students in this course are allowed (and encouraged!) to submit practical homework assignments in PAIRS. At the same time, each pair must work on their own

    How to submit
    Exercises are to be submitted electronically. For each project create a tar file called ex#.tgz (i.e. ex1.tar). Submit it using the course admin system that can be reached from the administratives page. Tar command should be: "tar cvzf ex1.tgz README [list of files]". Any mistake in creating the tar, adding unneeded files, missing files (like README), README with wrong format, doing jar instead tar, lower/upper case mistakes etc, forgetting your partner name, will result in 10 points penalty since these mistakes will cause the automatic tests to fail. To help you test your tar I will create a script that checks it. Reference to the script is found inside the exercise.

    README submission
    The README file should include the following details:
    • In the first line should be the login(s) of the author(s), comma seperated (and nothing else).
    • The personal details of the author(s).
    • The name of the exercise.
    • A list of the submitted files, with a one line description for each file.
    • Any remarks you have about special cases, implementations, additional features or anything else you think the checker should know.
    • Answer to exercise theoretical questions (if any)
    You can use the sample README as template.