ArgoUML

Project Management Plan

Modification history:

Project Name: ArgoUML

Team Members:

• Pete Lorins
  Email: petelorins@aol.com
  Individual web page: http://members.aol.com/petelorins/PetesPersonalPage.htm
• Dawid Trawczynski
  Email: dt39127@pegasus.cc.ucf.edu
  Individual web page: http://pegasus.cc.ucf.edu/~dt39127
• Chi-Hwa John Marcos
  Email: cjmmrcs@netscape.net
  Individual web page: http://pegasus.cc.ucf.edu/~cjm21809/ArgoUMLChi.html

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

ArgoUML is a modeling tool to help you do your design using UML. ArgoUML is an open source project, coded in Java. Diagrams are the main way of presenting object-oriented designs. Argo can also provide tabular presentations of the design and textual presentations in the form of source code, and (future) English language explanations. Your implementation will allow editing in any of these presentations, and all of them are kept consistent. This project is to extend ArgoUML will include the following features:

• undo/redo 
• copy/cut/paste 
• drag-and-drop

• Concept of Operations
• ArgoUML CVS Documentation
• Sun Microsystems for Java Developers

• Code Standard
• Document Standard
• Technical Progress Metrics

• Group Members

Dawid Trawczynski dt39127@pegasus.cc.ucf.edu

Peter Lorins             PeteLorins@aol.com

Leticia Izquierdo Leti_I@hotmail.com

John Marcos cjmmrcs@netscape.net

• Responsibilities:

Leticia Izquierdo – responsible for group web site, direct communication with the client and formal documentation

John Marcos – ArgoUML High Level and Low Level Code Design and Implementation, Documentation

Dawid Trawczynski – ArgoUML High Level and Low Level Code Design and Implementation, Documentation

Peter Lorins – ArgoUML High Level and Low Level Code Design and Implementation, Documentation

All communication among team members shall be accomplished through personal meetings (minimum one hour per week), email and telephone.  Leticia shall schedule meeting times although all group member shall make a final decision as to where and when meeting shall be held.

Communication with the course instructor shall be thru email unless required otherwise.  Communication with the client shall occur thru email and personal meetings when required.  Leticia shall schedule formal meeting times with the customer upon prior consultation the customer and all team members

Deliverables 

This project will use the Water Fall Model as the Software Life Cycle Process. The task is to add additional features to the release software ArgoUML. The requirements are clear and concise. Requirement, Specification and Design phase will be simple with little risk. Major effort will only lie in implementation and later phases.

All source code shall be compiled by using and SD Java Kit.  The source code shall be compiled for a LINUX operating system.  Visual Java, Java 2 SDK, Jbuilder,  and CodeWarrior may be used as software development environments for this project.  ArgoUML source code will also be needed so that original source code may be modified to include features required by the customer.  All code modification shall be accomplished thru source control software, namely CVS.

Version control shall be accomplished thru the use of CVS.  All team members shall accept the responsibility of utilizing CVS when modifying source code.  Standard check-in and check-out procedures shall apply when utilizing source code for development purposes.

• Quality Assurance (QA) activities will occur prior to the delivery of each project artifact.
• QA activities will include:

• Quality Assurance Manager: Pete Lorins

Potential risks for this project are:

1.      Project deadlines not met – unsuccessful design implementation

2.      Project deadlines not met – lack of team member effort and communication

Risk management steps:

1.      Ensure that top level and low level design are feasible by performing required design analysis and reviews

2.      Communicate team related issues with the instructor and team members