next up previous
Next: BNF Up: CMSC420 Project - Spring Previous: Invalid Commands

Part 1: TreeMaps, Fibonacci heaps, and a Mediator

In Part 1 we will be getting our feet wet with JAVA (hopefully not for the first time) by implementing a treeMap which will store the sites, which can be bases or targets, sorted by site name (dictionary data structure); another treeMap which will store these sites based on their geographic location (spatial data structure); a Fibonacci Heap to store base inventory data; and, a Mediator which is capable of parsing and executing some basic commands.

To help facilitate the interactions among these various objects, we would recommend that you design some basic objects which you will use to store the data in. For instance, design a Base class which stores all of the information related to a site (name, latitude, longitude, etc). However, when you design your Fibonacci Heap, and treeMaps, you are discouraged from expecting a Base object. Rather, try accepting any generic object (either ``Object'' or create a base class or interface which Base derives or implements which the other objects expect). The reason for this is that we may not be storing only Bases in future projects (hint hint). If the idea of accepting a generic object is confusing, see the TA or post to the newsgroup as this is a very useful design which will save you lots of time later on. If all fails, go ahead and have your objects expect a Base and you can worry about changing it in later parts of the project. Note: you will be creating "Bases" and "Targets" so you might want those to inherit from some super class (maybe a Site super class???).

The following commands should be supported for Part 1 of the project.



Subsections
next up previous
Next: BNF Up: CMSC420 Project - Spring Previous: Invalid Commands
MM Hugue 2004-02-28

Web Accessibility