Interpretation of business process model elements by BPMN-to-Service-Model transformations

This content applies to version 7.5.4 or later. The service model, or UML elements, that the transformation generates depends on the elements of the source process model and their characteristics.

XSD data types

The transformation does not transform the XSD data types into UML elements. All the referenced XSD data types in the process model are referenced as XSD visualizer objects in the generated UML model.

Generation of UML elements

If the Business Process Modeling Notation (BPMN) model to transform does not contain implementation details such as service interfaces and task details, the transformation cannot generate a complete service model.

The following table lists how the transformation transforms business process model elements into UML elements.

BPMN process model element UML element
Process
  • Service component, also called a participant component or service participant component, with the following characteristics:
    • Has the «Participant» stereotype applied
    • Is generated in the package that contains the BPMN definitions
    • Name is derived from the Process::name property
    • Contains an opaque behavior that describes the implementation
  • Owned «Link» comment

    The transformation sets the Comment::body property to the BPMN process URI (BPMN model resource URI#ProcessRef).

Definitions
  • Package in the root package of the target model
    • The package name is derived from the name of the source model
Interface and its operations
  • Interface generated in the package that is associated with the BPMN model name in the source model
    • The interface name is derived from the BPMN Interface::name property
Operations in an interface
  • Corresponding operation in the corresponding interface
    • The operation name is derived from the name of the BPMN operation
Process::supportedInterfaces
  • For each generated interface, the transformation generates a «ServicePoint» port in the «Participant» component
    • The transformation adds each generated interface to the list of provided interfaces
ServiceTask::Operation
  • Port that has the following characteristics:
    • Has a default name of portn
    • Is generated in the «Participant» component of the associated interface, where the associated interface contains the operation
    • The generated UML interface, which is generated from the BPMN interface that contains the ServiceTask::Operation, is added to the list of required interfaces of the port
  • Class that defines a usages relationship to the generated interface. By default, the name of the generated class is Classn.
Operation messages
  • Visual representation of an XSD object by using the Message::StructureRefStructure property in the source model
    Note: The structure must have a valid item definition that contains a valid XSD OName.
  • Input (Operation::inMessage) and output (Operation::outMessage) parameters in the corresponding UML interface. Parameter names are derived from the corresponding Message::name property in the source model

    Each parameter type is set to the URI of the visual representation of the XSD object.


Feedback