Teams Update
Wednesday, July 24, 2002
Here is our status as of mid-afternoon of Tuesday, July 23, 2002:
- Jesse and I finished up the Scheduler interface, added JavaDoc comments to it, and Exceptions.
- "Fixed" the CabConsole unit test bug David made lieu of by disabling the test (more on that later).
- Added unit test for the Dispatcher UI.
- Danny began looking for possible acceptance tests we can create based off of the use cases and the test case list we put up on the website.
- Unsure how to generate test data. There is some hardware that's been mentioned on the website, but we don't know what format to create the data in or what to send it to in our program. For example, the Cab UI hasn't been flushed out enough for us to create some sort of I/O mechanism for the credit card or GPS data.
- Would like to start building the actual scheduler class sometime soon. I think Jesse might have started in on that today, but I'm not certain.
- Danny added an outline of some acceptance tests to the internal webpage and renamed what was formerly acceptance tests to unit tests because it addresses tests for each subcomponent of the system.
Some suggestions:
- Add the ability to read UI commands (like button clicks) from a text file to make testing the UI easy.
- The Mikam Tribe has not met since Monday.
- Margaux has been trying to help coordinate interfaces with other groups via email.
- The team will meet again and begin coding as soon as everyone has decided upon their interfaces, which will hopefully be later on this week.
- Have been working on the interface for the data store.
Concerns/questions (discussed with MIKAM Tribe, but might be useful to the rest of the class):
- How were you thinking the backups would work?
- What information are you going to need to restore the model in case of a crash? How do you want that data packaged? One huge object, or lots of "get" functions? Incidentally, we are definitely going store customer objects, cab objects, and zone geographic information.
- Have you figured out how you're representing zones geographically yet?
- We could use some extra information in the Customer class:
- We would like a reference to the cab the customer is in (if any).
- We're not sure if you have an idea of what the "time of pickup" variable is going to be
for.- We would also like some indication of the type of transaction: hailed
cab, reservation, or "now" call (this one needs a better name).
- Worked on CabConsole hardware simulation, on the internet site.
- Initial CabConsole UI for the prototype, completed.
- Interface for the CabConsole and the Transmitter, completed.
Problems:
- We are still not sure what are the responsibilities of the transmitter.
- What are the responsibilities of the Mapper?