Project One

Operation Concepts: Team-based action/shooter game Unique classes with different play styles Sophisticated melee combat system Objective-based maps Team strategy emphasizing different class abilities as well as individual skill

System Requirements Purpose: provide entertainment (17+?) Different classes introduces depth of gameplay not seen in other fps games. Some classes will have a natural advantage over others. Both melee and ranged specialists such as ninja-like assassins and snipers Unique abilities such as invisibility, pet control, and damage over time

System and Software Architecture: Network code and physics engine (the Source engine) already provided, allowing developers to focus on the game Rely on Valve Corporation’s Source SDK which includes modeling programs, face posers, base code, and mapping programs.

Lifecycle Plan: Gamers are the primary users. Target casual as well as hardcore gamers. Developers provide bug fixes as well as game content updates via patches. Game and updates distributed through Valve’s content delivery system (Steam).

Feasibility Rationale: Proven market for fps games. Unique because of the involved melee combat system as well as class-specific abilities. Implementable because of Valve’s vigorous support for third party developers.