Team 7 CyberGuide Project Plan

Project Features

• Bitmap display of Lab
• Clickable icons on display for points of interest
• Icons link to HTML documents that describe projects
• Tracks current location of guide via IR signals
• Easily maintainable list of current project locations

Project Schedule

ACTIVITIES
Meeting	8	16	12	12	12	12	12	4
Design	0	10	14	14	0	0	0	0
Training	10	14	9	8	0	0	0	0
Coding	0	0	0	0	25	21	0	0
Debugging	0	0	0	0	9	10	0	0
Testing	0	0	0	0	2	5	0	0
Writing	1	8	13	14	0	0	36	4
TIME	-1/15-	-1/22-	-1/29-	-2/5-	-2/12-	-2/19-	-2/26-	-3/4-

Activities description

Meeting (88 hours)

Weekly meetings will be during classtime each Wednesday and Friday. This time will be spent designating responsibilities for the upcoming week. Also, members will update the group of their status and problems they have encountered. Individual members will also meet outside of class for additional updates.

Design (38 hours)

This will involve designing the project, including specifications and usability. Planning how the system will be built, including analysis and design of the underlying system structure is a fundamental aspect of the overall design. Design will chiefly be done by the architect, with help from the programmer.

Training (41 hours)

This involves learning Visual Basic. Most of this time will be spent by the programmer studying various sources of information. The programmer will then spend time showing other members of the group the basics of Visual Basic.

Coding (46 hours)

This is the actual writing of the program. Most of this work will be done by the programmer but all members will do some coding.

Debugging (19 hours)

This time will be spent running test data to find and correct errors in the program.

Testing (7 hours)

Making sure that the program is usable by other people.

Writing (76 hours)

Documentation of the project plan, requirements, and schedule will be done during this time. Most writing will be done by the technical writer.