• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Reqs on DataBase vs. GUI

 
Tomas Carlstrom
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
In my assignment there are more requirements on the Database interface than for the GUI. The end user must only be able to search and book records via the GUI, but the implementation of the Database interface must also support creation/deletion of records. Is it up to me to decide how to handle the unclear requirement? It would make no sense to write code which cannot be used by the end user anyway. Or if you take the other stand it would make little sense to have an application for a business in which you can't add more records. This application would not be a success. Is this what is meant by that I should motivate my decisions on unclear requirements or is the poor GUI just a way to limit the scope of the GUI part?

Any help is appreciated.

Tomas
 
rinke hoekstra
Ranch Hand
Posts: 152
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I would suppose that apparently another application is responsible for adding/ deleting recs to the gui. It may (or may not) use your interface.

Yes, I think the gui is poor, and yes, I think it is so in order to limit the scope.

However, the instructions also say that the gui must be made with expectance of future extensions. So maybe these are the delete/create implementations???

Anyway, you must implement those methods, even though the gui doesn't use them.

Hope it helps, Rinke
 
Tomas Carlstrom
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your help. I was thinking this is probably the case as the assignment says "must implement this interface". So this unclear function is not a candidate for my own judgement and motivation to descope.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic