Assignment Submission Rules
COP3530

To receive full credit for your assignments the following rules have to be followed. Violation can cost up to 100% of your Assignment credit. Please read the information on the page carefully, you are responsible for the knowledge of the material put up here. If anything in this page is ambiguous, please clarify with the TA's immediately. No excuses will be entertained. 

• Please put your full name, student ID, section, and CourseWorX ID on every assignment. This is only way for us to know that its your work. Insert this information as a commented part before the beginning of your code.

            The format is:

                        Name : XXXXXXX

                        UF ID: XXXXXXX

                        CourseWorX ID: XXXXXXX

                        Discussion section # : %%%%%%%%%%%

           If this information is missing you get 0 credit for the assignment. 

• An on-time software submission of your assignment is required, through CourseWorx, or your assignment is considered late. Late assignments receive an automatic zero.

• Graders will test your code with their programs. Mere passing of all the test cases does not ensure full credit. There will be time and space constraints on the implementation of the algorithm. This forms a major part of your assignment grade. Your program should run within acceptable space and time constraints. These constraints ( if you have to take care of, will be specified in the specs for the problem ). After each assignment is graded, the policy and the test cases will be available online. You can download these, run them on your code that you submitted and report discrepancies if found.

• If the problem specifies the name that you should give your class, you must give your class that name, or it will cost you up to 30% of credit for that question.

• Typically, you will be asked to extend a class and include a new member function. The signature of the function must be the same as that specified by the problem. The return type, function name and the parameters passed should be the same as that specified in the specs. Violation can cost 100% of the assignment grade.

• Each of the following is required, and if not satisfied, will result in a zero for the code portion of an assignment:

  1. The java file (say, ClassName.java) must compile successfully.

  2. A softcopy of the source code (ClassName.java, NOT ClassName.class) needs to be submitted in the jar file via CourseWorX.

  3. The submitted file must be properly jarred. Improper jarring of files again can cost 100% for that assignment. The simplest syntax of the jar command is as follows.

     To create a jar file:

        jar cvf (jar file name) (file 1) (file 2) (file 3)...

     To extract the contents of a jar file:

        jar xvf (jar file name)

     For example, if you have ClassName.java and readme.txt to submit for a problem, use the following command to jar them properly into a file called MyAssignment.jar:

        jar cvf MyAssigment.jar ClassName.java readme.txt

     Warning: Some editors have the capability to add your class to a jar archive. Do not use this capability to make your jar files because this only adds the class file, not the java file to the archive. To be sure, use the method of jarring described above.

     Note: You can verify that your submission was successful by downloading your submission from CourseWorX and successfully unjarring it.

• No copying of assignments is allowed. Please look at the Academic Dishonesty policy. We will run MOSS on your assignment and view cases of cheating seriously.