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

unspecified requirements

 
Cleverson Schmidt
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ranchers
I'm a bit confuse with my requirements.
I'm working on the URLyBird test and it is clear to me that clients will be able just to book and search hotel rooms, at least this is what is described in the problem statement, but if I look at my DB interface I can see methods like delete and create. Am I supposed to implement these methods? What if I don't? In that case what would be the best approach, maybe throw an UnsupportedOperationException? Is it possible to loose points if I implement just the least?
Thank you in advance
Best Regards
Cleverson Schmidt
 
Michael Hartman
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You should provide implementations for all methods of the given DB interface. I believe part of the assignment is to develop a (potential) fully working database server. You're right though, the client or business interface will only take advantage of the booking and searching functionalities.
 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
They are 2 seperate issues:
1. For all methods defined in the interface, you need to implement ALL of them.
2. However, in your GUI, the only methods that required to support are ONLY search and book.
I am not sure whether, in the interface, you only implement the search and book functions will lead to mark deduction, however, to play safe, you should implement all functions, as suggested by the instructions.
Nick
 
Min Huang
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Where? I do not see anywhere in the instructions where it suggests, requires, or otherwise recommends that all the methods are to be implemented. In fact, I do see that you will not be credited for extra work. Also, extra code that is unstable or buggy could lead to markdowns. But anyways, in the end its up to you to draw your conclusions about whether or not to implement them, and then write it in your design doc.
 
Philippe Maquet
Bartender
Posts: 1872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Min,
Where? I do not see anywhere in the instructions where it suggests, requires, or otherwise recommends that all the methods are to be implemented.

Instructions:
Your data access class must be called "Data.java", must be in a package called "suncertify.db", and must implement the following interface

Implementing an interface means implementiong its methods.
Regards,
Phil.
 
Anonymous
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Implementing an interface means implementiong its methods.

A class technically implements an interface even if all the methods throw UnsupportedOperationExceptions... The question is whether this is considered "implementing" or not.
Personally, I support Michael's point of view.
Regards,
Marcel
 
Min Huang
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, that's what I meant - implementing them but leaving them blank. I that people have passed by just leaving them blank. I believe Mark (Spritzler) passed w/o touching them. Those methods are just artifacts from an older assignment version.
 
Cleverson Schmidt
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What to do now
Leave them blank or throw an UnsupportedOperationException?
[ April 24, 2004: Message edited by: Cleverson Schmidt ]
 
Philippe Maquet
Bartender
Posts: 1872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Marcel:
A class technically implements an interface even if all the methods throw UnsupportedOperationExceptions... The question is whether this is considered "implementing" or not.
Personally, I support Michael's point of view.

Hence mine, I guess:
Michael:
I believe part of the assignment is to develop a (potential) fully working database server.


Min:
Yes, that's what I meant - implementing them but leaving them blank. I that people have passed by just leaving them blank.

In nearly one year spent on this forum, I didnd't see anyone, as far as I can remember, who decided to leave blank delete() and create(), or to "implement" them as optional operations (use of the UnsupportedOperationExceptions). Now if you *really* want to try it...
Min:
I believe Mark (Spritzler) passed w/o touching them. Those methods are just artifacts from an older assignment version.

Mark got the FBNS assignment, an old version indeed, and no useful comparison can be made with the new assignments as far as database access is concerned. AFAIK, FBNS provided an *existing* data class to be modified, while all new assignments provide an *interface* to be implemented.
Cleverson:
What to do now :confused
Leave them blank or throw an UnsupportedOperationException?

I'd choose the safe way: just implement them, making them fully workable.
Regards,
Phil.
[ April 25, 2004: Message edited by: Philippe Maquet ]
 
Cleverson Schmidt
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm convinced, I will implement all of them.
Thank you very much guys
Best Regards
Cleverson
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic