search

eclipsesource / papyrus-umllight

Eclipse Public License 2.0
4 stars 2 forks source link

Create simplified UML Use Case diagram type and palette #3

Closed planger closed 5 years ago

planger commented 5 years ago

The UML Use Case diagram shall include the UML concepts listed below. This includes adapting the palette.

cdamus commented 5 years ago

As mentioned on #9, if we're going to have the Extend relationship in the palette, then so too must we have ExtensionPoint because a the Extend has to reference at least one point at which the extending use case is inserted.

Update 24 Oct. 15:40 EDT

I see in testing that the Extend connection tool creates an extension point in the target UseCase implicitly, which is helpful. And also, neither in the UML Light use case diagram nor in Papyrus UML does the palette tool for explicit creation of an extension point actually work (the use case shapes in the diagram don't permit creation of anything within them). So, perhaps best to leave off the ExtensionPoint tool, after all.

cdamus commented 5 years ago

@planger In the Papyrus UML use case diagram, the Subject tool creates a Component. We seem to be excluding components from the UML Light dialect, so I would suggest that this tool should create a Class in our context. Thoughts?

planger commented 5 years ago

@planger In the Papyrus UML use case diagram, the Subject tool creates a Component. We seem to be excluding components from the UML Light dialect, so I would suggest that this tool should create a Class in our context. Thoughts?

@cdamus Yeah, good idea! I think that's fair.

cdamus commented 5 years ago

This is fixed with Pull #27.