CPSC 219: Assignment Submission Requirements
Make sure that you carefully read the assignment specifications for each
assignment! (This is a set of general guidelines for all assignments and
each assignment may have a more specific set of things for you to do).
Points to keep in mind:
- Due time: All assignments are due at 4 PM on the
due
dates listed on the course web page. Late assignments or components of
assignments will not be accepted for marking without approval for an extension
beforehand.
What you have submitted in D2L as of the due date is what will be marked.
- Extensions may be granted for reasonable cases by the course
instructor with the receipt of the appropriate documentation (e.g., a
doctor's note). Typical examples of reasonable cases for an extension
include: illness or a death in the family. Cases where extensions will not
be granted include situations that are typical of student life: having
multiple due dates, work commitments etc. Tutorial instructors (TA's) will
not be able to provide extension on their own and must receive permission
from the course instructor first. (Note: Forgetting to hand your assignment
or a component of your assignment in does not constitute a sufficient reason
for handing your assignment late).
- Method of submission: You are to submit your assignment using D2L [help link].
Make sure that you [check the contents of your submitted files] (e.g., is the
file okay or was it corrupted, is it the correct version etc.). It's
your responsibility to do this! (Make sure that your submit your assignment
with enough time before it comes due for you to do a check).
- Identifying information: All assignments should include contact
information (full name and student ID number) at the very top of your program
in the class where the 'main()' function/method resides.
- Collaboration:
Assignments must reflect individual work, group work is
not allowed in this class nor can you copy the work of others. For more
detailed information as to what constitutes academic misconduct (i.e.,
cheating) for this course please read the following [link].
- Execution: programs must
run on the computer science network. If you write you code in the lab
and work remotely using a remote login program such as Putty or SSH. If you choose to
install Java on your own computer then it is your responsibility to ensure
that your program will run properly here. It's not recommended that you use
an IDE for writing your programs but if you use one then make sure that you
submit your program in the form of individual text ".java"
files (one for each class that you define).
- Source code: in order to get any credit for your work you must
submit all relevant dot-java files for the assignment (e.g.,
Driver.java). If you only submit your byte code
files (e.g. Driver.class) then you will not be
awarded any credit.
D2L configuration for this course
- You can (and really should) submit work as many times as you wish before
the due date
- D2L will only retain whatever files that you submitted the last time
that you uploaded to D2L, previous files will not be retained (e.g. if you
submit files: A.java, B.java, C.jpg the first
time and then you submit A.java the second time
then D2L will only have one file stored: A.java.
That means that you should submit every file associated with the assignment
each time that you want to submit something regardless of how many of those
files were actually changed since the last submission.