Spring 2006
CS134 (Section 1): Computer Game
Design and Programming
CS 134 Section 1 (Course Number 27177):
Mon/Wed 1:30pm-2:45pm, Location: MH 222
Instructor: Soon Tee Teoh
Office Hours:
Tue/Thu 2:00pm-4:30pm
I am also available by appointment.
Office: McQuarrie Hall 211 (phone:
408-924-7227).
E-mail: teoh@cs.sjsu.edu
Course Website:
http://www.cs.sjsu.edu/~teoh/teaching/cs134/
Prerequisites:
The prerequisites
for this class are CS 130 and CS 151 (with a grade of "C-" or better
in each).
Adding and Dropping Classes:
The student is responsible for understanding the policies, procedures, and deadlines for adding and dropping classes, and for academic renewal, withdrawal.
Course Description:
This class introduces architectures and object-oriented patterns for computer
game design. Topics include animation, simulation, user interfaces, graphics,
and intelligent behaviors. Each student is expected to participate in a team
project requiring substantial programming.
Text: none
Course Objectives:
The
course objectives are:
To
learn about the software development process in the context of video games;
To
learn about object oriented techniques with regard to video game development;
To
learn about the basics of creating a game engine;
To
understand the use of simulations and physics in the context of video games;
To
learn about Artificial Intelligence in the context of video games; and
To
learn about collision detection in the context of video games.
Student Learning Outcomes:
Upon
successful completion of this course, students should be able to:
Create
a requirements document for a reasonable sized project;
Understand
the various stages of a software development process and use them in new
projects;
Apply
game design patterns in developing a new video game;
Understand
how a game engine can be put together;
Understand
how physics can be applied in video games and how to set up a simulation
environment;
Understand
and apply useful AI techniques like the A* algorithm in the context of video
games; and
Understand
common techniques for detecting collisions among objects in a video game.
Schedule:
This is the tentative course schedule. All
topics marked in Red-Bold-Italics are class activities which are part of the project
or midterm examination. Failure to be present at the appointed time will result
in loss of points.
|
Week |
Date |
Topic |
Assignment Due |
|
0 |
1/25/06 |
Introduction to Game Design |
|
|
1 |
1/30/06 |
Game Design Principles |
|
|
2/1/06 |
Introduction to Computer Graphics |
|
|
|
2 |
2/6/06 |
3D Graphics with OpenGL |
|
|
2/8/06 |
Lighting with OpenGL |
Project Proposal |
|
|
3 |
2/13/06 |
Project Discussion |
|
|
2/15/06 |
Project Discussion |
|
|
|
4 |
2/20/06 |
Texture-Mapping with OpenGL |
|
|
2/22/06 |
Game AI: A* Path Finding |
|
|
|
5 |
2/27/06 |
Game AI: Flocking |
|
|
3/1/06 |
Review |
|
|
|
6 |
3/6/06 |
Midterm 1 |
|
|
3/8/06 |
Game AI: FSM |
|
|
|
7 |
3/13/06 |
Game AI: Fuzzy Logic |
|
|
3/15/06 |
Collision Detection |
|
|
|
8 |
3/20/06 |
Game Physics: Collision Response |
|
|
3/22/06 |
Game Physics: Projectiles |
|
|
|
|
|
Spring Break |
|
|
9 |
4/3/06 |
Review |
|
|
4/5/06 |
Midterm 2 |
|
|
|
10 |
4/10/06 |
Game Physics: Laws of Motion |
|
|
4/12/06 |
Graphics: LOD, Visibility |
|
|
|
11 |
4/17/06 |
Intro to Networking |
Project V1 |
|
4/19/06 |
Play-testing |
|
|
|
12 |
4/24/06 |
Decision Trees and Neural Nets |
Play-testing Report |
|
4/26/06 |
Particle Systems, Terrains |
|
|
|
13 |
5/1/06 |
Intro to Animation |
|
|
5/3/06 |
Review |
|
|
|
14 |
5/8/06 |
Project Demos |
Project Final (5/7) |
|
5/10/06 |
Project Demos |
|
|
|
15 |
5/15/06 |
Review |
|
|
|
|
|
Teaching Methodology: The course is given through two lecture periods each
week. There will also be a designated discussion session and class activities. Students
in the course are expected to complete all the project assignments and learn
the material covered in lecture.
Attendance Policy: Lectures: Students should attend all lectures, not only because they are responsible for material discussed in the lectures, but also because active participation is essential to insure maximum benefit for all members of the class. Attendance will not be used as a criterion for grading. The student is responsible for knowing all announcements made by the instructor during lectures.
Course Requirements:
The course is composed of three components: assigned readings, lectures, project and exams. Examinations will be based on lectures.
Examinations: All examinations will be announced at least one week in advance and will cover material discussed in class and the text book. Test material will be drawn from lecture and any supplementary material provided by the instructor. Exact details about examinations in this course will be determined by the instructor. Typically there will be two in-class examinations during the semester and a two-hour final examination. Specific details will be made available before the exams are offered.
Grading: Your grade will depend on: exams (based mostly on class lectures) and project. Each student will accumulate points for all assigned project parts and exams. Keep your project and tests at least until you receive your grade. The instructor should be notified of any grading disputes and special circumstances regarding midterms and the project by May 15, 2006.
(1) 2 Midterm Examinations (2 @ 20%) 40%
An unexcused absence from an examination
will result in a grade of zero for that examination. The only valid excuses for
missing an examination are prior written approval from the instructor or a
documented medical emergency.
(2) Project
30%
Students will work in groups of 2 or 3
members (each group should turn in only ONE project). Each group is required to
present a 10-minute demonstration of their work. Each student in the same group
will receive the same grade for the project.
The project is graded on the correctness of
the program and the adherence to the requirements given in the assignment. A
submission that does not follow the instructions cannot be evaluated and
therefore will receive no credit. If the program code is written clearly, some
partial credit may possibly be given for partial correctness of the program
code.
Late Turn-In Policy: You may submit your project within 24 hours after
the due time for a 10% deduction of your grade for that part. You may submit
your project within the next 24 hours for a 20% deduction. No credit will be
awarded for projects submitted more than 48 hours after the due time.
(3) Final Examination 30%
The final exam will assume familiarity with
material covered in lecture. The final exam will be held on:
Section
1: Thursday, May 18, 12:15pm – 2:30pm
Grading Scale (in points):
100-95 A+
94.99-90 A
89.99-85 A-
84.99-80 B+
79.99-75 B
74.99-70 B-
69.99-65 C+
64.99-60 C
59.99-55 C-
54.99-50 D+
49.99-45 D
44.99-40 D-
Below 40 F
Disability Policy:
“If you need course adaptations or
accommodations because of a disability, or if you need special arrangements in
case the building must be evacuated, please make an appointment with me as soon
as possible, or see me during office hours. Presidential Directive 97-03
requires that students with disabilities register with DRC to establish a
record of their disability.” See http://www2.sjsu.edu/senate/s97-10.htm
.
Academic Dishonesty Statement (from
Office of Judicial Affairs):
“Your own commitment to learning, as
evidenced by your enrollment at