Teams Update
Monday, July 29, 2002

The SegFaults

Team Status

• Scheduler- A lot of the primary functionality behind the scheduler is either complete or well under way. The scheduler update function is threaded so it will update automatically. A few parts of the scheduler are still waiting for the mapper to be completed.
• Mapper- The zone generation code based off of the Voronoi diagramming technique is about 75% complete. We plan to complete coding and begin testing for this component on monday.
• MapperUI- The mapper UI code is about 50% complete. Right now the UI will open a window with a picture off a map and has fields for entering GPS coords for the upper left and lower right hand corners of the map. Eventually, the voronoi code will allow you to create hot spots by clicking on the map and then genrate zones(convex polygons) from those hotspots.
• Acceptance Testing / Data - A simple Random Customer and Credit card number system has been implemented which can feed data to a sub system or a file. However, since fireman went down this last friday it's kinda put a pincer on testing.

Team Plan

1. where you are w/ respect to goal. Where ahead in some parts and behind in others.
   Hopefully by wed/thur we can start testing the scheduler and by friday we will start having some basic acceptance tests. Overall about 45% towards our goal
2. next week's plan
   1) Finish Mapper internals on tuesday
   2) Finish MapperUI on wednesday
   3) Finish Scheduler by Friday
   4) Have at least one data throughput acceptance test done by friday
3. est. time
   1) 15 man hours
   2) 18 man hours
   3) 15 man hours
   4) 6 man hours

Suggestions, Advice, Solicit/Offer help
Here is the bug tracking tool David was suggesting we look at http://www.elementool.com/

Mikam Tribe

Status

• Currently, we are plugging along with our code. We met today for a few hours and got the basics of the first two user cases done. 
• RMI has also been set up for the model end.

Team Plan

• With the goal of having at least the first user case running by Wednesday, as long as nothing goes wrong, we should meet this goal.
• Hopefully, we'll also have a few other use cases running by then. 
• Next week as long as we can build again and we can all cooperate well, we should be able to get a substantial number of use cases done.

Note to class: We should discuss more use cases and diagram them as the
team leads did last Friday. These were very useful to look at when
writing code.

Team Doug

• For Wednesday, we are going to implement storage for information as shown in the data store interface (no output yet, though). 
• We will fully define the report interface. The first thing is contingent on getting database access.
• We have mostly been working on refining the data store interface, and have recently done some work on the dispatcher override reports.

The Masters

Status

• We have implemented three new classes SchedulerTransmitter, TransmitterTower,
  CabTransmitter. You can now send a customer or a string all the way from
  Scheduler to the CabConsole and vice versa.

Suggestions, Advice, Solicit/Offer help

• If you want to send information from the Scheduler to the CabConsole please
  instantiate SchedulerTransmitter and use the Transmit method. You will need to
  specify as arguments the string destination ("CC") and the information to send(
  which can be a Customer or a String). If you want to grab the information sent
  from the CabConsole to the Scheduler, you will need to call the method
  getMessage() or getCustomerInfo()from the SchedulerTransmitter (they return an
  arraylist of strings or a CustomerQueue with all the information).
  
  In summary, to send or receive information to/from CabConsole use the
  SchedulerTransmitter class and its methods.
  
  We committed our changes but fireman seems to be broken. The last build has
  been hanging for hours, since yesterday. Has anybody notice that??
  

Team Tsunami

• RMI research is on hold for atleast one more day because 1/2 of our group is out of town.
• Dispatcher UI has been completely laid out in java swing. John is communicating with the model group in order to get the agreed upon functionality for Wednesday finished.
• The manager UI is still under construction with java swing.