CMPT 126 Harbour Centre

Submissions Instructions

SUBMISSION SERVER

Submissions will only be electronic. Keep at least two copies of anything you submit and also the email you receive from the submission server confirming your submission until the end of the semester.
Remember to also submit the PERSONAL INFORMATION FILE : submissionPersonalInformation.doc . Fill in the information. If it is a team work ALL the members in the team must complete the information to have the submission marked. Submit it together with your other files. Your signature may be typed
In some cases you will have to provide diagrams, for which you can use specialized software or you can write the diagrams in paper and then scan them to submit electronically.
Only one file is accepted by the submission server. For multiple files submissions you should compress them (.zip or .gz or .rar). You can find recomendations to compress your files in section Course description → Software.
To submit, follow the instructions in the Submission Server.
The submission server password is the one you use for Gradebook. Check section Admin → Gradebook .
Test the submission server early! If you have trouble using your ID and password, email csilop@sfu.ca.

DEADLINES AND LATE SUBMISSIONS POLICY

Unless otherwise specified and announced in class and in this website, assignments are due on the due date and time stated on each assignment and lab exercise.

Late submissions policy. If you have some problem and cannot finish your assignment or lab exercise by the due date/time contact the instructor before the deadline to get permission to submit late. Please notice that unless there are documented health problems and if approved (at the discretion of the instructor), a late assignment will have a penalty of up to 10% per day late. Therefore, it is highly recommended that you submit the assignment not later than the deadline

SOURCE CODE GUIDELINES

In every source code submission remember to include:

Use of comments to include author/s and date information.
Use of comments to clearly identify the submission (e.g. Lab exercise or assignment number).
Use of comments to briefly clarify and explain the purpose of the exercise/s.
Use of comments to describe each class, method, parameters and return values.
Meaningful naming of classes, methods and variables.
Use of TAB positions and clear indentations. This will be done more or less automatically depending on the editor you use for your source code.
When explicitly requested, you should follow the JAVA standard documentation style which would allow javadoc (see Appendix I in the textbook [L&L 6th ed also appendix I]) to generate the HTML pages documenting your classes. If you prefer you may follow the standard documentation style in all your submisssions (even if not required) as well.
You may want to consult http://geosoft.no/development/javastyle.html, in particular items #2 and #3 for general recommendations and naming conventions to write code.