Announcements
Members & Reports
Project
Schedule
Meetings
Documents
Contacts
Links
Contact Meeting: 03-07-02

-Discussed the Test Case Document: Overall, pretty good.

Suggestions from client:
- Separate the document into unit tests and system tests. Also, test cases, especially with system tests, should be easy enough to read for a user that has no experience dealing with the system.
- There should be steps outlining exactly how the user interacts with the system to check the test case.
 
Discussed Version 1.0 which they have installed.
Good news: They were impressed by it.

Problem with Version 2.0:
We then discussed garbage collection in Java and why our Version 2.0 is having a huge memory overhead, and they suggested that there may be some leaks in the pointer references within the hash table implementation, as previously discussed in the other meetings.
 
Voice from the client:
-Abhay and Radha don't really care as much for the GUI, they would rather want a "quick and dirty" engine that can parse all the layers of the Bluetooth stack. So, if there is a huge memory overhead with having the GUI, we shouldn't worry about that as much, we should concentrate on the engine itself.
- The clients have stated that we can always "scope down" our application. They would rather want to see 3 optimized layers that are fully working rather than 4 layers that are not working properly and are not reliable.
 
Others:
- We were given the TS-107 spec that Charles requested
- SDP discussion-Radha has some good knowledge about it, so she will be willing to help us with it.