CyberGuide Project Plan

Winter Quarter 1996 1/16/96 Document Author: Jason Bennett Project Sponsors: Gregory Abowd

CyberGuide Team: Matt Howser (Architect/Programmer) Derek Adams (Programmer/Architect) Jason Bennett (Technical Writer)

Project Description

In this incarnation of CyberGuide, we are striving to not only recreate CyberGuide on another platform, but upgrade and improve it at the same time. Originally written for the Apple Newton, this incarnation of CyberGuide will be a port to the Delphi language and will be designed to run on a palmtop Intel platform under Microsoft Windows. This port will not be a direct one in the sense that this group will not have the advantage of a knowledge of the original code, only the interface and purpose. It will, therefore, be a recreation of the system, with changes to make the interface more appropriate for the new platform. The team will not, however, settle for a simple recreation. It is our purpose to enhance the program as well, with features such as determining facing, a rotating map, color-coding the display, and displaying the most appropriate route to a selected destination.

The current incarnation of CyberGuide features a map of a room, currently the GVU lab, with the locations of the demonstrations marked. The user can scroll the map, and when he moves the map will track where he currently is. The guide uses crude infrared sensors mounted on the ceiling to keep track of location, using a sensor interfaced through the Newton's serial port. It can determine the direction the user is moving, although not the precise direction he is facing. There are zoom in and zoom out features to give a close or wide view of the room, allowing the user to see as many locations as he wants, or narrow his view down to the closest few. "Clicking" on a location, using a pen on the Newton, brings up a description of what is being demonstrated at the location in a small window.

At this time, CyberGuide is an effective if crude tour guide. The basics of the interface are certainly present, with many good ideas represented. There are, however, areas that are improvable. Although there is not sufficient time to explore all of CyberGuide's possibilities, our goal is to markedly improve upon the existing product. Some facets of the guide which need improvement are hardware-based and outside of the scope of this portion of the overall project. However, there are many areas in which the software can also be improved. With the improved speed and graphics the Intel platform offers, some enhancements will come automatically through hardware, some are implementable on either plaform, and some will take advantage of the specific platform. The orignial abstract for the project envisions an interface that is both intuitive and personal. This quarter, we hope to make great strides in this direction.

Much of the information in this overview has been taken from past project notebooks and abstracts. I have linked some of the primary sources through their home pages at the beginning of this plan. The writer is grateful to the project pioneers for their vision and clarity.

Project Schedule

The ° character designates various deliverables.

Activities description

Requirements (12 hours)

Acquiring and sorting all of the requirement documents, along with detailing deadlines and determining what features need to be added or changed in the CyberGuide system. This will include all team members working together to determine what needs to be accomplished over the course of the project.

Roles:

Architect/Programmers (4 hours each), Technical Writer (4 hours)

Planning (36 hours)

Initially, there will be a great deal of time devoted to planning, mostly involving organizing the group and determining the project and its objectives. We will continue to have regular planning sessions throughout the life of the project (weekly, at least) in order to keep the project on track and on time. This will usually involve all team members.

Roles:

Architect/Programmers (12 hours each), Technical Writer (12 hours)

Training (18 hours)

The type of training done will vary by team member. The programmers/architects will primarily focus on reviewing and perfecting their knowledge of Delphi, while the writer will focus on learning CGI scripts and image maps. At the end of the training period, there will be a full team meeting to share some basics on Delphi and scripting.

Roles:

Architects/Programmers (5 hours each), Technical Writer (5 hours)

Design/Definition (8 hours)

The Programmer/Architects will meet and plan the layout of the project during this time. Because of a lack of Newton knowledge, they will start from scratch without utilizing the existing Newton code. Once the architecture definition is complete, there will be a briefing of the writer, likely in conjunction with other business.

Roles:

Architects/Programmers (4 hours each)

Writing (16 hours)

The Technical Writer will use this time to compose all of the required documents for this course. This will include all HTML documents, the project notebook, CGI scripts for the pages, and any other documentation required for the project.

Roles:

Techincal Writer (16 hours)

Revising Documentation (8 hours)

This time will be devoted to the writer's revision of documents which have been previously composed in order to bring them up to specifications. This will include, but not be limited to, this project plan and the project notebook.

Roles:

Technical Writer (8 hours)

Programming (48 hours)

The Programmers/Architects will utilize this time to actually code the application in Delphi. The time will fluctuate appropriately, peaking when the most coding is occurring and declining as the testing phase sets in. The writer might assist in this phase, but it is assumed that his writing duties will keep him firmly occupied during this time period.

Roles:

Architect/Programmers (24 hours each)

Testing/Debugging (42 hours)

Once the coding has moved into an advanced stage, time will be set aside specifically for the purpose of debugging and testing the application's code. The time will peak as the coding finishes, then hopefully will decline as the bugs are snuffed out one by one. The programmers will be primarily responsible for this, although again the writer will assist if needed.

Roles:

Architect/Programmers (21 hours each)

User Testing (21 hours)

As the application nears its alpha and then beta stages, user testing will commence. This will consist of the team members and others outside the team field-testing the application on its intended platfor in an appropriate location. This will enhance the debugging of the program and possibly yield new ideas which might be implemented quickly at the late date. All members of the team will be imvolved in this fascet of the project.

Roles:

Architect/Programmers (7 hours each), Technical Writer (7 hours)