This course teaches students the fundamentals of digital game design with an emphasis on team-based development. In this course students will produce a significant game using techniques and principles derived from established state-of-the-art industry practices. Topics include an examination of game design theories, programming architectures, audio-visual design and game production.
- Instructor: Stephen Brooks
- Lectures: Tuesday & Thursday, 2:35-3:55 pm, SIR JAMES DUNN 135
- Lab Hours: 1:35-2:25 pm, Mondays, CS 133 (no TA) & CS 143 (with TA help)
- Learning Center Help Hours: Wednesdays 10-11am and Mondays 4-5pm
- Office Hour: Fridays 3:00-4:00 pm, CS 327
(Optional) Course Texts - check if there is one or more you like...
General Game Design & Development in Unity
Game Development in Unity Only
- Explain the origins of modern digital games.
- Discuss the demographics and sociology of games and online communities.
- Produce documentation for a game design.
- Design an appropriate interface for a given game genre.
- Design game levels and challenge hierarchies.
- Discuss the role of diegetic and non-diegetic game elements
- Construct and iterate through a paper based simulation.
- Develop a multi-level game as part of a team.
- Script object and character interactions.
- Construct and program in-game particle systems.
- Develop and integrate character animations.
- Setup and script physics interactions.
- Test and debug an interactive game.
Hardware & Software
Hardware: A windows machine with a decent graphics card.
Software: Unity 3D, Google SketchUp, GIMP, MS Visual Studio.
- 20% Programming Assignment
- 10% Project Proposal
- 15% Project Progress Report
- 55% Final Project Report, Demo and Presentation
All work you submit must be your own. It is fine to discuss problems, but when it comes time to submit solutions,
the materials you hand in must be done individually, by yourself. Any materials referenced must be attributed.
All suspected instances of academic dishonesty must be reported to the Senate Discipline Committee.
In particular, you should never show another student code that you have written for an assignment in this course,
nor should you write code for another student to use in his/her assignment. Note that this specifically prohibits
working with other students when writing the code for your assignments. As I said above, it is fine to discuss problems,
but the code you submit must be your own, written by you alone.
For further information regarding academic honesty at Dalhousie, please see the University plagiarism website.
Also note that all assignments and projects will be checked for plagiarism using automated software.
Late Submission Policy
Late assignments will be penalized 5% per day (or part thereof). You may not receive credit for work that is more than 3 days late.
The project CANNOT BE HANDED IN LATE (no exceptions).
Return to main page.