Having broken down the problem into its constituent modules, it became possible
to draw up a project timetable. Total time for implementation and testing for
each module was estimated by the programmers and analysts. The module
dependency graph shown below was constructed based on these estimates and used
to create a coding schedule.
During the main coding phase of the project, the testing of the individual modules in isolation is also planned to occur in parallel. By testing a particular module shortly after it has been implemented, it will be possible to discover and resolve any problems efficiently.
The schedule on the following page outlines the task assignment to the programmers and analysts over the two-week period beginning 3rd February. During this time, the project manager is to coordinate the efforts of the team in addition to formulating a progress report towards the end of this period. Documentation is also to be written to accompany the code during this time.
Following the second review meeting on 16th February, the entire system will be built and thoroughly tested to conform to the acceptance criteria laid out in the specification. Documentation is also to be finalised by the end of this period.