PDF version of this document

Project Development

For a Gantt chart, see appendix A.

The following describes the preferred completion dates and does not exclude the possibility of a few phases overlapping. These are the 'ideal dates', but there is still time to accommodate changes if need be.

1. Readings on game theory and implementation of game playing programs need to be fully completed by the end of week 11.
2. Readings on advanced graphical models and coding them in GLUT must be completed by beginning of semester 2, although more of that could be complemented within the phase of maintenance and extension.
3. Requirement Analysis - to be completed by the end of week 3.
4. Specification - to be completed by the end of week 5.
5. High-level Design - to be completed by the end of week 7.
6. Low-level Design - to be completed by the end of week 11. This will require a great deal of work, therefore, a month is allocated for that stage.
7. Implementation - to be completed by the beginning of semester 2. Please note that these phase will have begun 2 months earlier (as indicated in the Gantt chart).
8. Testing - to be completed by the end of week 3 of semester 2.
9. Simulation - collection and analysis of data to be completed by the end of week 3 of semester 2. This should not really require more than a few days to complete.
10. Documentation - to be completed by the end of week 4 of semester 2.
11. Maintenance and Extension - to be considered as time allows.

Note that the above plan leaves a few weeks vacant until the demonstration. This is, in principal, a safety net that should be used mainly to cover for work on stages 5-7, which are possibly the most crucial ones. Shall any of these stages happen to progress more slowly than anticipated, they should occupy these weeks at the expense of research and extra work (c/f Section 4.2).