Hide menu

TDDD23 Design and Programming of Computer Games


In this course you are examined on completing your tasks and the understanding of game design and game programming you demonstrate through your work (the game product) and throughout the course in plans and the oral examination. Whether or not your game is good, fun, or will sell is of no concern.

Examination is individual! This means you cannot divide the work in the group but everyone must know every aspect of your project. Teams larger than two will have to implemnet substanitally bigger projects - in code or creation volume. A situation may arise that two students working together may not both pass the course or may get different grades. This has actually happened in the past.

Examination criteria:

  • Quality of completed tasks and game project. (What is quality: see below - but not size or features)
  • Ability to incorporate game-design knowledge into the game project.
  • Volume of work - with regards to number of participants.

Grading criteria

In the course I use the following criteria when grading projects:
  • Well tested, polished game: That the game is always working and intuitive to use with regards to controls. Is complete with start screen and end credits.
  • In-game tutoring: the game teaches the player without stopping the player from playing.
  • Progression: the games evolves from intuitive and easy start into a suitable challenging level also including elements of variation.
  • Pick-up-and-play: Players can play directly, without being required to learn - solved by of in-game tutoring.
  • Complexity of the game development platform vs. the game content. A rapid-development environment such as Game Maker or Construct 2 and/or a technically non-challenging game-ideas requires a much longer game and/or more perfect implementation.

Page responsible: Erik Berglund
Last updated: 2013-08-20