CAT|ICS 3U – Computer and Information Science

robocode

Design 1 tank to engage in battle with other tanks designed by the other students. Your team will be given 5 days to get your tanks ready. On the sixth day, you will enter an elimination tournament against other teams. Your tank will be marked on code efficiency and win/lost battles. The following are the requirements for this assignment:

Requirements

  1. Each team will consist of 1 or 2 student/s max.
  2. Tanks must be designed based on the tanks found in the Robocode application; others will be disqualified.
  3. Each team must use and modify2methods.
  4. Teams must disclose where the tank’s code was written (i.e.:Sitting Duck, Tracker, etc.)
  5. “Walls” an”Interactive” are the only tanks you may not use.
  6. Teams must be able to successfully upload and compile tanks for battle.
  7. Tanks can’t be controlled manually.
  8. Submit a folder with the member’s names.
  9. The folder must contain Word submission and tank code. Tank code has to be submitted in Java format (.java)
  10. Do not print anything.
  11. A word processedsubmission (do not print) explaining, in detail, the idiosyncrasies of the tank, what methods make the tank different, how the methods work, why these methods were selected and from where. Requirements:
  12. Cover page with team’s members full names, tank name, date and course code.
  13. You must use the following 3subtitles: Tanks:which were your sample tanks. Methods: name the 2 “borrowed” methods (no marks will be given for extra methods). Methods’ Details : explanation of the methods. In this section you will successfully explain by comments how the tank was modified. Provide a copy of the original tank followed by the modified version, highlight in red font the modified lines.

Tournament

  1. Each team must battle all teams in the tournament.
  2. Battles are 1 v 1. (Need to know how to transport a tank in a USB).
  3. Each team will be awarded 3 points for a win, 1 point for a tie and 0 point for a loss.
  4. Battles are best 3 out of 5.
  5. A team will not be allowed to participate in the tournament unless the written portion of the assignment has been submitted.
  6. If a team refuses to battle another team, a loss will be awarded to the refusing team.

Marks

  1. A tank MUST compile AND compete in the tournament in order for a team to get a mark higher than 50% (minimum Level 2). Otherwise, a failure mark and/or Level 1 mark will be assigned.
  2. Modifications will be marked based on complexity (i.e.: colours vs. events).
  3. Submission: Thursday June 16th. Battles: June 17th.

CPT | robocode / final examination15%
name:
ICS 3U / iona secondary school
application | 12 / 0 / 1 / 2 / 3 / 4
Tournament Participation / Team played under ¼ of all participants. / Team played ¼ of all participants. / Team played ½ of all participants. / Team played ¾ of all participants. / Team played all participants.
Tank Complexity / Tank was not modified. / Changes in the tank were not challenging at this stage in the course. / Changes in the tank were somewhat original and demanding. However, the changes were well below the student’s ability. / Changes in the tank were original and demanding. However, the changes could’ve been more challenging given the student’s ability. / Tank modification was original, complex and challenging.
Program Execution / Tank did not upload. / Tank uploaded successfully.
communication | 16 / 0 / 1 / 2 / 3 / 4
Submission / Team did not submit any requirements. / Submission portion met few requirements. / Submission portion met some requirements. / Submissionportion met most requirements. / Submission portion met all requirements.
Comments / Few non-descriptive comments were used in program. / Some non-descriptive comments were used in program. Program has many spelling errors. / Some comments were descriptive. Program has 3 or 4 spelling errors. / Most comments were descriptive. Program has 1 or 2 spelling errors. / All comments were descriptive and free of errors. Syntax is also free of errors.
Syntax / Syntax was not indented and spaced. / Syntax is poorly indented and spaced. / A small part of the syntax was properly indented and spaced. / Most of the syntax was properly indented and spaced. Some handwritten information / Syntax was properly indented and spaced
Naming Conventions / Student did not follow proper naming conventions. / Proper naming conventions were used for a few identifiers and classes. / Proper naming conventions were used for some identifiers and classes. / Proper naming conventions were used for most identifiers and classes. / Proper naming conventions were used for all identifiers and classes.