My previous post disappeared, I don't know if did something wrong or if its content didn't respect the privacy...
If a use case seems to lead to functional bugs, what the candidate is supposed to do?
- modify use case, and may be make assumptions (on business process, external system, etc...)
- lists potential bugs as risks and identify a mitigation strategy (I thought risks was just technical, not fonctional)
- make assumptions justifying the giving use case specifications.
- something else...
I hope I'm allowed to ask this. Let me know if I can't.
i think the best possible option is to make your design as flexible is to consider all possibilities and even if you have to make any assumption state those clearly. Just an example if you have to use a web service and you don't know exact interface, at least you could put all the methods which is possible. At least it gives the examiner a hint that you are thinking about other possibilities and you understand those possibilities also. This is my view.