Cyberguide Project Plan

Winter Quarter 1996 1/19/96 Project Sponsors: Gregory Abowd Chris Atkeson

Cyberguide Team: Robert Duncan Sue Long Prabath Valiveti Michael Minori Eugene Liu Chris Goodrum Daniel Bassett Danny Lentz Derek Abiusi Stephen Eley

3.2 Team Description
3.3 Team Goals
3.4 Team Activities
3.5 Team Schedule
3.6 Project Risks

4.1 Project Task
4.2 Team Description
4.3 Team Goals
4.4 Team Activities
4.5 Team Schedule
4.6 Project Risks

5.1 Project Task
5.2 Team Description
5.3 Team Goals
5.4 Team Activities & Schedule
5.5 Project Risks

6.1 Project Task
6.2 Team Description
6.3 Team Goals
6.4 Team Activities
6.5 Team Schedule
6.6 Project Risks

7.1 Project Task
7.2 Team description
7.3 Team Goals
7.4 Team Activities
7.5 Team Schedule
7.6 Project Risks

8.1 Project Leader - Robert Duncan
8.2 Domain Expert
8.3 Equipment Manager - Eugene Liu
8.4 Web Manager - Chris Goodrum
8.5 Meeting Manager - Daniel Bassett
8.6 Documentation Manager - Prabhath Valiveti
8.7 Software Manager - Micheal Minori
8.8 Presentation Manager - Stephen Eley

1.0 Introduction

2.0 Related Documents

http://www.cc.gatech.edu/fce/cyberguide/project_notebook/index.html

3.0 Outdoor Cyberguide Team

3.1 Project Task:

3.2 Team Description:

As team leader/member of the Outdoor Cyberguide team, he is responsible for:

• infinity Set the schedule for the team
• infinity Act as liason between the team and the Project Leader
• infinity Responsible for the team's overall results
• infinity Guide the direction of the team in conjunction with the Project Leader
• infinity Self-training in Cyberguide, NewtonScript and the Newton Toolkit (NTK)
• infinity Co-software/architecture engineer for team
• infinity Responsible for documentation of design and code
• infinity Documentation Manager for team documents

Derek Abiusi
gtd263a@prism.gatech.edu
892-6818 x.121

As team member of the Outdoor Cyberguide team, he is responsible for:

• infinity Setup of the revision control system for code developed by the team
• infinity Self-training in Cyberguide, NewtonScript and the Newton Toolkit (NTK)
• infinity Co-software/architecture engineer for team
• infinity Responsible for documentation of design and code
• infinity Responsible for procurement of new equipment/hardware
• infinity Equipment Manager for team equipment

3.3 Team Goals:

3.3.1 Analysis

3.3.2 Feasibility

3.3.3 Outdoor Cyberguide

3.4 Team Activities:

3.4.1 Analysis

1. 1. Attend the NewtonScript tutorial session.
2. 2. Become familiar with NewtonScript and the Newton Toolkit (NTK).
3. 3. Study and examine the existing Cyberguide code.
4. 4. Understand interactions between the existing positioning system and the map.
5. 5. Learn the map structure used and the formats for information used by the information browser of Cyberguide.
6. 6. Learn how the Newton handles program files, serial input, and SOUPS.

3.4.2 Feasibility

Phase One:

1. 1. Become familiar with the GPS equipment and the specs. of the output format over a serial connection.
2. 2. Determine how the GPS information will be translated into what Cyberguide presently expects via the serial port connection with the Motorola IR circuitry.
3. 3. Determine map size constraints (estimate available memory).
4. 4. Meet with the map builder tool team to discuss future map format.
5. 5. Develop approach for development of phase one.

Phase Two:

1. 6. Examine scrolling limitations and map detail constraints given processor speed and capability.
2. 7. Investigate use of existing technology developed for other products.
3. 8. Establish scheme for translating GPS coordinates directly to non-discrete positions on map.
4. 9. Develop approach for development of phase two.

3.4.3 Outdoor Cyberguide

Phase One:

1. 1. Replace the Motorola IR circuitry with the GPS device and integrate into the existing Cyberguide system using discrete positional updates at fixed locations.

• infinity Develop design of object classes, methods and interactions with existing Cyber guide objects classes.
• infinity Develop the objects in NewtonScript and integrate with the existing code.
• infinity Test, redesign, and rebuild as needed.

Phase Two:

1. 2. Improve the positional update on the map with the intention to produce a non-discrete position, scrolling map.

• infinity Develop design of object classes, methods and interactions with existing Cyber guide objects classes.
• infinity Develop the objects in NewtonScript and integrate with the existing code.
• infinity Test, redesign, and rebuild as needed.

3.5 Team Schedule:

3.5.1 Analysis

• infinity Activity 1. January 17
• infinity Activity 2. January 17 - Ongoing
• infinity Activity 3. January 20 - January 21
• infinity Activity 4. January 20 - Ongoing
• infinity Activity 5. January 21 - January 23
• infinity Activity 6. January 21 - January 23

3.5.2 Feasibility

• infinity Activity 1. January 19
• infinity Activity 2. January 23 - January 25
• infinity Activity 3. January 23 - January 25
• infinity Activity 4. January 25
• infinity Activity 5. January 25
• infinity Activity 6. February 2 - February 4
• infinity Activity 7. February 2 - Ongoing
• infinity Activity 8. February 4 - February 6
• infinity Activity 9. February 8

3.5.3 Outdoor Cyberguide

• infinity Activity 1. January 17 - February 8
• infinity Activity 2. February 1 - February 22

3.6 Project Risks:

3.6.1 The Newton can't read the GPS signal.

Develop hardware to convert the GPS signal into data that the Newton can understand.

DAMAGE:

The loss of time needed to create the new hardware. The money that will be needed. Also, the Newton will have extra equipment added onto it that will make it harder to han dle. We will also have to rely on others to teach us how to make such a device.

3.6.2 The GPS does not give discrete and constant changes in position.

Need to develop an algorithm that will round off to the nearest position that the Newton knows about.

DAMAGE:

Extra time will be needed to develop and implement such an algorithm. The time neces sary to compute the position will increase, possible reducing performance.

3.6.3 The scale of the map is not large enough to accommodate the GPS positioning scheme.

Use a larger scale / less detailed map.

DAMAGE:

The position of the user will not be as precise. The user will have to travel longer dis tances to see a change on the map.

3.6.4 The GPS does not work correctly.

Get another GPS that works correctly.

DAMAGE:

Time and money will be spent replacing the GPS.

3.6.5 A large and detailed map will require too much memory if added software is needed to interpret the GPS into a language that Newton can understand.

Add memory to the Newton.

DAMAGE:

Time and money will have to be spent.

3.6.6 A large and detailed map coupled with the addition GPS interpreting software could slow the processing time of the application. If the processing time becomes too long, delays in the users position could render the Newton useless.

Optimize the code so the processor is not working as much. Use a less detailed map that will take lees time to draw. Move the software that interprets the GPS signal into a lan guage that Newton understands into an external hardware device.

DAMAGE:

Time will be spent trying to optimize the code. Time could also be wasted building a hardware device that interprets the GPS signal.

3.6.7 We will not be able to purchase necessary devices, i.e. cables, and they will need to be custom built.

Build the cables ourselves.

DAMAGE:

Time wasted building cables. Relying on others to teach us how to construct the cables.

4.0 Map Services Team

4.1 Project Task:

4.2 Team Description:

Currently the only member of the Map Services Team. He is responsible for:

• infinity Self-training in Cyberguide, Newton, and NTK
• infinity Analysis of current Cyberguide program units
• infinity Design of the new Map Services utilities
• infinity Implementation of Map Services utilities in NewtonScript
• infinity Interfacing with other project teams to ensure compatible development
• infinity Documenting and reporting on Map Services Team status.

4.3 Team Goals:

4.3.1 Analysis

4.3.2 Path Generation

4.3.3 Map History

4.4 Team Activities:

4.4.1 Analysis

1. 1. Become familiar with Newton operation and NTK.
2. 2. Examine current Cyberguide code in the Open Systems Lab.
3. 3. Evaluate said code, keeping notes on basic implementation for utility integration (and possible later redesign).
4. 4. Meet with Map Building team to discuss possible path-building hooks in the provided map.
5. 5. Meet with Information Browser team to evaluate future integration difficulties, if any.
6. 6. Deliver final report on Map Services team status at end of quarter.

4.4.2 Path Generation

1. 1. Develop a Breadth First Search algorithm for optimal path generation given rele vant data points.
2. 2. Design necessary object classes and relationships in NewtonScript.
3. 3. Call for modification of Cyberguide or Map Building tool (if necessary) to provide necessary data relationships.
4. 4. Implement utility design in NewtonScript.
5. 5. Test, debug, and redesign as necessary.

4.4.3 Map History

1. 1. Design necessary object classes and relationships in NewtonScript.
2. 2. Implement utility design in NewtonScript.
3. 3. Test, debug, and redesign as necessary.

4.5 Team Schedule:

4.5.1 Analysis

• infinity Activity 1. January 19
• infinity Activity 2. January 22 - January 26
• infinity Activity 3. January 22 - January 26
• infinity Activity 4. February 5 - February 9
• infinity Activity 5. February 5 - February 9
• infinity Activity 6. March 4 - March 8

4.5.2 Path Generation

• infinity Activity 1. January 25 - January 31
• infinity Activity 2. January 29 - February 8
• infinity Activity 3. February 5 - February 9 (if necessary)
• infinity Activity 4. February 12 - February 26
• infinity Activity 5. February 26 - March 4

4.5.3 Map History

• infinity Activity 1. January 26 - February 4
• infinity Activity 2. February 7 - February 15
• infinity Activity 3. February 15 - February 20

4.6 Project Risks:

4.6.1 Lack of Data Hooks

SOLUTION:

Redesign the map data structure, or provide additional path information concurrent to the map.

DAMAGES:

The Map Builder tool may have to be reworked or modified. Cyberguide code may have to be modified for Map History information.

4.6.2 Lack of Processing Ability

SOLUTION:

Find a different algorithm to generate the path. (Depth-first search?)

DAMAGES:

Design time lost; possible failure to generate optimal path.

4.6.3 Design Changes

SOLUTION:

Modular code; stay informed of any new developments; make code requiring fewer data hooks.

DAMAGES:

Possible time lost; utilities may lose some functionality if data hooks are revised or removed.

4.6.4 Unmanageable Code

SOLUTION:

Redesign and reintegrate vital portions of Cyberguide.

DAMAGES:

Redesign is a MAJOR undertaking, and out of the scope of this project team. The Team Project Plan may have to be rewritten.

5.0 Data Tool Team

5.1 Project Task:

We would like to build a tool that streamlines this process, and hides details of the pro grams operation from the user preparing the demo.

5.2 Team Description:

As team leader/member of the Data Tool team, he is responsible for:

• infinity Set the schedule for the team
• infinity Act as liason between the team and the Project Leader
• infinity Responsible for the team's overall results
• infinity Guide the direction of the team in conjunction with the Project Leader
• infinity Self-training in Cyberguide, NewtonScript and the Newton Toolkit (NTK)
• infinity Co-software/architecture engineer for team
• infinity Responsible for documentation of design and code

As team member of the Data Tool team, he is responsible for:

• infinity Setup of the revision control system for code developed by the team
• infinity Self-training in Cyberguide, NewtonScript and the Newton Toolkit (NTK)
• infinity Co-software/architecture engineer for team
• infinity Responsible for documentation of design and code

5.3 Team Goals:

1. 1. Analyze the information needs of the Cyberguide.
2. 2. Develop a data format for the Cyberguide. (to be done in conjunction with the Info browser group)
3. 3. Determine whether any currently existing tools can be used with little or no modifica tions.
4. 4. Design and implement a set of tools for creating and managing Cyberguide tours.

5.4 Team Activities & Schedule:

5.4.1 January 17 -- January 26

• infinity Meet with the Infobrowser group to discuss data format needs.
• infinity Research existing utilities and tools. Specifically, determine whether current tools for creating HTML ISMAP files will be acceptable.

5.4.2 January 27 -- February 2

• infinity Research methods of transferring data to the Newton from a workstation.

5.4.3 February 3 -- February 9

• infinity Complete design of data format and survey of available tools.
• infinity Determine what workstation platform to build the tool for.
• infinity Begin implementation of tool on selected platform.

5.4.4 February 10 -- February 22

• infinity Complete implementation of tool.

5.4.5 February 22 -- March 9

• infinity Perform usability study on tool.

5.5 Project Risks:

5.5.1 Dependence on Infobrowser being correctly and completely implemented.

Modify the design of the tool to produce data that can be used by the current design.

5.5.2 Existing tools cannot be used.

Create a tool to manipulate the bitmaps and for selecting hot spots.

5.5.3 Transferring data to the Newton proves to be me challenging than expected.

Shift schedule to accommodate additional research and development of a solution.

5.5.4 Selected platform proves to be inadequate or unacceptable.

Shift to another workstation platform.

6.0 Network Team

6.1 Project Task:

The wired network system includes connecting a Cyberguide unit to a UNIX box to estab lish a communication link. The person holding the Cyberguide will be able to send e-mail and retrieve information via the link. By allowing direct and immediate communication, this will be a convenient extension to the existing Cyberguide system.

The wireless infrared network will handle communication between a central server and various Cyberguide units. The network will allow useful features such as message broad casting and peer location. Since Cyberguide already has built-in infrared communication capability, developing the network based on infrared is a feasible attempt. Due to time and technical resource restraints, we will build a network simulator by the end of the quar ter.

6.2 Team Description:

Kevin Cloudt - Software Engineer
gt5258b@prism.gatech.edu
(404)206-4411

Robert "Bear" Marples - Team Architect
gt3642b@prism.gatech.edu
(404)874-8847

Rich Bails - Schedule Manager/Software Engineer
richb@cc.gatech.edu

Trevor Toth - Technical Writer
gt1844a@prism.gatech.edu

Michael Minori - Software Engineer
twelve@cc.gatech.edu
(404)206-4223

Michael Minori will work closely with Sue Long (suelong@cc.gatech.edu) in porting an existing protocol software (LlamaTalk) to UNIX.

6.3 Team Goals:

1. 1. Learn Newton programming
2. 2. Learn and experiment with the Newton hardware
3. 3. Produce various documents and keep them most up-to-date (e.g. team project plan, requirements plan, user's manual, etc.)
4. 4. Porting the LlamaTalk protocol to UNIX
5. 5. Develop a working simulation of the wireless network

6.4 Team Activities:

1. 1. Attend Newton tutorial sessions and access related material (e.g. experienced people, books, newsgroups, etc.)
2. 2. Find official specifications for the Newton hardware; run experiments in determining information such as IR range, speed, etc.
3. 3. Coordinate the Technical Writer in producing and updating various documents, espe cially on the World Wide Web.
4. 4. Translating Pascal code into UNIX C; understand how LlamaTalk operates
5. 5. Programming the Newton in order to run simulations; programming the server platform (possibly UNIX) to run simulations; build the necessary hardware (if any) to run simu lations

6.5 Team Schedule:

6.5.1 Week ending 1/20/96

• infinity Produce the team project plan.
• infinity Systematic understanding of the existing Cyberguide.
• infinity Acquire some hands-on experience with Newton programming

6.5.2 Week ending 1/27/96

• infinity Meet with Prof. Chris Atkeson to discuss further administrative and technical detail.
• infinity Complete Newton programming training.
• infinity Experiment with different infrared communication hardware (the existing Newton IR and the Sharp IR).

6.6 Project Risks:

6.6.1 Leaving of one or more team members.

Redistribute responsibilities and tasks.

DAMAGE:

Each team member will be responsible for more things and acquire a heavier workload.

6.6.2 Unable to acquire necessary hardware for the project.

Seek an alternative hardware or workaround; or abandon the tasks related to the specific risk.

DAMAGE:

Slowing down progress; spend extra time on finding alternative; spend extra money in finding alternative; and maybe abandoning parts of the project at a greater scope.

6.6.3 Conflicting schedules.

Meet with those who cannot attend announced meetings separately or keep constant con tact.

DAMAGE:

Slows down the whole team sometimes; more time spent on meetings; and extra time spent on communication.

7.0 Information Browser Team

7.1 Project Task:

7.1.1 The Information Browser

7.1.2 Scope of the project

• infinity The information browser is intended to manipulate existing html files for viewing on the Newton.
• infinity The browser will have the capability to maintain the links which are part of the html code.
• infinity The browser will use the mapbuilder tool being developed by Chris and Daniel in order to maintain consistency between the two projects.
• infinity The team will not concern itself with maintaining communications, wireless or serial, between the machine providing the html code and the Newton itself.
• infinity The team will also not attempt to modify the Bookmaker program which handles the conversion of html code to Newton books. Instead, the output and input will be format ted appropriately with scripts.

7.2 Team description:

• infinity Learn the Newton Bookmaker tool.
• infinity Coding the appropriate input and output scripts.
• infinity Coordinate with the map builder team in order to ensure compatibility.
• infinity Maintain documentation on schedule slippage for the project.

• infinity Learn the Newton Bookmaker tool.
• infinity Coding the appropriate input and output scripts.
• infinity Produce documentation for activities undertaken by the team.
• infinity Maintain documentation on software effort and any costs that arise.

7.3 Team Goals:

7.3.1 Learning:

7.3.2 Coordination:

7.3.3 Documentation:

- Schedule slippage - Software effort - Any substantial additional costs - Development of the information browser

7.3.4 Building:

7.3.5 Assessment:

7.3.6 Functionality:

7.4 Team Activities:

7.4.1 Learning:

1. 1. Go through the NTK tutorial to become familiar with Newton programming.
2. 2. Speak to Sue Long about the Newton Bookmaker utility.
3. 3. Evaluate/Examine the Bookmaker utility to understand basic functionality.
4. 4. Begin preliminary testing on html to books conversion i.e what are the results?
5. 5. Write basic scripts in order to become familiar with the scripting environment.

7.4.2 Coordination:

1. 1. Have an initial meeting with the map builder team to work on conceptual ideas.
2. 2. Establish set meeting times (on a weekly basis) to continue coordination, especially in the coding stage.
3. 3. Appoint liasons between the groups who can communicate whenever necessary.
4. 4. Develop the software conjunctly on a periodic basis.

7.4.3 Documentation:

1. 1. Maintain a "sub" project notebook for the information browser.
2. 2. Perform scheduled evaluations for the following software development areas:

• infinity Schedule slippage
• infinity Software effort
• infinity Software costs
• infinity Development or goal changes

1. 3. Assign roles to each group member to keep track of the major software development areas.
2. 4. Periodic printing of evaluation material so that it can be available to the entire Cyber guide team.

7.4.4 Building:

1. 1. Have scheduled programming times so that the team can work as a unit in the coding process.
2. 2. Periodic checks to verify code consistency and control error propagation.
3. 3. Periodic evaluations of the code to verify the other team members work.
4. 4. Coordinate opportunities for the map builder team to examine the teams code and func tionality.

7.4.5 Assessment:

1. 1. Have scheduled intervals where the entire documented process is examined in order to assess the state of the project.
2. 2. Allow all of the "sub" teams to review the assessment.
3. 3. Begin, if necessary, new goals and activities for the remainder of the project period.

7.4.6 Functionality:

1. 1. Assess the functionality of the following areas:

• infinity Ability to receive html format
• infinity Ability to convert html format
• infinity Ability to create viable Newton books
• infinity Ability to maintain html links as Newton books
• infinity Ability to interface with the Map Builder tool

1. 2. Assess the ability of the software to integrate with the CyberGuide Project as a whole.
2. 3. Produce documentation to verify the functionality.

7.5 Team Schedule:

7.5.1 Week 1 (Jan 15 - 21)

• infinity Develop project plan [Prabhath]

• infinity Begin NTK Tutorials and Bookmaker examinations. This will continue until Jan. 21, at various times. [Danny and Prabhath]

• infinity Meet with Mapbuilder team to agree on platform and conceptual direction. [Danny and Prabhath]

7.5.2 Week 2 (Jan 22 - 28)

• infinity Begin preliminary coding and functionality. [Danny and Prabhath]
• infinity Begin documenting development process [Prabhath]
• infinity Begin documenting schedule changes [Danny]
• infinity Set a meeting time to meet with map builder group to discuss progress
• infinity Please note that Week 2 will be a basic plan for activities for a typical week. The rest of the schedule contains dates that are milestones that we set:

7.5.3 Week 3 (Jan 29 - Feb 4)

• infinity Assessment period, to track programmer proficiency and essentially finish design period

7.5.4 Week 4 (Feb 5 - 11)

• infinity Have become proficient in the Newton Bookmaker platform and can write scripts.
• infinity Preliminary scripts and design ideas are completed.

7.5.5 Week 5 (Feb 12 - 18)

• infinity Write scripts for accepting html input.

• infinity Work on conversion process. In other words attempt to ensure that the html code is properly turned into Newton Books.

7.5.6 Week 6 (Feb 19 - 25)

• infinity Reassessment period.

• infinity The output should be in Newton Book form and html links will be preserved in the book format.

7.5.7 Week 7 (Feb 26 - Mar 3)

• infinity The Map Builder tool should be integrated with the Information Browser.

7.5.8 Week 8 (Mar 4 - Mar 10)

• infinity Prepared final documentation with schedule slippage, costs, efforts, and the develop ment process should be ready.

7.6 Project Risks:

7.6.1 Both team members are new to Cyberguide and Macintosh programming.

1. 1. Begin immediate and early immersion in NTK and Newton Bookmaker:

• infinity impossible to calculate time necessary for familiarity
• infinity inherent complexity within platform cannot be overcome, even with tutorials.

1. 2. Coordinate extensively with Sue Long and other graduate assistants:

• infinity Will take time away from actually completing project
• infinity Less learning and more mimicing of code

7.6.2 The chosen platform will not allow the desired functionality.

1. 1. Spend time initially researching other html conversion utilities:

• infinity Will cause schedule slippage
• infinity Using other platforms may not allow us to be advised by other members of the Cyberguide team

1. 2. Switch platforms if necessary further in the project development period:

• infinity Obvious schedule slippage, much more extensive
• infinity Problems with overall system compatibility

7.6.3 The communications platform will limit downloading of html documents.

1. 1. This area is not our teams directly, but our end could be modified to rectify communica tion incompatibility:

• infinity Lack of communication knowledge could slow project down
• infinity Major changes could be necessary if the communication tools are not examined carefully
• infinity Script rewrites would also be likely

7.6.4 The map builder coordination effort will not be compatible, causing redevelopment of one or the other tool.

1. 1. Work with map builder team to modify their software end:

• infinity Lack of experience might not help such an effort
• infinity The difficulty in modifying the map builder tool is difficult to estimate beforehand.
• infinity Once again schedule slippage is likely

1. 2. Modify the information browser to be compatible with the map builder:

• infinity See Risk 3

8.0 Key Personnel

8.1 Project Leader - Robert Duncan

• infinity Act as liaison between the Project Team and the instructor (Mike McCracken) and the sponsor (Gregory Abowd).
• infinity Set the schedule for the project.
• infinity Guide the direction of the project in conjunction with the sponsor.
• infinity Responsible for the project's overall results.

8.2 Domain Expert

• infinity Aid other project members in learning NewtonScript.
• infinity Aid other project members in understanding the NTK.
• infinity Act as software engineer as needed for the various teams.

8.3 Equipment Manager - Eugene Liu

• infinity Keep track of equipment whereabouts at all times.
• infinity Make sure that batteries are charged and ready for use.
• infinity Have faulty or damaged equipment repaired or replaced (if feasible).
• infinity Responsible for the location of the equipment.

8.4 Web Manager - Chris Goodrum

• infinity Convert FrameMaker documentation to HTML when needed.
• infinity Maintain the Cyberguide web page with helpful links.
• infinity Responsible for the Cyberguide page content.

8.5 Meeting Manager - Daniel Bassett

• infinity Take meeting minutes.
• infinity Develop and coordinate meeting agendas with faculty advisor.
• infinity Make sure the meeting is following the meeting agenda.
• infinity Responsible for maintaining and distributing meeting minutes.

8.6 Documentation Manager - Prabhath Valiveti

• infinity Responsible for quality of the documentation.
• infinity Make sure the documentation is up to date.

8.7 Software Manager - Micheal Minori

• infinity Establish and setup revision control system for software files
• infinity Make sure that software is being well commented.
• infinity Backup software files on a regular basis.

8.8 Presentation Manager - Stephen Eley

• infinity Organize presentations
• infinity Make sure everyone is doing their part in the presentations
• infinity Responsible for the quality of the presentations