Use case diagram basic and alternate flows for EAI

[dirkme]

Hi, I am attempting an EAI use case diagram.
My question is how to model basic and alternative flows if I have a message sent from system A, to EAI, to system B or C. System A publishes a message, and based on its content EAI routes to either B or C.
2 questions:
1. Would this be modelled as two seperate basic paths?
2. Would exceptions be modelled as alternate flows?

Thanks  

[jfzouain]

If I understand you correctly, this would be modeled as a basic path with a business rule in each flow.

Basic Path
1. System A sends a message
2. If message has rule x  is routed to System B
3. If message has rule y  is routed to System C

You can add an Activity Diagarm to this Use Case with a fork to route the message.

Hope it helps, but remember there are different ways to create this.
This is just one way.

[dirkme]

Alternatively one can have multiple use cases "inheriting" from the base use case using the <<extends>> relationship. Would this make more sense? Then one would have seperate sequence diagrams for each use case. Any ideas?