This diagram is dedicated to a Participant modeling including its internal structure and relationships to Service Architectures.
The elements required for modeling the internal structure of the Participant should be dragged and dropped from the model browser. This includes dragging and dropping of other Participants and ServiceArchitectures. This operation will create parts for Participant including ports and required collaboration use for ServiceArchitectures. Parts have to be typed with Participants, Ports with ServiceInterfaces, CollaborationUse with ServiceArchitecture.
Table 9 Participant Diagram Palette
Command | Description |
---|---|
![]() |
Creates a Class with SoaML.Participant stereotype Stereotype representation: “text” SmartAction:
![]() ![]() ![]() |
![]() |
Creates a port with SoaML.Service stereotype on Participant or Part Stereotype representation: “text” |
![]() |
Creates a port with SoaML.Request stereotype on Participant or Part Stereotype representation: “text” |
![]() |
Creates a part inside of Participant Restriction:
|
![]() |
Creates a Collaboration Use inside of Participant Restriction:
|
![]() |
Creates a “generalization” link between two Participants. |
![]() |
Creates a “Provide Interface” link on a Port. |
![]() |
Creates a “Required Interface” link on a Port. |
![]() |
Creates a “Connector” between two Ports. |
![]() |
Creates a “Delegate” link between external port and a port belonging to a Part. |
![]() |
Creates a “Binding” link between Collaboration Uses representing Service Architectures and Parts representing Participants |
![]() |
Creates a traceability between two model elements |
![]() |
Creates a Note for a model element |
Figure 23 Participant Diagram Example
This is the major use case extracted from the SoaML specification and implemented in the SoaML Modelio module:
Figure 24 Participant Modeling Use Case
In the above Use Case a Service Architecture is dragged and dropped into the Participant.
Figure 25 Conjugate Service Interface Modeling Use Case