draft

Project Plan

XXXXXXXX

Submitted by Team X

XXXXX

Revision History

Name / Date / Reason For Changes / Version
Box Leangsuksun / 2/28/2004 / Draft / Beta 1.0
XXX YYY / 2/28/2004 / Correction / Beta 1.0.1

A. Introduction

The purpose of this plan is to provide information about the XXXX System project including deliverables, schedules, risks, dependencies, assumptions, estimates, project team, and change management.


B. Software Project Description

This Project is intended for the employees of the company, XXXX who are involved in the process of molecular simulation for drug design and discovery. The company has been facing some problems [1] with its current network management strategies. The aim of this project is to provide the best practices possible for its Network Management, which would enhance and expedite the process of drug design and discovery.


C. Team Members

Xxxx (roles)

Yyyy

zzzzz

D. Deliverables

As of now, there are no other project deliverables, except for the first version of the project.

E. Project Timeline

Responsibility Assignments:

1)  Problem Statement: Team Effort

2)  Project plan: Team Effort.

3)  Requirement Gathering and Documentation: xxxx will be the team leader in this phase and yyyy and zzzz will be assisting him.

4)  Analysis and Design: xxxx will be the team leader in this phase and yyyy and zzzz will be assisting her.

5)  Coding: xxxx will be the team leader in this phase, yyyy and zzzz will be assisting him.

6) Testing and Implementation: Team Effort.

E. Project Assumptions and Potential Risks

·  Assumptions:

·  The following assumptions are taken:

·  1. Users are highly qualified and have expertise in the area of molecular modeling and simulation.

·  Users are required to know and operate Windows GUI.

·  The current cluster has minimum three nodes and is running on the same operating system, Windows.

·  The developers are well versed with the programming language, C and C++ and Visual Programming.

F. Resources: To be decided.

Milestones and deliverables: The Gantt chart [2] is prepared describing the milestones and deliverables, which is attached to this document.

Note:

The Quality plan and testing schedule will be added later in this document.

References:

[1] Problem Statement submitted on September 28th.

[2]Gantt chart (sample taken from www.latech.edu/~box.)

9/29/2005 3