CSE 4316 Spring 2001

Project Plan and Presentation

Project Plan Due: February 23, 2001, midnight

The Project Plan should completely and specifically describe your project. The specific components of the Project Plan are outlined below. The Project Plan is a professional quality document and should be emailed to me (holder@cse.uta.edu) and published on your team's web site by the above deadline.

The Project Plan Presentation is a professional quality multimedia slide-based (preferably Microsoft PowerPoint) presentation of all aspects of the Project Plan. All team members are expected to participate in the presentation and have a professional appearance (e.g., no jeans, no tennis shoes, no T-shirts). Each team will be given a 50-minute class period for their presentation (45 minutes) and questions and feedback from the audience (5 minutes). Presentations will be given on the following dates during class.

Please email me (holder@cse.uta.edu) your team's preferences for dates. Reservations will be prioritized in the order I receive them.

Project Plan


The Introduction should include your team/project name and your team members' names, titles, contacts (email), and relevant experience. The Introduction should also give a brief overview of the project, including the problem statement, proposed solution, benefits to the customer, and a summary of the major resource needs, project budget and project duration. You should also develop a graphical illustration of the major components of your project that shows their functional relationship to each other.

Project Definition

The Project Definition is a detailed description of the project's deliverables, milestones and tasks. The deliverables are specific descriptions of the what your project will produce to solve the problem, including hardware, software and documentation. The project should be broken down into milestones with dates. These milestones should not just include the prototype and final project completion, but also checkpoints along the way (e.g., sensor X circuitry completed and tested, all sensors interfaced with GUI, etc.).

The project tasks should be presented similar to the work breakdown structure (WBS) in the textbook. Tasks should be oriented around the milestones, and specific descriptions should be given for all tasks. Project reports and presentations should also be included in your project tasks.


The project plan should include a complete list of the resources necessary for the completion of the project. The list should include both resources already available and resources yet to be acquired. Typical resources include personnel, computing hardware and software, facilities (e.g., space, storage), and materials (e.g., sensors, controllers, electronics). Each resource not yet acquired should be described in terms of functionality needed, when needed, alternatives available and their tradeoffs, and costs of each.

Individual Task Plans

Each task described in the Project Definition should have an associated Individual Task Plan (ITP). The ITP is a detailed description of the task, the team member(s) assigned to the task, the estimated task duration, the deliverables of the task, and the dependencies of the task on other tasks. You should include here the network diagram (PERT chart) for your project.


The Schedule should show each task along a time line indicating when each task will be completed. You should include here the Gantt chart for your project. Also, discuss any slack or uncertainty you may have about the schedule, and what might be modified if the project gets behind schedule.

Quality Control

The Quality Control section of the Project Plan describes the testing and integration tasks of the project and how the results of this testing will be documented and used during the project.

Project Control

The Project Control section describes how you will monitor and control the execution of the project. Project Control will include meeting schedules, meeting documentation, project performance measurement, comparison to baseline plan, and incorporation of change. In other words, how will you implement the project control process depicted in Figure 4.2 of the textbook.

Documentation and Dissemination

This section describes what documentation will be produced to describe the project deliverables and the project execution (e.g., project plan, meetings minutes, progress reports, prototype report, user's guide, etc.). This section should also describe how this information will be disseminated via your web site.