Informal Science Education II

Project Management Plan

EEL 5881 - Software Engineering, Fall 2000

Modification history:

VersionDateWhoComment
Version 0.0 August 15, 2000 G. H. Walton Template
Version 1.0Michael WalesOctober 11, 2000 Initial version

Team Name: Miles Computer Engineering

Team Members:


Contents of this Document

Project 0verview

Reference Documents

Applicable Standards

Project Team Organization

Deliverables

Software Life Cycle Process

Tools and Computing Environment

Configuration Management

Quality Assurance

Risk Management

Table of Work Packages, Time Estimates, and Assignments

PERT Chart

Technical Progress Metrics

Plan for tracking, control, and reporting of progress


Project 0verview

Our project is to create a Cellular Automata simulation tool. The tool will be most likely used by computer scientists and biologists to create parameters that will simulate different life. Our Cellular Automata tool will give these researchers the ability to quickly change simulation parameters, and the flexibility to create very complex simulation conditions.


Reference Documents


Applicable Standards


Project Team Organization

Our group orgranization is pretty informal and pretty open. Since Jeff and Mike already knew each other before the class (and share all their classes this semester), this should not cause any problems. Michael is more of a leader and is always trying to create the greatest program the world has ever seen. Jeff is more relaxed and practical, which helps to keep the project more manageable.

Tasks will be divided between Mike and Jeff as they see fit during the process of the semester. We will avoid working on the same tasks at the same time to avoid redundancy. And the website will be kept up to date all the time on Pegasus with the latest version of each document created. This will avoid us having to coordinate with each other to bring the website together. We can communicate with each other daily, and intend to try to communicate with our customer every few weeks to keep him up to date on our progress.


Deliverables

ArtifactDue date(s)
Meeting Minutes2 meetings to date
Individual LogsThese are updated each week and can be viewed any time by accessing our webpage on Pegasus.
Group Project Management ReportsT.B.A.
Concept of OperationsOctober 16, 2000
Project Management PlanOctober 16, 2000
Software Requirement SpecificationsOctober 23, 2000
High-Level DesignT.B.A.
Detailed DesignT.B.A.
Test PlanT.B.A.
User's ManualT.B.A.
Final Test ResultsT.B.A.
Source, Executable, and Build InstructionsT.B.A.
Project LegacyT.B.A.

Software Life Cycle Process

We are planning on beginning with prototyping our software, then the next step we intend to accomplish is to draw the UML diagrams for our system. This should help us find any features left out of the prototype that need to be included in the final product.


Tools and Computing Environment

We intend on using Java 2's JDK V1.3 to build our project. This will enable the product to run a variety of platforms, such as Windows 95 or later, Mac, Unix, or Solaris. The libraries that we will be using are the standard libraries that Java is distributed with.


Configuration Management

The version control of will be handled by each team member. Jeff and Mike are both responsible for updating the version number and recording any changes to a document when they are made. These changes will be recorded in table at the begining of each document.


Quality Assurance

Each team member will be responsible for quality assurance. The person responsible for drawing up a document will not be solely be responsible for checking the document for errors. Jeff and Mike will perform a walkthrough at the completion of each document, and inspections will be performed at key points in the development process. The results will be reported by each reviewer in a list, each list will contain items that the reviewer does not understand and items that the reviewer believes are incorrect.


Risk Management


Table of Work Packages, Time Estimates, and Assignments

Work packageEstimated Time Responsiblity
Documentation30 hoursJeff and Mike
Webpages10 hoursJeff and Mike
Coding40 hoursJeff and Mike


PERT Chart

Pert Chart
Pert Chart for Project Management Plan Version 1.0

Our critical path is: (5 weeks) Main simulation window -> Procedures for inital state editing -> Help utility for entire simulation


Technical Progress Metrics