Interpretation of business analysis model elements by Business-Process-to-Service-Model transformations

The UML elements that the Business-Process-to-Service-Model transformation generates depends on the objects in the source UML model, which is also called the specification model. The specification model is a UML realization of a WebSphere® Business Modeler business process model, and is created when you import a WebSphere Business Modeler model into your workspace.

The stereotype that the transformation applies to the generated elements depends on the target profile that you select in a Business-Process-to-Service-Model transformation configuration.

Important: The Software Services profile is deprecated and a profile called the Services Modeling (SoaML) profile is available for modeling services. For information about migrating from the Software Services profile to the Services Modeling (SoaML) profile, see the related link at the end of this topic. For information about how stereotypes in the Software Services profile map to stereotypes in the Services Modeling (SoaML) profile, see the related link at the end of this topic.

For more information about the Software Services profile, also called the UML 2.0 Profile for Software Services, see the article entitled UML 2.0 Profile for Software Services on the IBM® developerWorks® Web site.

The following table lists the specification model elements that the transformation supports, and the corresponding UML output that the transformation creates.

Specification model element Transformation output (UML high-level architectural model)
Model or package The transformation creates a UML model or package with the same name, containment structure for nested packages, and collaborations. Nested packages or collaborations might also contain UML activities.

Classes and data types, and activity elements are not transformed. When necessary, the generated model creates usage relationships that correspond to these elements in the source model.

The target profile that you select in the transformation configuration determines whether the transformation applies a stereotype to the generated model or package:
  • If you select the Services Modeling (SoaML) profile, the transformation does not apply a stereotype
  • If you select the Software Services profile, the transformation applies the «serviceModel» stereotype
Collaboration The transformation creates a UML component that has the same name and containment structure as the source collaboration element.
The target profile that you select in the transformation configuration determines which stereotype the transformation applies to the generated component:
  • If you select the Services Modeling (SoaML) profile, the transformation applies the «Participant» stereotype
  • If you select the Software Services profile, the transformation applies the «serviceProvider» stereotype

The transformation creates a CollaborationUse element for each component.

The type of the CollaborationUse element is set to the collaboration element in the source model.

Each port in the generated component binds to a respective role in the collaboration, through the CollaborationUse element. For details about the ports that the transformation creates, see the Collaboration role::type row below.
Collaboration role The transformation creates a UML port on the component. The generated port has the same name as the role in the source model.

Each port binds to a role by using a collaboration use relationship.

Collaboration role::type If the role::type property specifies the same interface that is realized by the collaboration element, the role::type property is set to an interface that is provided by the port. The type of the port is also set to that interface.

All other role::type properties are set to required interfaces.

For all ports that are associated with required interfaces, the transformation generates a UML class that has a usage relationship with the interface that the source model defines. The transformation sets the port type to the generated UML class. The name of the generated UML class is the same as the interface name in the source model, with a suffix of Protocol.

Consider the following example: If a class defines a usage relationship to one or more interfaces, and if the class is set to the value of port:type property, the port shows all the interfaces in the list of required interfaces.

Interface The target profile that you select in the transformation configuration determines whether the transformation applies a stereotype to the generated Java interface:
  • If you select the Services Modeling (SoaML) profile, the transformation applies the «ServiceInterface» stereotype
  • If you select the Software Services profile, the transformation applies the «ServiceSpecification» stereotype

Feedback