The collaboration specifies who the members are, what they are answerable for, and the way they are expected to work together. The collaboration roles (properties of the collaboration) are derived from the function resources assigned to tasks in the course of model. The role names are the identical as the primary required role useful resource for any task in the process.
However, service specification collaborations derived from a WBM business course of mannequin can be handled as patterns and instantiated utilizing totally different CollaborationUses. Alternatively, these collaborations can be transformed into contract templates to mannequin rich business patterns. The package deal construction of the UML2 business providers model proven in Figure 8 is exactly the identical because the catalog construction in WBM. This view in the RSA Model Explorer is similar to the WBM Project Tree view.
You can also create RequisitePro links to WBM mannequin components from an RSA model. You can create URL comments and connect them to parts in the business providers model to offer handy navigation to supplemental paperwork describing the business requirements. The design mannequin must be a separate mannequin from the business process mannequin for a few important reasons. The first is to maintain the implementation completely separate from the specification.
The invocation of a task is represented by a CallOperationAction. The CallOperationAction has an extra target InputPin whose name is the name of the position useful resource assigned to the task in the process mannequin, and whose sort is the Interface similar to that position resource. The operation property of the CallOperationAction is the corresponding operation of the function interface. The CallOperationAction can also be positioned in an ActivityPartition whose name is identical because the role name assigned to the duty, and whose Represents property is the function Interface.
- The business service specification provides another view of the business course of that also realizes the identical business use instances.
- The Business Services Modeling formalizes the relationship between business operational necessities and their realizations.
- This might help transition business course of fashions into business providers models that enable more flexible implementations that fit better with SOA runtime platforms.
The motion has enter and output pins for every of its parameters, and a further target enter pin known as claimProcessor of sort ClaimProcessor, the function responsible for the task. The action is placed in an exercise partition whose name is claimProcessor, and whose Represents property is the ClaimProcessor interface. Each business course of within the WBM model is viewed as a Collaboration with the identical name in UML2, as proven in Figure eleven for the Administer Claim course of. This collaboration represents the business service specification or contract that specifies what implementers must do in order to meet the business necessities.
The business item templates in WBM are viewed as superclasses within the BSM as a result of they symbolize shared properties. In Figure 10, the DataStructure Template is the superclass of both ClaimContainer and ClaimFolder, and represents properties which are widespread to each subclasses. Templates have a special meaning in UML2 and can be used to seize instantiatable patterns.
This helps present who’s answerable for the action in the realization contract’s activity. For example, the task Continue Claim Verification in the Administer Claim process turns into a CallOperationAction whose name is Continue Claim Verification.
Using WBM and RSA or RSM requires WBIM model 18.104.22.168 or later, RSM or RSA version 6.0.zero.1 or later (6.zero.1.1 is most well-liked). Use IBM® Rational® Product Updater (RPU) to install and apply any required updates and options.
The role kind is the interface comparable to the function as described under. The collaboration position represents the usage of a service provider enjoying a role in a specific collaboration to realize some result. The kind of the collaboration role specifies what obligations that service supplier has to offer in order to play the role. The collaboration position kind is commonly an Interface whose operations are the specifications for the function’s responsibilities. But in RSA, you possibly can create a category diagram to indicate the classes and their superclasses.