Preparing part II. I've been thinking about the use-cases and sequence diagrams. The use cases show some alternative scenarios, but there are much more. Some of them are pretty obvious like:
- what if two customers book the same seat at the same time? When are seats locked?
My idea is to ignore all this scenarios in my sequence diagrams since I don't know FBN policy, and just design a sequence diagram that matches what the use-cases say + assumptions I made while designing class and components diagrams. Maybe I'll add some notes about the most relevant scenarios ommitted.
Do you share my point? Anyone succeded with this strategy?