BUG GPS Planning Meeting 12/9/98

Attendance:

Name:E-mail:
Jonathan Boothjbooth@uiuc.edu
Tim Johnsontcjohns1@uiuc.edu
Vikram Kulkarnivkulkarn@uiuc.edu
Jason Lutherjluther@uiuc.edu
Mike Maginmmagin@uiuc.edu
Charlie Powepowe@uiuc.edu
Matt Wronkiewiczwronkiew@uiuc.edu
Others

Interface Design and Requirements Overview

The GPS software will be broken into at least two applications. The user interface will be in one application, which will take care of processing data and reports. The other app will communicate with the GPS and provide data to other applications. The hardware is abstracted in the GPS interface application, and the GPS ionterface handles communication with multiple programs simultaneously. The user interface provides a map window with geographical and street information. It also displays basic location and speed information. A seperate window provides graphs and trip maps. A world map window shows a globe with the current GPS position. Saved trip routes can be displayed on the globe for reference. Drawings of the map and globe windows appear below.

Using the new message-based communication framework should allow the developers of different modules to work more independently of each other.

Module Responsibility for GPS

  • Map Window
    • Basic Interface: Charlie Powe
    • Map Display: Jason Luther, Charlie Powe
    • Graphs: Vikram Kulkarni
    • Trips: Vikram Kulkarni
  • GPS Interface Application: Jason Luther, John
  • Export/Import Data: Tim Johnson
  • History of GPS: Jason Luther, Broden
    • Trips
    • Origin
  • Organize Data: Vikram Kulkarni
  • World View: Matt Wronkiewicz