 

  
  IMGD 4000 - Objectives
  
Assumed Knowledge:
-  Introduction to program design
     (e.g., CS
     1101
     or CS
     1102).
-  Object-oriented design and programming
     (e.g., CS
     2102).
-  Systems programming concepts
     (e.g., CS
     2303).
-  Software engineering
     (e.g., CS
     3733).
-  Basic technical game development skills
     (e.g., IMGD
     3000), including:
  
    -  Game engine architecture
    
-  Iterative technical game development process
    
-  Scene management
    
-  Input controls
    
-  Simple AI
  
 
Goals:
-  To be able to participate effectively as technical developers in
     interdisciplinary teams with artists to produce games.
-  To be able to quickly become proficient in a new game engine,
     regardless of the programming language or framework.
-  To expand technical game development skills beyond those listed
     under 5 in Assumed Background above, including game physics,
     steering and multi-player networking.
-  To be conversant with some of the more important advanced and
     emerging technical concepts in game development (e.g., advanced
     camera control).
Objectives:
-  Each student will be a member of a team consisting of 2 or 3
     technical developers and 1 or 2 artists (from IMGD 4500), which
     together produces a game on schedule with deadlines and
     milestones and using team coordination tools, such as source
     version control.
-  Students will develop C++ and scripting code for the Unreal
     Engine game engine (as opposed to building an engine from scratch
     in C++ in IMGD 3000).
-  Each students will implement individual game elements applying
     new technical skills learned, such as steering and multi-player
     networking.
-  Each student will be individually tested on their knowledge of
     important technical game development concepts presented in
     lectures.
 Return to the IMGD 4000
     Technical Game Development II home page
 Return to the IMGD 4000
     Technical Game Development II home page
Send all questions to Mark
Claypool.