Assignments

There will be two assignments for COMP6700.

Important

• From the date of return of your assignment you have 2 weeks in which to query you mark. After that time your mark is final.

• No group work is permitted for the assignment. We do encourage you to discuss your work in the labs and lectures, but we expect you to do the assignment work by yourself.

• We do take plagiarism seriously! You should read the chapter in the Department of Computer Science Student Handbook that discusses assessment (Chapter 6, pages 22-25), particularly the sections headed Misconduct in examinations (which also applies to assignments and other forms of assessment) and Collaboration versus misconduct in assignments.

• Please make sure you have read the assessment scheme, and that you understand it (if not please discuss it with the course coordinator).

Assignment specifications and due dates

• Assignment One:  Due 18:00pm EST on Thursday 25 April 2013 (week 8)

  Supporting material

  • web-1.txt mini-web structure file to use as a sample (is you need more, use these: web-2.txt, web-3.txt and web-4.txt).

  • The Marking Guide (refer to the assignment paper!)

  • The submission protocol (refer to the assignment paper!)

  • Late submissions: If you submit after the above deadline, your submissions will be penalised as follows:

    How late	< 6 hours	6…24	24…48	48…72	72…96	> 96 hours
    Deduction (from 15 marks)	-0.5	-1	-2	-4	-8	-15 (forget it!)

    Late penalties apply even if you submit just one file after the deadline.

  ---

• Assignment Two:  Due 18:00pm EST on Sunday May 26, 2013 (week 12)

  Supporting materials and Instructions

• This assignment project will be managed by the source code management (SCM) system called Mercurial. Instructions on how to use Mercurial will be given in Lab 6, when you will start your work on the assignment and learn how to use the SCM to manage and submit it.

• The original code, which you will extend further needs to be downloaded as an archive ass2.zip. Instructions how to compile, generate documentation and run it are provided in the file README. For convenience, I also include a Makefile to simplify all of these operation --- (on the command line) run:

  1. make --- to compile
  2. make doc --- to generate JavaDocs
  3. make run --- to run

• You can use your favourite Java IDE (Eclipse, Netbeans, IntelliJ IDEA, or what have you) to study the code and extend it further as the assignment tasks require. In fact, despite using an IDE is not necessary to work on the assignment successfully, it is extremely beneficial given the amount of JavaFX API which can be put to use in the assignment code. A modern IDE will guide and facilitate the selection of a class or its attributes through the code-assist feature. Video tutorials on how to use Eclipse, Netbeans or IntelliJ IDEA are abundant on the Web. Google (or Bing, or Yandex, or Bai-du) them up!

Note: The Doc comments in the source code are not quite complete; their purpose is to demonstrate how a source code needs to be documented. You will have to add missing doc comments in the existing code (to document your understanding of its working), and also include doc comments for every significant addition that you will make to the program code. This is an assessable item which is a part of the Assignment assessment scheme.

• The Marking Guide (refer to the assignment paper!)

• Hints and FAQs (if any)

• The submission protocol (refer to the Lab 6)

• Late submissions will be penalised as follows:

  How late	< 6 hours	6…24	24…48	48…72	72…96	> 96 hours
  Deduction (from 20 marks)	-0.75	-1.5	-3	-5	-10	-20 (forget it!)