The Mapper

General:

The Mapper is a subsystem of the Scheduler. Its job is to create zones after the user draws them on the Mapper. The Mapper is launched when the system starts. The only user of the Mapper is the tech guy who is supposed to start the system. The user is supposed to click on the drawing pad to create zones.

Preconditions:

A model server should be running and there should be a successful database connection.

Responsibilities:

Return the number of zones created to the model
Store the zone polygons in the database
Convert addresses to zones

Architecture:

Dataflow Diagram – Use Case 1:

GUI Actions List:

GUI Action

Goal

Methods that are called

Actions

Mouse clicked on the drawing area

Draw in the drawing pad

paintComponent()

1. Add points

2. Generate polygons

3. Draw polygons

Save button pressed

Save data into the database

saveDB()

1. Save polygons

2. Save GPS coords

3. Save the filename

Load button pressed

Load file

ImageFileToLoad()

1. Load a map image file

Clear button pressed

Clear the drawing pad

clear()

1. Clear all points

Javadoc Link:

http://www.cs.washington.edu/education/courses/cse403/CurrentQtr/www/docs/full-api/index.html

Tests attempted:

Manually clicking on the mapperUI, then monitor all of the data structure if they are doing the right thing.
Unit test that contains tests for each method.

Known Bugs:

The number of zones returned is not correct.

Features for Future Versions:

Drag zone boundaries to alter their sizes.