Project Work

TracNav(TracNav/TOC_PPS)?

Scenario

The game starts on the space station. Suddenly we are attacked by vicious aliens and the player is ordered to help to defend the station. But the aliens are to strong so the player has to fly towards moon. There he discovers that all the human defenses have been shattered. So he has to fly towards earth. The spaceship of the player crashes into the sea and the player is rescued by a navy vessel. Shortly after that the aliens arrive and start their invasion. So the player has to fight again against the aliens but this time on the surface of the earth. While you fight you have to reach a point (Gate, station,…) where the level is finished.

Topics

Difficulty:

++	very advanced
+	advanced
+-	moderate
-	piece of cake

Overview:

This table will soon be filled with tickets containing the tasks to reach our goal.

	Difficulty	Ticket	Owner	Project Page
Coding
FPS Weapon and HUD	+
Automatic defence mechanism	+-
Enhance Vertical-scroller mode	+
Enhance/Rewrite AI	++
Content Creation
Spacegate	-
Moon Surface	+-
Moon Station	++
Turret	+-
Spaceship	+
Enhance Vertical-scroller level (enemies, environment)	+

Milestones

• 05.Apr: Choose the Project
• 19.Apr: Project Plan Review (1 week)
  until now you have created on your project wiki-page:
  1. an UML-diagram of you module
  2. a timetable (similar to BspModel)
  3. started a developers journal (​here for engine developers, ​here for content creators)
• 19.Apr: Start of Implementation and Content Creation (5 weeks)
  1. write header files
  2. write the source itself
  3. collect reference materials
  4. make outlines (skizzen) of the objects you like to create
  5. generate content
• 17.Mai: Implementation stop, review in teams and design resync (1day)
  1. show what you did, and how it will go on
  2. are you sill in your development schedule?
• 17.Mai: Continue implementation/ content creation (2 weeks)
  1. the source implementation will continue and finish as fast as possible
  2. the content created should be finished as soon as possible too.
• 31.Mai: Project freeze: debug, documentation and testing phase (1 week)
  1. use GDB
  2. use Valgrind
  3. document with doxygen
  4. write a module description on the wiki
  5. write a model/content description on the wiki
• 14.Jun: Code finished and working perfectly
• 21.Jun: Convention and big show