Assignments

Assignment 1 has been posted. It is due Monday, Jan. 21st. This is an individual assignment.

Please email your finished Rose petal file to our TA, on Monday, before 8:55 am

We will not be doing presentations for assignment 1.

Marking Scheme: Design: 10

Assignment 2. UML is due Wednesday Jan 30th. Code is due Monday, Feb. 11th., @ 8:55 am. Please zip up final Rose mdl file (one only) with source code and an application jar file that will work right out of the box (e.g. by double clicking on it once it is removed from the archive) and email it to your TA .

Marking Scheme: Design: 10 Final Product: 10

Project

Each group is to select their own project under the following guidelines:

  1. It should splittable into roughly equal model and view parts.
  2. It must be approved by me.

You should be careful to choose a project that is neither too ambitious nor too simple. Best is a project which you feel could be developed easily in the time frame but has considerable scope for improvement once the first version is working, giving you a potential range of deliverables.

Schedule

Wednesday, Feb 13th, 8:55 am: email me (in plain text please) a one or two paragraph Charter Statement together with a statement of who is responsible for the model part and who the view part.

Friday, Feb 15th, 5:00 pm: all projects should be finalized.

Monday, Feb. 25th, 8:55 pm: preliminary design in the form of a zipped up Rose model file should be emailed to Lujie & to whichever group has been assigned to conduct/critique your design review.

Tuesday, March 4th, 2:00-5:00 pm: Presentations will start at 2:00. and will be critiqued . 25% of the project mark. for preliminary design/presentation, of which 12% will be for design, 8% for presentation and 5% for your conduction/critique of the design review of the other group you are assigned.

Here is the list of projects for the course. Groups will be reviewed on Tuesday, March 8th at the time shown and the review will be conducted by the group shown (review groups were selected randomly). It is your responsibility to ascertain a valid email address for your reviewers and to email them your Rose files in pized up form on Monday, Feb 24th.

Group Game Model View Reviewers Time
1
Cribbage Michael Hobbs Bryan Coish
4
2:00
2
Tank Game Shane O'Connell Sean Jessome
1
2:20
3
Heroscape Stephen Foote Tim Smith
6
2:40
4
RPG Ryan Gaudon Brian White
5
3:00
5
Side Scroller John Hawley Ryan Martin
2
3:20
6
Side Scroller Pu Zhang Jeffrey Griffin
3
3:40

Reviews will be held in EN1000. The TA will queue up all the designs and bring them up in Star UML. Teams will have 10 minutes to present the design, with each member presenting his own half of the project. The review team may then make comments and ask questions for the last half of the time allotted.

Monday, March 24th, 8:55 am: Final project due. Please zip up final Rose mdl file (one only) with source code and an application exe file that will work right out of the box (e.g. by double clicking on it once it is removed from the archive) and email it to your TA .

Tuesday, March 25th, 2:00-4:00pm: Project presentations, in our lab. Each group should set up a demonstration of their game on a lab computer. The TA and I will be going around and asking you to demonstrate your game. We will be judging the quality of your game as a finished "product" at that time.

Marking Scheme: 70 marks total, of which

Preliminary Design 25% of which 12% is for the design (6% for team and 6% for either model or view individual), 8% for presentation (again, half team and half individual) and 5% for design review (individual).

Final Product: 75% (50% team, 25% for individual model or view part). We will consider the quality of the design (based on your final UML), the UML itself, the quality of the final product (based on the demonstration) and, briefly, the quality of your code.

Overall, 40% is individual, 60% is team.