Participant Diagram

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.

Palette

Table 9 Participant Diagram Palette

Command Description
Participant Creates a Class with SoaML.Participant stereotype
Stereotype representation: “text” SmartAction:
  1. If clicked inside of exiting Participant, a new Part is created typed by a newly created additional Participant, including ports.
  2. If Participant A is dragged and dropped inside of an existing participant, a part is created typed by Participant A
  3. If Service Architecture A is dragged and dropped inside of an existing participant, a Collaboration Use is created typed by Service Architecture A
Restrictions: only Participants and Service Architecture typed instances are possible to create inside.
Service Creates a port with SoaML.Service stereotype on Participant or Part
Stereotype representation: “text”
Request Creates a port with SoaML.Request stereotype on Participant or Part
Stereotype representation: “text”
Instance Creates a part inside of Participant
Restriction:
  1. It is impossible to model instance outside of a Participant.
  2. Instance should be typed with a Participant
CollaborationUse Creates a Collaboration Use inside of Participant
Restriction:
  1. It is impossible to a Collaboration Use outside of a Participant.
  2. Collaboration Use should be typed with Service Architecture
“Generalization” link Creates a “generalization” link between two Participants.
“Provided Interface” link Creates a “Provide Interface” link on a Port.
“Required Interface” link Creates a “Required Interface” link on a Port.
“Connector” link Creates a “Connector” between two Ports.
“Delegate” link Creates a “Delegate” link between external port and a port belonging to a Part.
“Binding” link Creates a “Binding” link between Collaboration Uses representing Service Architectures and Parts representing Participants
Traceability link Creates a traceability between two model elements
Note Creates a Note for a model element


Figure 23 Participant Diagram Example

Use Cases

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

image049.png (553 Bytes) admin admin, 25 June 2015 10:04

image020.png (351 Bytes) admin admin, 25 June 2015 10:04

image076.png (45.5 KB) admin admin, 25 June 2015 10:04

image051.png (219 Bytes) admin admin, 25 June 2015 10:04

image078.png (4.46 KB) admin admin, 25 June 2015 10:04

image072.png (252 Bytes) admin admin, 25 June 2015 10:04

image009.png (333 Bytes) admin admin, 25 June 2015 10:04

image069.png (3.36 KB) admin admin, 25 June 2015 10:04

image071.png (8.44 KB) admin admin, 25 June 2015 10:04

image037.png (557 Bytes) admin admin, 25 June 2015 10:04

image032.png (1015 Bytes) admin admin, 25 June 2015 10:04

image073.png (754 Bytes) admin admin, 25 June 2015 10:04

image077.png (5.77 KB) admin admin, 25 June 2015 10:04

image070.png (4.92 KB) admin admin, 25 June 2015 10:04

image068.png (1.47 KB) admin admin, 25 June 2015 10:04

image075.png (604 Bytes) admin admin, 25 June 2015 10:04

image036.png (640 Bytes) admin admin, 25 June 2015 10:05

image074.png (651 Bytes) admin admin, 25 June 2015 10:05

image021.png (327 Bytes) admin admin, 25 June 2015 10:05