• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Completeness

 
Trym Moeller
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I keep on dreaming up new functionality when deciding what to implement.
My assignment about accommondations, says that "I am commisioned to let the user generate a list of accommondations matching the users choice of name/location". But I imagine that for the application to be working I must also implement functionality to book and unbook an accommondation, to create, update and delete an accommondation (hotel manager job).
How much of this do you think is relevant to the assignment?
Best regards Trym
PS. any comments are appreciated.
 
Jay Bromley
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Trym,
Don't do it! At least not for the project you turn in. I went through a similar phase in thinking, but the collected wisdom seems to be do only as much as your assignment tells you to do. There is no extra credit for extra features, Sun is interested in how well you do what they specify and nothing more. Maybe one can consider it practice in avoiding feature creep. Gives you less to test and less things to go wrong also.
Of course, if you're interested in doing all this for personal learning, great (this is what I'm doing, I've got an exam branch and an experimental branch in my source tree.)
Regards,
Jay
 
Bill Robertson
Ranch Hand
Posts: 234
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Trym,
What do your specifications say? My specifications say the User Interface
only needs to allow the user to "book". So thats all the functionality
I added on the front end. BUT, and this is a big BUT, do you have
to implement on the back end an interface provided by Sun that has
delete, update, create...methods. If you do I would seriously consider
implementing them but not placing them on your GUI or anywhere else
for that matter. Just keep them in your Data or DataAdapter (or both) classes and JUnit test them from there. The very mass majority believe these methods must be implemented and working. As if they could be plugged into you GUI at anytime. Get it.
Bill
 
Trym Moeller
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks.
I will stick to the nice way, just implementing the required interfaces and the book functionality in the gui and test as much as possible with junit.
\trym
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic