Hello all, I have a couple of doubts regarding what functions should we supply in the GUI. Here is what Sun expects: In the application overview, it says
The new application, using the existing data file format, must allow the CSRs to generate a list of accomodations that match a customer's criteria. This is the project that you have been commissioned to implement.
This requirement is same as the second requirement in User Interface below And in the User Interface, it says
The user interface for this assignment must satisfy the following criteria:
It must be composed exclusively with components from the Java Foundation Classes (Swing components).
It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
It must present search results in a JTable.
It must allow the user to book a selected record, updating the database file accordingly.
Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the users when this occurs
But what about the other funcationality that we did in the Data class. I mean we have implemented the functionality like creating new record, deleting a record, updating a record. Are we not supposed to provide this functionality in the GUI? Or we just have to allow only two business operations shown below.
The search/find functionality. Will give all search options as follows: CSR can search all records, can search on name/location or both.
The book functionality. CSR can book a room by selecting record in JTable or by entering record number in the textfield and book button(I want to provide this functionality too, is it ok? Or just allow CSR's to book only by selecting record in JTable? All suggestions are appreciated).
Are these two functions sufficient on the GUI side for project scope? Appreciate your help, thanks. [ February 26, 2004: Message edited by: Satish Avadhanam ]
Originally posted by Satish Avadhanam: The book functionality. CSR can book a room by selecting record in JTable or by entering record number in the textfield and book button(I want to provide this functionality too, is it ok? Or just allow CSR's to book only by selecting record in JTable? All suggestions are appreciated). Are these two functions sufficient on the GUI side for project scope?
Yes, search and book are sufficient on the client GUI side. You only need to implement one way to book a record. I prefer a TextField and a Book button, but allowing the user to edit the owner field in the JTable is also OK.
SCJP, SCJD, SCWCD, SCBCD
posted 14 years ago
Thanks George. I have also a couple of doubts regarding the design. I'm still working on it. Will post it once done. Please comment on it. Appreciate your help, thanks.
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database