Teams Update
Wednesday, July 31, 2002
Team Status
- Mapper Internals- currently done adding any new functionality to the internal of the mapper subsystem. Almost done with the
unit testing of the subsystem and will begin merging mapper UI with the subsystem tonight.- Mapper UI- A simple mapper window with GPS entry fields has been created. A picture of a map can be loaded to the window and points can be placed on that map.
- Scheduler - Mechanism for updating the scheduler based on a timer has created. Customers inside the scheduler are sorted by pick up time using a binary tree for efficiency.
- Bug tracking Interface - Bug tracking system is up
- Acceptance Test- Since the system is in the middle of a major architectural update it's not possible to create an automated test for the system or even start the system up to test. As such we are going to elaborate on the testing steps on paper for our first use case tonight
Team Plan:
- Integrate the Mapper with the rest of the system (Scheduler, Model, etc)
- Create more acceptance tests
- Integrate the scheduler with the system
- 3 est. time
- Mapper - complete by friday
- Scheduler - complete by Monday
- 1st Acceptance test - complete by Friday
Team Status
- Most of the internal code related to the user cases work.
- Met with the Masters to discuss the interface between the Model and the cab consoles.
- Meeting with Database group.
Team Plan
- Work on initializing the Model, which involves initializing Zones, Cabs, etc.
- Work in class to get the first use case working.
Team Status
- We have successfully connected to the database using JDBC in Eclipse! That's pretty much the extent of our accomplishments so far since that took longer than we thought.
- We are currently working on getting data storage methods working. Things are progressing well, but it is not finished yet.
Team Plan
- We are a bit behind in getting the data storage methods working. That will be our next priority. By Monday, we are aiming to have all of the data storage methods working (add, update, etc.) as well as the ones that return all objects in the database (getAllZones, etc.)
- The report format has not been figured out yet; that WILL happen by Friday.
Team Status:
- Currently, working with the MIKAM Tribe to iron out some details.
Team Plan:
- Our system should support one user case, but I am not sure about how it will work with Model because that is not resolved.
- Resolve the issues that we have of integrating our part into program.
DispatcherUI's layout is complete.
Team Status
- ManagerUI's layout is 1/2 complete - should be done by tomorrow.
- Had difficulties with RMI, and consequently, are moving on without it.
- we're abstracting a network connection with a new object called "communicator" to communicate with the model.
Team Plan
- w.r.t. our goals, we are right on schedule.
- Tomorrow all UI layouts should be complete, and we can begin work on the underlying interfacing with other components. We will continue to toy around with RMI.
- We should have all our responsibilities taken care of within a week from tomorrow.