CS 3911 - Design Project

Spring Semester 2003

DELIVERABLES

·        Status Reports

·        Requirements Document

·        Project Plan

·        Mid Term Presentation

·        Design Document

·        Peer Evaluation

·        Final Presentation

·        Customer Delivery

Status Reports
Weekly status reports should include the following information:

1. Project Team
2. Planned Hours:________ Actual Hours:__________
3. Objectives for the Week
•  
•  
•  
4. Accomplishments
•  
•  
•  
5. Objectives/Plans for Next Week
•  
•  
•  
6. Problems/Issues

Requirements Document

Project Plan

Midterm Presentation
These presentations are meant to provide a progress report and to make sure that the team, their advisor, and the course coordinator have a clear view of the current status and plans for the project.   Remember this is a status presentation, not a "What I did on my summer project" presentation.  Each presentation should include at least the following components:

1. A concise statement of the goal or vision for the project
2. A brief description of the requirements derived from the goal.
3. A overview of the design solution.
4. Planned vs. Actual Project Data
5. A discussion of any problems or risks the team is facing.

You have a 15 minute window to give a solid, concise, complete status update.  You are also graded on how well you handle questions, so both be ready for them and leave time to answer them.

Design Document

USE THIS FORMAT FOR THE EVAL!
Each team member will complete a set of self and peer evaluations for each team member.  You will be asked to evaluate the effort and performance of the individuals in your group to both the instructor and your faculty advisor.  This feedback will be a significant factor in determining an individual's grade.

Each presentation should include at least the following components:

1. A concise statement of the goal or vision for the project
2. A reminder of key requirements and design elements
3. A description of what you accomplished during the semester and a demonstration
4. A discussion of how well the results matched your initial plan, including the reasons for any significant deviations from the plan.
5. A reflection about what you learned from this experience.

This presentation should be around 30-35 minutes.

Since everyone on each team is supposed to do a part of one of the two presentations, be sure that any team members who didn't present at mid-term present now..

Delivering the Project to your Customer
The final requirement for the semester includes scheduling a meeting of the whole project team with the customer.  Attendance by the faculty advisor at this meeting is strongly encouraged, but not required. The agenda for this meeting should include:

1. A brief presentation of what you have accomplished relative to the requirements, probably taken from your final presentation to the class.  This presentation need not be a formal, stand-up one unless your customer is actually a group.
2. A demonstration of the operation of your software to the customer.
3. An opportunity for the customer to try out the software.
4. Discussion with the customer of the strengths, weaknesses and opportunities for extension of the software.
5. Hand over of the source code and documentation of the software.  The documentation should include:
• technical overview & installation guide
• system test plan showing outstanding defects.
• a user manual that describes the features of your system.
• commented source code with good style
• delivery package (setup scripts, file organization, etc.)
• a project history should be delivered to your advisor covering your experiences and lessons on the project.

I will send the customer a request for feedback on your efforts as a whole and on the quality/professionalism of this delivery meeting.

GeorgiaTech Disclaimer
This page is maintained by: watersr@cc.gatech.edu
Last Modified on Monday, May 13, 2003.