Project Management Plan

EEL4884, Spring Semester, 2004

Modification history:

Team Name:  Team Goalie

Team Members:

• Luis Gonzalez, Email, Homepage
• David Mui, Email, Homepage

Project Overview

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

• Concept of Operations - Brief description of the proposed system.
• www.robocup.org - Official Robocup Website
• Robocup Manual - Robocup Soccer Server Manual

• Coding Standard: Our code will be well documented at the head of the file and throughout each file. Each version of the code will have it's date with it and version number. Code will have generous white space and all code blocks will be indented to provide for easier code reading. We will adopt a naming convention similar to the naming convention of the Java programming language. All classes will start with capital letters, while functions will start with lower case letters. All classes will be in seperate files, and have documentation on the other classes (and the other class' version number) that they are compatible with.
• Document Standard: All our non-code documents will be in the HTML format. The font size will be the default font size, with headings in boldface, and major headings in enlarged fonts. We will use Microsoft Word to perform grammer and spell checking on our documents before their final submission. The user manual will definitely be checked because it is a deliverable to the customer. All sizeable documents will have a table of contents and a modification history.
• Artifact Size Metric Standard: Our metric for measuring the size of our code and progress will be to measure the size of the source code files in bytes. This metric will lessen the effects of whitespace (where as "lines of code would" increase) on our progress. This metric will not convey the complexity of the code, but it is quick, easy, and will fit our purposes.

Project Team Organization

My name is David Mui and my group member, Luis Gonzalez, is in this group that will designing the Goalie subsystem for this soccer simulationFor now I will be assuming the role of project manager however the workload will be divided between us both.  The group website is currently being maintained by me, however in the future Luis, will also be updating the web page accordingly as the software development progresses. 

Luis and I has exchanged cell phone numbers and email and we will be in contact with each other to work on the Goalie subsystem. We also have been communicating online via an online instant messaging program, so it will not be difficult for us to contact one another to schedule a meeting.

Deliverables

Software Life Cycle Process

Our group will attemp to utilize the iterative approach in developing the Goalie subsytem for the Robocup Soccer simulation.  As of this revision of the Project Management Plan we have yet to identify the processes that include the major phases, however this document will be updated accordingly as the project progresses.

Tools and Computing Environment

The operating system that our project be will developed on is a Debian/GNU Linux distribution.  The source code will be written in C++ programming language and compiled under the g++ compiler provided by Linux.

As of this revision we have yet to determine the libraries required for the Goalie subsystem, however this document will updated accordingly as the project progresses.

Configuration Management

Quality Assurance

Luis and I will both be responsible for quality assurance activites for this project.  The project will be well documented and extensively tested in lab meeting times.  If any defects or errors is evident it will be our own responsibility to report them to each other.

Risk Management

For this project our group should be able to minimize the risks involved with the project.  We just need to document the code as thoroughly as possible and brainstorm with the client to develop the system to specifications.

Some risks involved could be a failure to document the code efficiently, failure to meet specifications, and failure to meet functionality requriements. Further updates to this document will added as the project progresses.

PER Chart will be created once the design process of the project has begun.

Plan for tracking, control, and reporting of progress

At a minimum, each team member will post the following information weekly: individual time and activity log, individual status information, individual issues and problems, and individual defect log.

Each week, the project manager will: read and analyze the logs; examine the technical content of the work done to date; examine the technical progress metrics; consider the QA results; reassess the potential project risks; and take corrective action if necessary.

The project manager will issue a Project Management Report on the schedule as indicated in the deliverables section above. At a minimum, the Project Management Report will be generated every two weeks and will include the following information: 1 sentence description of overall status, 1 or 2 sentence of any planned changes to the project plan, graph of planned vs actual time, graph of planned vs actual for each technical progress metric, updated PERT chart."