How do I address the "include" relationship in the use case diagram (Part 2)

[wang xf]

There are 5 use cases in the diagram. The "Check Inventory Availability" use case include the "Enter Request" use case. like this below:

"Check Inventory Availability" --- <<include>>------> "Enter Request".

I will draw the sequence diagram for these two use case separately. Do I need to address this kind of "include" relationship in the sequence diagram. If yes, how do I do in the sequence diagram?

[Jeanne Boyarsky]

Wang,
I actually just did it as making one use case a pre-requisite for the other in my sequence diagram.

[wang xf]

Jeanne Boyarsky wrote:Wang,
I actually just did it as making one use case a pre-requisite for the other in my sequence diagram.

Hi Jeanne,

thanks.

But the use case "Enter Request" is independent of the use case "Check Inventory Availability". It does not really need to have the pre-requisite to start it.

Correct me if I am wrong.

[Rajiv Shr]

Wang,

You can use the Interaction Occurence element ("ref" element) to include one sequence diagram into another. This way you can have separate diagrams for 2 use cases, and include one in the other.

More details here - http://www.ibm.com/developerworks/rational/library/3101.html
Refer to this section in the link above - "Referencing another sequence diagram"

- Rajiv

[Jeanne Boyarsky]

wang xf wrote:But the use case "Enter Request" is independent of the use case "Check Inventory Availability". It does not really need to have the pre-requisite to start it.

Correct me if I am wrong.

Maybe I misunderstood. I thought you were saying that you wanted to include it first.