Team      

Development Plan 
Table of Contents  
Introduction   
Editor   
Graphics   
Hardware  
Architecture   
Data  
Code  
Demo  
Motion Capture   
Scoring   
Team   
Behavior   
3D 
Task List   
Milestones   
 

The modular architecture of Vertigo is designed to achieve several goals. It divides the project’s code components among independent functional categories that allow for several programmers to apply themselves to the project concurrently. It allows for concurrent development on multiple platforms. And it creates a distinction between engine and game code which allows programmers to create object and non-player character behavior code independent of the engine.  

This chapter will briefly describe the architecture of the Vertigo software and outline the code components and data structures which define the project.  

Multiple Platform Support  

Vertigo consists of a kernel of code which is platform independent. Beneath this code are a 3D API and platform independent input and output code. Beneath this layer are drivers and platform dependent libraries like those of the PlayStations libgs and libgte. By isolating platform-dependent code, the Vertigo team seeks to make multiple platform development time and cost-effective.  

Major Project Components  

Vertigo is composed of several components, each of which is either platform-dependent or platform independent. The basic blocks are as follows:   

Platform-Independent  

• Game Flow User Interface
• Game Play User Interface
• Game Code
• Behavior
• Engine
• Graphics Pipeline
• Scoring 
• Motion Capture Data Loader
• Motion Capture Interpolation
• Motion Capture Playback
• Demo Mode Playback 

Platform-Dependent  

• 3D API Wrapper
• Low-Level Sound Playback
• Low-Level Music Playback
• Controller Input Interface
• Editor - On PC only, output is used by all platforms
• Mesh Loader
• Sound 
• 3D API Wrapper
• PC Networking - not available on PlayStation
• Environment Traversing Database
• Non-Player Character Behavior
• Object Behavior