Click to go to Development Process

The development methodology is a staged iterative one in which each module is intended to pass through each stage only once. Figure 1 outlines the development activities and deliverables for each stage. Also see Project Responsibilities.

Figure 1: Development methodology

Click to go to Figure 1 Draft project plan

The draft project plan introduces the project; describes the development methodology; identifies the module structure and format; assigned resources; project contacts; responsibilities; development tools, backup strategy, file names and file access; defines project deliverables and email and web site addresses for tracking and storing all deliverables.

Click to go to Figure 1 Final project plan

The final project plan includes comments from a review of the draft project plan. Approval to go ahead with the project must be indicated by an email from the customer to the project email address before module development is started.

Click to go to Figure 1 Draft modules

A draft version of each module will be produced and distributed, in HTML or Acrobat format from the project web site, for customer review and approval. All illustrations will be in draft form. The target for draft modules is 70% completion in content, organization, and format. Each draft module must be reviewed by the customer to verify technical accuracy and completeness. Comments must be marked on a printed copy of each module. Approval of each draft module, with or without comments, must be indicated by an email by the customer to the project email address before work is started on Beta modules.

Click to go to Figure 1 Beta modules

A beta version of each module will be produced and distributed, in HTML or Acrobat format from the project web site, for review and approval. Each beta module will include comments received on the draft version and illustrations will be in their final form. Beta modules will be technically accurate and at least 90% complete in content; their organization and format will be in their final form. Each beta module must be reviewed by the customer to verify technical accuracy and completeness. Comments are to be marked on a printed copy of each module. If required, an index will be added and each module edited to ensure format consistency, correct grammar, spelling, and pagination. If possible, beta modules will also be verified by at least two typical users to ensure procedural accuracy, completeness, and suitability. Approval of each beta module, with or without comments, must be indicated by an email from the customer to the project email address before work is started on Final modules.

Click to go to Figure 1 Final modules

A final version of each module will be produced. It will include all comments received on the draft/beta versions of each module. PostScript and Acrobat or HTML versions of each module will be prepared and delivered from the project web site and/or CD. Approval of each final module must be indicated by an email from the customer to the project email address.