Frequently Asked Questions
and Frequently Answered Answers
Who can take the course, and what are the prerequisites?
CIS 4002 is open to anyone who has taken CIS 3000;
teams are built the same way that they are in CIS 3000, and the assignments and milestones follow the
model established by that class. CIS 4002 is also open to all masters of engineering students in the
computer science department (who may not take CIS 3000, but have the programming background to join
How is the course graded?
Students of CIS 3000 will find the grading format to be familiar, but slightly modified. As with
CIS 3000, there is a combination of group grades and individual grades, assigned across various
categories. In terms of percentages, your grade breaks down as follows:
-
60% - Completed game
-
15% - Documents (milestones, wiki, website, manual)
-
15% - Presentations (prototypes, alpha, beta, final)
-
10% - Class Participation
I use the following criteria in assigning each of these grades.
-
Class participation is assigned a letter grades according to your participation in
during topical and playtesting discussions. This grade is primarily determined by your level of
preparedness and organization on the day of your chosen topic. However, it also includes mundane
factors such as attendance.
-
All documents are assigned a letter grade, with the same grade being given to all
of the members of the group. You will be given an intial grade when the document is due, but may
resubmit any document for a better grade any time up until the final document portfolio is due
(limit one resubmission a week).
-
All prototype presentations are graded on a pass-fail basis. You will pass so long
as you have a completed prototype of some fashion that demonstrates adequate progress from the
last milestone.
-
All release presentations (alpha, beta, final) are assigned a letter grade. This
grade will reflect the amount of progress you have made since the last prototype, as well as the
quality of your presentation script.
-
For the completed game, I will assign you an individual letter grade determined by
both the quality of your grame and your peer reviews. Each member of your group will submit a peer
review documenting the quality of your contribution to the team.
As with CIS 3000, the idea behind this grading scheme is that, with such an open-ended project,
things do not always work out as planned. You should get used to things falling apart, forcing
you to start over. The grading system is designed to encourage you to keep working constantly
without penalizing you for "going back to the drawing board".
When and where does the class meet?
All classes meet TuTh 12:20-1:10 in CL3,
unless otherwise noted.
How do project teams work?
Students usually work in teams of about 4-6 people. Unlike CIS 3000, teams are determined by
students (we spend an entire class on team organization); however, the staff may reserve "veto"
power, or the ability to restructure teams. Artists, in particular, are a precious commodity
and often need to be reassigned to balance out teams.
What does CIS4002 count for?
For the most part, it is simply an elective to help you build your resumŽ in games. It is also one
of the primary courses in the game-design minor. It currently does not count as a 4000-level
project/practicum course, because it is listed as CIS/CS. However, there is some discussion
(not finalized) on allowing it to count for the software engineering vector.
|