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

Providing full CRUD functions in GUI

 
Alan Mc Kernan
Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

My spec says to provide functions to showall/search/book. Alot of people seem to provide delete/create/update functionality also.

Is this deemed a good idea? Originally I thought heck why not. But now im thinking maybe the customer (hypotetically) does'nt want their agents to be able to create/delete/update etc. They only want the agents to be able to search and book.

Has anyone thought of this?

Alan
 
Saheed Adepoju
Ranch Hand
Posts: 267
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Alan Mc Kernan:
Hi,

My spec says to provide functions to showall/search/book. Alot of people seem to provide delete/create/update functionality also.

Is this deemed a good idea? Originally I thought heck why not. But now im thinking maybe the customer (hypotetically) does'nt want their agents to be able to create/delete/update etc. They only want the agents to be able to search and book.

Has anyone thought of this?

Alan

Hi
Well providing CRUD operations in the GUI would be a total waste of energy cause the instructions says ..should allow the user to book and search... I dont know what your instructions say but if they say you must provide full CRUD in the GUI then u must Usually guys here at the ranch forget(dont want to) implementing the create() and delete() sometimes. You can't dodge the update() cause that is how you book a record(By writing the Owner id to the the record).
Anyways just dont do an overkill for the project, remember there aint no money involved when u pass the assignment, just a certificate, so just provide what they want. Have a nice day!
 
Bob Nedwor
hangman
Ranch Hand
Posts: 215
Eclipse IDE Oracle Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have basically already raised this issue (as I am sure others have). I suggest you check out :
this link

or at http://www.coderanch.com/t/187973/java-developer-SCJD/certification/Don-Think-Any-Statements-Implemented

Based on this input from Andrew, it seems that it may very well be acceptable to just implement these un-needed methods over in our Data.java, by simply throwing the UnsupportedOperationException. This is all I am doing.

I hope this helps.
[ March 06, 2006: Message edited by: Bob Nedwor ]
 
Alan Mc Kernan
Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Interesting..

I'd honestly prefer to add the CRUD functions. It would look more like a full application. I'm just afraid that *maybe* this would lose me marks. Or maybe it would gain me marks - yes I know they say no more marks for added functionality - but if an examiner looks at a full range of functions, and a shiny interface, I'm bank that they will give more marks.. at least overall.

No I wont get any money - But i would like to get a better score. Sure if i was doing it for money, well I would'nt be

Andrew, have you any thoughts?
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Alan
Andrew, have you any thoughts?
Too many, or too few, depending on the amount of alcohol I have been drinking

Seriously, I have seen many people get perfect marks for their GUI without having Create or Delete functionality in it. I don't honestly think that adding these two functions is worth the extra time, especially with the risk that the assessor might not like what you have done. Even if you do it perfectly, it is still possible that your assessor may decide that you have gone beyond the scope and get a negative impression of your entire application as a result (this is especially true if the assessor is working in an organization that provides fixed price contracts - going beyond scope is almost always considered lost revenue in those cases, and is really frowned upon).

Remember you do have these words in your instructions: "You will not receive extra credit points for work beyond the requirements of the specification."

Regards, Andrew
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic