transputer.gif (9866 bytes)
Brock University
Department of Computer Science

COSC 4F00: Generic Project Phase Plan

Fall 2017 Instructor: Vlad Wojcik mail.gif (1189 bytes)Support: John Futers

darkDot.gif (501 bytes)PROJECT PHASE PLAN:

The teams are requested to present their project phase plans. The generic plan is listed below; it consists of five phases. Successful completion of each phase is worth 10% towards the final mark in the course.

Each team is free to propose a modified phase plan, together with the team marking scheme. Such plans are subject to approval by the course instructor.


darkDot.gif (501 bytes) GENERIC PROJECT PHASE PLAN:

darkDot.gif (501 bytes)Definition Phase (Identification of Requirements)

  • Primary Objectives:
    • Specification of requirements
    • Preliminary project plan
    • Definition of acceptance criteria
  • Secondary Objectives:
    • Finding people
    • Understanding the development environment
    • Forming tentative design ideas

darkDot.gif (501 bytes)Design Phase

  • Primary Objectives:
    • Baseline design of operational software
    • Baseline design of support software
  • Secondary Objectives:
    • Preparation for integration testing
    • Setting up change controls
    • Constructing simulation models
    • Planning manpower for subsequent phases
    • Preparation for programmer training
    • Publication of Programmer's Handbook (coding standards, naming conventions, etc.)
    • Initial preparation for systems test
    • Initial preparation for acceptance test
    • Initial preparation for site test
    • Setting up project libraries

darkDot.gif (501 bytes)Development Phase

  • Primary Objectives:
    • Detailed design
    • Coding
    • Module test
    • Integration test
    • Software documentation
  • Secondary Objectives:
    • Detailed preparation for system test
    • Detailed preparation for acceptance test
    • Detailed preparation for site test
    • Preparation for customer training

darkDot.gif (501 bytes)System Test Phase

  • Primary Objectives:
    • Testing against Specification of Requirements
    • Testing as "live" as possible
    • Testing not controlled by programmers
  • Secondary Objectives:
    • Completion of acceptance test preparations
    • Customer training
    • Correction of descriptive documentation
    • Completion of user documentation
    • Re-assignment of people

darkDot.gif (501 bytes)Acceptance Phase

  • Primary Objectives:
    • Execution and analysis of acceptance tests
    • Signing of formal acceptance agreement
    • Assistance in installing the system
    • Assistance in beginning operation
  • Secondary Objectives:
    • Completion of customer training
    • Cleanup of documentation
    • Testing on-site
    • Continuing maintenance and tuning
    • Continuing operation
    • Project evaluation

darkDot.gif (501 bytes)REFERENCE:

After P.W. Metzger: Managing a Programming Project, 2nd ed., Prentice-Hall Inc., 1981, ISBN 0-13-550772-3


cameo.gif (1740 bytes)Instructor: Vlad Wojcikmail.gif (1189 bytes)
Revised: 5 September, 2017 8:36 PM
Copyright 2017 Vlad Wojcik