"to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user"
and "the search mechanism should be flexible..."
The specification of FlightByNight looks to be different. It does not require "Or" search (3b).
It looks like your suggesting is to avoid doing "OR" searching by trying to turn the interpretation of the URLyBird requirement, which is easer to implement, which extremely dangerous game.
[Tony]: If we use a JBox the user can only select the full value for each field, so findByCritea is OK.
Mmmm... but don't you also allow the user to type in their own text to search for? I think that really needs to be an option. What if the user wants to search for something that was just entered in the DB, after the JComboBox options were initialized? I suppose you could allow a manual refresh of the box options. (Or it could be done automatically, but I think that would generate a lot of unnecessary work for the server and network.) And what if the DB grows huge and there are thousands of unique values to choose from? It may not be practical to list them all in the JComboBox, or even if they're listed, the user may not want to try to search through them all.