• Register/Submit/Getgrade Instructions
• Coding Style Guidelines
• General Guidelines - Programming Exercises
• Submission Guidelines - Programming Exercises
• Submission Guidelines - Theoretical Exercises
• Late Submissions, Exemptions
• Appeals

 

Register

Every student should register to the electronic submission system. This is done by following the Register  link (also in the home page). Just enter your login name and your password and follow the instructions.

Simply follow the Grades  link from the home page. Enter your login & password, and all your grades will  be presented.

• Follow the Submit from the home page.
• Choose the exercise you wish to submit.
• Enter the file you want to submit, either directly or using the 'Browse' option. Important: The default filter for 'Browse' is *.html (i.e. all files with .html suffix), change it to *.jar)
• Press 'Submit'. The application will respond with the message:

        Total size transfered: XXX bytes.
• Make sure that the size matches. If XXX = 0 it probably means you've entered the wrong name.

Submission Guidelines - Programming Exercises

• Programming exercises will be available on the net (see the schedule).
• You should submit programming exercises electronically (see instructions below), and also submit a printout in the course box on floor -2 (see instructions below).
• Please follow the submission guidelines carefully! Exercises are corrected using automatic scripts. Failure to follow the guidelines will cause a reduction in your grade.
• Important: Please read the regulations regarding late submissions.

• Submission Block:
  Each source file should begin with a submission block. This block identifies the file and students.
  The submission block MUST BE in the exact following form (cut and paste, and don't forget to replace the details with the correct details):

  /*
   Exercise No.         : 1
   File Name            : FooBar.java
   Name (First Last)    : Umberto De-Miguel, Silvio Di Palma
   Student No.          : 03239243-19, 05612387-23
   login                : miguel, palma
  */

• readme file:
  You should include a plain text file called readme (it's readme, not Readme, nor README, nor readme.txt, nor REAME.txt) that contains:
  
  • The FIRST line MUST contain your logins (and only them) separated by a comma, e.g.,

  gadish,yanko
  

  • DO NOT include any other stuff in the first line!
  • The next lines of readme should contain your names and IDs.
  • The next lines of readme should be a list of all files and a short (one line) description of each file.
  • Next in readme comes a short documentation of your exercise:
  • Note any assumptions you have made.
  • Describe the data structures you used (e.g. hierarchy of classes, etc..) and why you chose to use them.
  • Give a short description of the algorithms you implemented.
  
  The readme should be concise - no more than 2 printed pages (or one printed on both sides...)

• Electornic Submission

Submit a jar file called exN.jar (where N is the number of the exercise) containing the following:

• The source files of your program (i.e. *.java). Include only files that are related to the program.
• The readme file.
• Your jar file must NOT contain *.class files or any other junk.
• Paper Submission

In addition, you should hand-in a hard copy of your exercise to the Data Structures box (on floor -2). Here's what you should do:

• Print each file on a separate paper. Do not concatenate the files!
• Make sure the printout is readable.
• The printing must use a fixed-width font (i.e., a font in which each letter has a fixed width, for example, courier new is a fixed width font).
• Make sure the printed lines do not fall off the right edge of the paper.
• Make sure you hand in printouts with correct indentation. Your indentation might look good on the screen but get spoilt in the printout (3 spaces are sufficient).
• The printed program must match exactly the one you submit.
• The order of the printed files should be as follows:
1. readme
2. Interface definition files (if any).
3. Class definition files. If the exercise includes inheritance, you should put each base-class before its derived classes.

Submission Guidelines - Theoretical Exercises

Theoretical exercises will be published on this web site, and should be submitted in the course box on floor -2 by the specified date and time (see the schedule). Late submissions of theoretical exercises will not be accepted in any case. Make sure you clearly write your name, student ID, and login name in the top left corner of the first page.

Late Submissions, Exemptions

You may submit a programming exercise up to 3 working days after the submission date. However, you will lose 5 points for each day you are late (not counting Fridays and Saturdays).

Please Note: Late submissions (of more than 3 days) will not be accepted.

In justified cases, such as miluim or sickness, you should approach one of the assistants for an extension. If you had miluim you should attach the ishur to the printout when you submit. As a general policy, we will grant an extention of the same length of the absence. The extention must be approved by us, it is not given automatically.

NOTE: Only an extention that has been approved by us by e-mail is valid.

Appeals

An appeal on an exercise grade may be submitted up to two weeks after the relevant exercise has been returned. This is a strict deadline - late appeals will NOT be considered!
Please bear in mind: when you submit an appeal, your grade is re-evaluated. In certain cases, this may result in a reduction in your grade.
If you nevertheless think your grade has been unjustfully reduced, and you wish to submit an appeal, do the following:

• On a blank piece of paper, write in a LARGE and readable format:

 
APPEAL ex#
-----------------
<login 1> <id#1>
<login 2> <id#2>

For example:
 
APPEAL EX2
-----------------
moshe 98749873
dina 29093409


• Write a detailed description of your appeal on a separate piece of paper.
• Attach both papers, with the first one at the front, to the printout you submitted, which includes the grader's remarks. Appeals which will not include the original printout will not be considered.
• You must hand your appeal personally to one of the assistants.