"Subject" in a Use Case Diagram ?

[ebousse]

I am willing to re-create in Gaphor this example from the UML specification (page 643, section 18.1.5, UML 2.5.1):

I don't see how in Gaphor it is possible to draw the subject part of the diagram (here it is the ATMSystem box).

Maybe I am missing something?

thanks in advance!

[danyeaw]

Hi @ebousse The subject would be a class in UML. Is it working to add a class to the Use Case diagram?

[ebousse]

Yes, if I remember right a "subject" in a UC diagram can be any kind of UML classifier, typically a class or a component (often with the «subsystem» stereotype).

Here is what happens when trying to put a class and a package in a UC diagram in Gaphor:

The class is displayed as if it was inside a class diagram, and the package is displayed as if it was in a package diagram. I could not find a way to make them appear as an open box for the UC diagram.

[ebousse]

I just found out that in Gaphor it's possible to drag a UC inside a class or package, to make it "open" itself.

Here is the result:

Interesting, but still quite different from the expected graphical syntax − especially regarding the component, which keeps its name in the middle!

[amolenaar]

especially regarding the component, which keeps its name in the middle!

This has been fixed in 2.12 :)

We have some documentation on working with stereotypes.

[ebousse]

This has been fixed in 2.12 :)

great!

Is there a plan to support the UML official syntax regarding the drawing of a subject within a use case diagram? (ie. as in the example shown in my first message)

We have some documentation on working with stereotypes.

Good to know :) thanks!

And in addition to the possibility to define new stereotypes, are "default" UML stereotypes already defined within Gaphor? (eg. SubSystem)

[danyeaw]

@ebousse I agree that adding at least some of the stereotypes that are available in the UML Standard Profile makes sense. Would you mind submitting an enhancement request as an issue?

[amolenaar]

We can add a few of those to the UML template. It would also be a nice showcase for our stereotype support.