GeeCON Prague 2014*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Assumptions about the GUI Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Assumptions about the GUI" Watch "Assumptions about the GUI" New topic
Author

Assumptions about the GUI

Douglas Kent
Ranch Hand

Joined: Oct 06, 2000
Posts: 171
I am making the assumption that since the instructions did not talk about creating an administrative interface, the only user features we need to implment are lookup and flight booking. This would lead to a further assumption that since the interface is limited to these functions, the new database constructor for "Data" would never be needed in the user interface either. Am I going wrong here? Or is it implicit that since the add record method is implemented in "Data", we need to support that in the GUI?
Shankar S
Greenhorn

Joined: Nov 02, 2000
Posts: 8
Douglas,
I am also making assumptions that we have to provide viewing and flight booking.
For flight viewing we can search the binary file and show them in the jtable. what about booking.
Do we need to modify the no of seats in db.db file or do we need to keep the booking information in seperate binary file?

Douglas Kent
Ranch Hand

Joined: Oct 06, 2000
Posts: 171
We need to deduct the number of seats available for that flight by the number of desired seats from the customer input. I would NOT keep that information separate...
Abhijeet Premkumar
Greenhorn

Joined: Nov 02, 2000
Posts: 18
Douglas,
Spot on. I think these assumptions are pretty fair. The specs never make mention of the fact that you would need to create a new db. This would also mean that you don't have to provide the constructor to the data class.
In my opinion the GUI is the only part in the entire assignment which would be more or less unusable for future projects. What do you think?
With warm regards
Abhijeet
Originally posted by Douglas Kent:
I am making the assumption that since the instructions did not talk about creating an administrative interface, the only user features we need to implment are lookup and flight booking. This would lead to a further assumption that since the interface is limited to these functions, the new database constructor for "Data" would never be needed in the user interface either. Am I going wrong here? Or is it implicit that since the add record method is implemented in "Data", we need to support that in the GUI?

Douglas Kent
Ranch Hand

Joined: Oct 06, 2000
Posts: 171
I certainly think it would be usable, provided you design it correctly, and de-couple the GUI from the DB-specific methods used to access our little DB...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Assumptions about the GUI