Sep 25, 2022  

Add to Portfolio (opens a new window)

CST 186 - Introduction to Game Programming

Credits: 2
Introduces principles of game and simulation programming through hands-on creation of simple games. Explores text-based and graphics-based game development through algorithm design, development, implementation, testing, and documentation. Incorporates text, graphics, sound, and animations in game design. Includes Top-Down Design, Object Oriented Programming, simple physics, basic Artificial Intelligence, and game engines.

Prerequisite(s): CST 173  (or CST 170) with “C” or better
Corequisite(s): None
Lecture Hours: 30 Lab Hours: 0
Meets MTA Requirement: None
Pass/NoCredit: Yes

Outcomes and Objectives
  1. Define the specifications for a variety of games.
    1. Access and analyze specifications and information to plan and design games.
    2. Choose a text-based or Graphical User Interface environment for a game.
    3. Select objects to use in a game; e.g., text, graphics, sounds, and animations.
  2. Develop logic for text-based and simple Graphical User Interface game programs using critical thinking.
    1. Apply the sequence, selection, and iteration program constructs to game development.
    2. Compare and contrast the use of variables, strings, tuples, links, and dictionaries in the construction of a game.
    3. Use Top-Down Design to break the logic of a game into components.
    4. Apply Object Oriented Programming concepts to game program logic.
    5. Describe Artificial Intelligence and game engines.
  3. Translate the logic of a game or simulation algorithm into a programming language.
    1. Code game programs in a programming language.
    2. Compile and correct syntax errors.
    3. Test, debug, and correct logic errors.
  4. Use a variety of input/output media in game programming.
    1. Incorporate text and graphics in a game program.
    2. Enhance a game with music, sound effects, and animations.
    3. Store and display scores and game statistics.
  5. Produce documentation for games.
    1. Document game program code.
    2. Create internal help documentation and make it available to users executing a game.
    3. Create external documentation for a game.

Add to Portfolio (opens a new window)