This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
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

NX: About GUI

 
Flavio Nobili
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi people,
We must build a Data class to access the database file. And in this class we must have, besides others, create and detele methods. But, where should I use these methods? The specification says the client needs to book, but it doesn't say if I have to allow the user to create and delete records.
Should I include in the GUI buttons to create and delete?

Regards,
Fl�vio.
 
George Marinkovich
Ranch Hand
Posts: 619
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Fl�vio,
Originally posted by Fl�vio Fran�a:
We must build a Data class to access the database file. And in this class we must have, besides others, create and detele methods. But, where should I use these methods? The specification says the client needs to book, but it doesn't say if I have to allow the user to create and delete records.
Should I include in the GUI buttons to create and delete?

The methods you mention (create and delete) are not used by your client application. They will probably be tested by the grader using some sort of testing harness (which is why the assignment instructions require us to implement all the Sun-supplied interface methods in the Data class). I would not include create and delete buttons in the GUI since as you say all your client application needs to do is search and book. The implementation of the Data class counts for 40 points. I think if you fail to implement any of the required database operations you put some of these 40 points at risk.
Hope this helps,
George
 
Leo Tien
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Fl�vio:
I agree with George, you shouldn't use create/delete method at all but you must implement they.
The assignment requires you must support search and book mechanism in GUI:
....� It must allow the user to search..... � It must allow the user to book a selected record,....

Although it never requires you must implement create/delete mechanism, but nearly all people implement it. As George statemented "if you fail to implement any of the required database operations you put some of these 40 points at risk.".
I think in the assignment, it hints that why have create/delete method in DBMain interface:
The company's IT director has decided to migrate the existing application to a Java technology based system. Initially, the system will support only the CSRs, although the hope is that this interim step will give them a starting point for migrating the system to the web.

Because the system we make will migrate the existing application, I think these application must have create/delete mechanism, but now, this system only support to CSRs, so the client of it haven't create/delete operation.
Make sense?
 
Flavio Nobili
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Leo,
Thanks for the explanation.
So... Is it a good idea to put buttons to create and delete in the GUI, or I may lose points doing so?

Regards,
Fl�vio.
 
Leo Tien
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Fl�vio:
Because this client GUI is supported only to CSRs, so you don't display create/delete button on it, it not the customers requirement.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic