22-Mar-2005

Vision
Team
Client
Schedule
Minutes
Case Studies
Deliverables
 
Date : 22-Mar-2005

Venue : S-3-179 (UMB)

Attendees : ReF Team, Prof. Bolker.

Minutes:

  1. Implement the changes that Professor had suggested for providing the Search and the AddType forms.
  2. Application should be such that it should know what inside X1 is, i.e. inside Ref knowing what X1 does or X1 should know what's inside Ref.
  3. Find out about the ISAM installer. If it needs to be purchased, first thing was to inquire whether Bill Perry can provide us.
  4. If the application was able to write to Excel files, if the size was the only limit while creating them, then, make the application to write to several different Excel files.
  5. Give the correct problem, when the application writes to Excel file. (let the professor know, if writing to the Excel file behaves in a haphazard way).
  6. Play with X1, treating it as a Gray box. Try to write sample programs which can give some output that's relevant to the X1s search results. Though we cannot use X1s SDK to embed in our application, we should let the customer know that we know how to use X1s functionality.
  7. Google Desktop Search API: In design, write a small API that can use the Google Desktop API for searching the hard disk.
  8. Using Windows API, write a small Proof of Principle Test to search the desktop (if possible)
  9. From UI's point of view, the application is boring. And from the customers perspective, the application is not flowing.
  10. While designing an application, the customer should be given the application in such a way that the customer can start using it. (Providing the functionality incrementally, that the user can start using it right away.)
  11. The application should have few mouse clicks and should be fairly simple.
  12. Give the customer two versions of the application, one with more mouse clicks and one with few clicks, give a choice to the user to choose the one that he/she likes.
  13. Application doesn't have the End-to-End functionality. When End-to-End functionality is provided to the customer, then the feedback that we get would be the right one. Else the feedback that we get now is hypothetical feedback.
  14. Satisfy the customer, by giving Unique hit functionality. Though the customer might not use it, it will still keep him satisfied.
  15. Professor will accompany us next time as
    • we could not convince the customer with the demo of the release we had given before
    • to win customers confidence  in the next meeting Professor is going to contemplate our application.

 


 
 
ŠAll rights reserved.Managing Medical Data team UMass Boston 2004