|
|
|
Guidelines
|
- Individual Work Policy
- Students in this course are allowed (and encouraged!) to submit homework
assignments in pairs. At the same time, each pair must work on their own. If you
are not sure what is the difference between cooperation and cheating, ask.
- Programming Exercises
-
You can use either Java or C++. Although this
is not plab, points will be taken for messy, unmodular or under-documented code.
Each exercise must be accompanied with a complete set on unit tests, using either
JUnit or CPPUnit. Notice: The unit tests are part of the exercise! It is
suggested that you start with the unit tests before writing the actual code.
Since we require a unified inteface to the program, in case of using Java you should
add a small shell-script that runs the Java class file. you can take the
sample script as a template. Don't forget to "chmod 755" it in
order to make it an executable.
All programming exercise must include a makefile. Calling "make all" should compile
the sources, create the requried executable, and run all the unit tests. You can refer to the sample makefiles
for Java and C/C++.
Each programming exercise must include a README
- 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 dexcription for each file.
- Any remarks you have about special cases, implementations, additional features
or anything else you think the checker should know.
- The name of the file should be "README". Not "readme", "ReadMe", "README.txt" or
any other combination you might think of. This mainly applies to students who
work in Windows environment.
You can use the sample README as template.
- Theoretical Exercises
-
There are two theoretical exercises. As a solution,
submit a file with your answers. This file has to be in one of the following
formats: text file (.txt), HTML file (.html), PostScript (.ps) or PDF (.pdf).
The name of the file should be exX.<suffix> (i.e. ex1.txt, ex2.ps). It should contain
the submitters names, logins and IDs.
- How to submit
- The exercises are submitted electronically. For each project create a zip file
called exX.zip (i.e. ex1.zip, ex2.zip, etc). Linux users:
create the file using
zip -9 -r <zip-file> <file-list>.
Submit the zip file using the course admin system that can be reached from the
administratives page.
- What if you can't finish the exercise on time?
- Relax. Submit what you have done, and explain what the problems you had to complete
the exercise. You will get partial credit for your work.
- What if your program is not working?
- It's not the end of the world. Hand in whatever you did, and explain what
works and what doesn't. If you want, you can also supply test files that you
developed, to demonstrate working and non-working parts of your exercise. Instead
of trying to hide the problem, be explicit and clear about it. You will get
partial credit for your work.
|
|