Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

B&S - GUI Functionality

 
Joshua Fix
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Something very shocking and mind-bottling just hit me in the face (now that I have a really cool GUI that can search, add, and delete records)... I just realized that there is NO requirement in my assignment to add or delete records from within the GUI. So all of the business logic sits on the server, since I have already written the code to implement the required interface, but I never actually have to do anything with it? Seriously? Here's the client requirements:
* 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.


Which brings me to my second question... I have never understood how or what I'm supposed to do with the "owner" field of my database. The provided database has all owner fields blank. There is a note after the description of the field:
Note that for this application, you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them. If this field is all blanks, the record is available for sale.

It says that my system does not interact with these numbers... but it simply records them. So what is it that gets recorded here? Do I just produce a random 8 digit number each time a client GUI is started? And does this field get displayed in the JTable? Or perhaps simply a "booked" flag?
 
Chih-Wei Lee
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Fix:
I provided a text filed on GUI for user to enter 8 digit customer id.
Because the user are CSRs, so the scenario would be
customer told CSRs his id by phone and then CSRs entered this customer id
to book a flight for him.
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy, my buddy.

It is not required that you allow users to add or delete records. All you have to do is allow the user to book a room/flight, that is, update a record, filling the "owner" field (which is the field that represents the customer that booked the room) with the number of the customer. The thing is, the user will simply provide an 8 digit number in the GUI and will hit a button, which will update the chosen record, filling the "owner" field with this number. And after booking a room/flight, you update the model of your JTable, so it can reflect the new reality.

Hope this helps, partner!
[ June 26, 2008: Message edited by: Roberto Perillo ]
 
Soroj Margun
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I can confirm that you can pass the exam without create add or delete function however your GUI may look good with them. By the way, spec. said that the function that beyond scope may not increase your score so implement only specified function in spec. is enough to pass.

[edit: forgot to answer]
For the owner number, you can both hardcode or provide the way to enter this number. Mine is hardcode in properties file.

Wish you all pass.
[ June 25, 2008: Message edited by: Soroj Margun ]
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey, partner.

When you say owner number, you mean the customer ID that the user has to provide in the GUI? If so, are you really hardcoding it? How are you dealing with it exactly?
 
Chih-Wei Lee
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hardcoding customer id is not a good way.
Since you can't distinguish which customer books which contractor.
All contractors will be booked by the same customer.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic