The Cyberguide Project was started in March 1995 by the Future Computing Environments (FCE) group and is headed by Gregory Abowd. The Cyberguide "vision" is to develop an intelligent handheld tour guide that has information about surrounding areas and your location. This vision was partially realized in the Summer of 1995, as a non "position-aware" version of the Cyberguide was developed on the Newton for the GVU Demo Days.

This project continues the developmental work done by those Cyberguide pioneers. The aim of this venture is to build a version of Cyberguide that is portable to a Windows platform.

Project Features

• An aerial display of the room.
• Icons signifying the location of points of interest in the room.
• A link to a description of each location's topics.
• A tracking device for the current location of the guide.
• An easily maintable list of 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-

Project Milestones

DELIVERABLE	GOAL DATE	ACTUAL DATE
Project Plan	1/19/96	1/25/96
Requirements Document	1/26/96	mmddyy

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 information exchange.

Design (38 hours)

This will involve designing the project, including requirements, specifications, and usability. Analyzing the project objectives, planning how the system will be built, and designing the underlying system structure, are fundamental aspect of the overall design. Design will chiefly be done by the architect, with help from the programmer.

Training (41 hours)

As all programming will be done in Visual Basic, the group will allow sufficient time for learning the software's particulars. Most of this time will be spent by the programmer studying various sources of information. He will then relay information as necessary to the rest of the group.

Coding (46 hours)

This is the actual writing of the program. The programmer will produce that code which requires a thorough knowledge of Visual Basic. Simpler coding tasks will be given to other members of the group.

Debugging (19 hours)

This time will be spent running test data to find and correct errors in the program. Examples of potential bugs include: an icon doesn't link to the correct description, icons are not properly situated on the screen, and the tracker doesn't locate the guide. All members will likely be involved in debugging.

Testing (7 hours)

Once the program is debugged, its usability will need to be tested. This involves running the program on the target machine, rather than the test machine. Also, persons outside the group will be asked to demo the program.

Writing (76 hours)

This time will be devoted to producing the text requirements for the project, namely, the project plan, the requirements document, and the design document. The technical writer, assisted by other members when practical, will complete these reports.