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

Restricting user,updating the user view/control

 
Inuka Vincit
Ranch Hand
Posts: 175
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So after readin a question from a fellow user I was thinking of a more general case that applies to all, of data violations. Please feel free to add to my list. Are these important... or am I realy overcomplicating things.

1. User is breaking a real world contract not specified in the requirements. Double booking rooms for exmaple.
2. The user is attempting to update a record that an other user has justupdated. Let the user know about this case?
2. The user is looking at search results and meanwhile the database has been updated. Do we need to update the user view?

The requirements imply that the user interface is just a simple view into a database. Ofcourse it also says that it should allow for easy extensability as well. I could keep it simple and still meet the requirements(I think).

Any ideas from you folks
 
peter wooster
Ranch Hand
Posts: 1033
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Inuka Vincit:
So after readin a question from a fellow user I was thinking of a more general case that applies to all, of data violations. Please feel free to add to my list. Are these important... or am I realy overcomplicating things.

1. User is breaking a real world contract not specified in the requirements. Double booking rooms for exmaple.
2. The user is attempting to update a record that an other user has justupdated. Let the user know about this case?
2. The user is looking at search results and meanwhile the database has been updated. Do we need to update the user view?

The requirements imply that the user interface is just a simple view into a database. Ofcourse it also says that it should allow for easy extensability as well. I could keep it simple and still meet the requirements(I think).

Any ideas from you folks


See

Last one gets... for solutions to this. There is no requirement to keep the table up to date with changes made by other clients, but in my opinion you shouldn't allow the user to make changes based on stale data.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic