4 main use cases description only states customer not TA even though in UC diagram they have shown both TA/Customer using the same use case.
I feel some UCs should have some alternative flows for TA since I feel TA will have to do something more to fulfill the basic requirements like search customer (Unless TA is just acting like customer on swing side where one swing app will be analogous to web session and TA will not be able to handle multiple customers in one shot.)
What would be the safe approach.
1. Should I assume that same UC flow as given in assgn will be used by TA ?I feel this will be a crude but easy way. 2. Add alternative flow to use case to make TA more sophisticated.Not sure if this violates requirements.
posted 10 years ago
Ajai, I would suggest go with your first option and document it.