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: URLy User Interface Requirements

 
Matthew Jarvie
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Group,
My spec states the following requirements for the UI:
->It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
->It must present search results in a JTable.
->It must allow the user to book a selected record, updating the database file accordingly.
I don't see anything regarding allowing the user to add/remove records from the database through the UI. It would be dead simple to add this functionality (thanks to the already implemented methods in DBAccess), but I was just wondering if anyone else had chosen to count this as "future functionality" and leave it at that? And passed..
Many thanks for your help,
-Matthew
 
Nathaniel Stoddard
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I did URLyBird and didn't touch adding or deleting anything - and passed. Remember, the specs specifically say that doing extra won't get you extra points. So, try and keep a lid on it.
 
George Marinkovich
Ranch Hand
Posts: 619
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Matthew,
Originally posted by Matthew Jarvie:

My spec states the following requirements for the UI:
->It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
->It must present search results in a JTable.
->It must allow the user to book a selected record, updating the database file accordingly.

These are the only database operations you are required to support in the UI.

I don't see anything regarding allowing the user to add/remove records from the database through the UI. It would be dead simple to add this functionality (thanks to the already implemented methods in DBAccess), but I was just wondering if anyone else had chosen to count this as "future functionality" and leave it at that? And passed..

Yes and yes.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic