Last update: April 15, 2012

There will be various small to medium size assignments and one more important programming project. It will be indicated explicitly if the work is to be done individually or in teams. The option to work individually will be possible.
During the first part of the course (before the reading break) there will be lab exercises to work on, for practice and/or due for submission about a week after they are posted. Brief assignments will also be provided, due a couple days or up to about a week after they are posted.
After the reading break, lab exercises will continue to be provided mostly as practice, and also medium size assignments and the project will be provided. Medium size assignments will be given more than a week to work on, as it will be announced. The project will include some intermediate submission and as a whole it will be given approximately 3 to 4 weeks to work on, as it will be announced.
Check the Course description → Academic honesty section for academic honesty policies.

The assignments, project and their due dates will be posted here as the course progresses.

Assignment #1 - Individual work - Initial explorations of course website. Brief Assignment #1. Due date/time: Wednesday January 11, 3:30 pm. Due date passed
Brief review Assignment #2 - Individual work - Introduction to Java, invitation to reflect about studying activities. Brief Assignment #2. Due date/time: Wednesday January 18, 3:30 pm. Due date passed
Brief review Assignment #3 - Individual work - Flow of control, loops. Brief Assignment #3. Due date/time: Wednesday February 8, 3:30 pm.Due date passed
CodeWrite Assignment - Individual work. Due date/time: Monday February 27, 11:59 pm.Due date passed
- Introduction to CodeWrite slide show.
- CodeWrite Assignment description.
- Link to the CodeWrite website.
RollTTT Game Due date passed

Design, code and revise assignment - Team work. Teams of two. (You can also work individually if you prefer so but it is not encouraged). Original Due date/time: Thursday March 15, 11:59 pm. If you submit by this deadline you will get 5% bonus.

Extended Due date/time: Saturday March 17, 12:00 noon. If you submit by this deadline you will not get the bonus points but you will not get any penalty either.
- General description of the assignment.
- Problem solving suggestions.
- See Readings and notes section for design guidelines and design guidelines and java notes.
- More detailed description of the assignment.
- Initial incomplete analysis and design documentation:
- Initial incomplete code:
- Sample runs:
  - Sample run 1 - no winners.
  - Sample run 2 - winner small type.
  - Sample run 3 - no winners.
  - Sample run 4 - winner main diagonal.
  - Sample run 5 - winner small type (run with non-revised design version)
- See notes about clarifications discussed in class and sent via email, notes 17, 17B and Q&A document in the Readings section
MPL Recursion assignment - Group work, up to 3 members. Recursion. Due date passed
- MPL assignment, questions about recursion. Due date/time: Saturday March 24, 11:59 pm. SUbmit directly via the MPL website and ONLY IF YOU SUBMIT AS A GROUP also submit a comment file via CourSys.
Final Project, Wizards and Witches game

Design, code and revise assignment - Team work. Teams of up to three (3) members. (You can also work individually if you prefer so but it is not encouraged). Last strict possible due date/time: Wednesday April 11, 3:15 pm.
- General description of the final project.
- More detailed description of this project.
- Initial documentation and initial code.
  - See Readings and notes section for design guidelines, in particular addressing this project, notes 28 and 28b.
  - Initial code
- Sample runs and screen shots:
  - , Sample run 1 - creation of board and two naive players.
  - Screenshots sample run 1: board just created -- P0 did the first move
  - Sample run 2 - Vold killed player P1.
  - Screenshots sample run 2: board just created -- both players moved -- Vold killed P1
  - Sample run 3 - maximum number turns reached.
  - Screenshots sample run 3: board just created -- players in same cell, both are naive, no interaction -- game over, no winners.
  - Sample run 4 - evil attacks helpful twice.
  - Screenshots sample run 4: evil attacks helpful -- evil attacks helpful again --
  - Sample run 5 - helpful makes a deal with points - notice also validation.
  - Screenshots sample run 5: helpful shares points --
  - Sample run 6 - helpful makes a deal first but then evil robbed all horcruxes and won.
  - Screenshots sample run 6: board and players just created -- helpful makes a deal (all cells are grey, all horcruxes are in the players boxes) -- evil robs all horcruxes.

ASSIGNMENTS EXERCISES SOLUTIONS.

These solutions should not be shared with students who are not registred in CMPT 125 Burnaby during the current semester 2012-1.

Brief assignment #1 solution
Brief assignment #2 solution
Post Lab questionnaire week #4 - solution
Solution and comments to brief assignment #3 - "While if" problem
Brief assignment #3 solution
Brief assignment Participation Lab week #8 solution
Solution RollTTT assignment. The code presented here corresponds to a design where there is a Player class representing one player, who has one big card (hence the naming of the files ending in RD - revised design).
Solution Wizards project.

MARKING SCHEMES.

Your questions and answers about Assignments? See the Q&A Tests and Assignments section.