UTM: General Information
| Instructor: | Jeremy Sills |
|---|---|
| Email: | j.sills@toronto.edu |
| Office: | CCT 3077 |
| Hours: | Monday, Wednesday 11 - 12 |
| Lecture: | Monday 2pm-4pm |
| Tutorial: | Friday 12noon-1pm |
Please review the course information sheet.
Announcements:
Exam aids Apr 16
You can bring anything hand written or
printed to the exam, the text, course notes,
assignment printouts, other texts.
You can not bring electronic devices.
Office hours Mar 30
During the exams I intend to have regular office hours Monday, Wesnesday and Friday.
To be sure call ahead or send an email.
Final submission Mar 30
Submit the final version of your assignment files.
Team evaluation Mar 28
For students who missed class on Monday,
print the evaluation sheet;
complete it and bring it to class on Friday.
Monday Mar 26 class Mar 23
Each team should bring a working version of their solution program so
we can do a dry run of the tournament making sure that the different
parts can interact with each other.
6a due date Mar 23
You can have an extra 24 hours until March 25 at 1:pm.
6a submission Mar 21
What to submit? Your player and other files with strategy (ai) included.
These files must compile and run with the game manager. Try your files with .class
files from other player teams. Careful that you keep your strategy
to your team. No need to submit the ,class files.
Lawrence Mandel visit in 301 class Mar 19,
Mar 18
Q&A with a Software Dev
Lawrence Mandel,
Firefox Program Manager, Mozilla
Sample exam Mar 16
Here is an old exam.
MORE Exercise 5 amended files Mar 9
Here are the Mar 9 amended
files.
I have fixed an ambiguity in the interface.
I have removed the SetupPlayer interface and incorporated a modified method
inside Player.
I have updated the code accordingly to behave correctly.
Exercise 5 amended files Mar 9
Here are the Mar 9 amended
files. They are compressed as a .zip file.
Andrai has provide a short explanation of the new files:
1) Deck.java: Contains the implementation of cards. CardObject
2) GameManager.java: Keeps track of the players and the overall game
(score).
3) GameRound.java: Keeps track of the current round, it's tricks etc.
Exercise 5 amended files Mar 7
Here are the amended
files.
Exercise 5 amendments to code Mar 5
Requested
changes to your interface.
Exercise 5 starter code Feb 28
There is the
starter code for exercise 5.
Exercise 4 submission Feb 24
One submission per team is enough.
Reading week office hours Feb 22
Reminder I am in today and will be in on Friday.
Exercise 4 ideas Feb 22
As with other exercises you have to make
decisions.
From exercise 3 you should have a good idea of what
objects are part of your solution.
Decide what data should be stored in the different
classes. Decide what actions (methods) should
be implemented in each class.
For example when a trick is played
should the comparison of cards
to see which one is highest
be done in the game manager class or in the card class?
Compare your choices with your team members.
Why should the players teams continue working on the
game manager and the game manager team continue to work
on the player class? Soon the members of the class must agree on
interface between the game manager and the players.
You have to agree among the different teams what is
in each of the different classes. And what the
interface between players and game manager should
contain.
Teams Feb 14
The teams are posted.
Exercise 1 Feb 10
Exercise 1 marking details.
Exercise 1 Feb 7
If you did not pick up your exercise 1 during tutorial last Friday
pick it up from me on Wednesday
Discussion board Jan 18
The 301 discussion board in Blackboard is now available.
TA contact Jan 18
The TA's perferred contact address is
jgorzny at cs dot toronto dot edu
The The submit page Jan 18
The submit page for Exercise 1 is ready.
Lecture/presentation schedule Jan 13
The schedules of lectures and presentations are listed in the menu on the left.
Report any mistakes.
Tentative schedule Jan 11
The tentative lecture schedule is here.
Computer related failures Jan 11
The following links lead to different sources of computer related failures:
http://catless.ncl.ac.uk/Risks/
http://www.csl.sri.com/users/neumann/neumann-book.html
http://www.csl.sri.com/users/neumann/
Process for text report presenters Jan 11
1. On the Monday a week prior to your presentation email the instructor.
2. On the Tuesday the instructor will reply with an outline of the
topics to be covered.
3. On Wednesday meet with the instructor with any questions.
4. On Friday send a copy of your presentation to the instructor.
5. Monday present.
Process for Tool and Failure report presenters Jan 11
1. On the Monday a week prior to your presentation email the instructor
with your topic.
2. On Wednesday meet with the instructor with any questions.
3. On Friday send a copy of your presentation to the instructor.
4. Monday present.
Tutorial Jan 6
There is a tutorial as scheduled this week, Friday 12 noon - 1 pm.
Assignment Jan 6
The assignment is posted.
