Evaluations
Staffware
This evaluation is based on Staffware Process Suite version 9.
Pattern |
Explanation |
Work Item Deadline |
|
| OCO-CWC-COM | Work items offered to group members are not necessarily withdrawn when a deadline expires but a compensating work item can be initiated. |
| ACA-CWC-COM | Work items allocated to a user are not necessarily withdrawn when a deadline expires but a compensating work item can be initiated. |
| OFF-CWC-COM | A withdraw action can be specified for a work item offered to a group when a deadline expires. |
| AFF-CWC-COM | A withdraw action can be specifed for a work item allocated to a user when a deadline expires. |
| SCE-CWC-COM | A work item in progress can be continued when its deadline expires. |
External Trigger |
|
| OCO-CWC-COM | An event step work item can be triggered by an external signal as a compensation activity. The current work item is unaffected. |
| ACA-CWC-COM | An event step work item can be triggered by an external signal as a compensation activity. The current work item is unaffected. |
| SCE-CWC-NIL | An event step work item can suspend until an external trigger is received. |
| SCE-CWC-COM | An event step work item can be triggered by an external signal as a compensation activity. The current work item is unaffected. |
WebSphere
This evaluation is based on WebSphere MQ Workflow version 3.4.
Pattern |
Explanation |
Work Item Deadline |
|
| OCO-CWC-NIL | Notification mechanisms are provided for overdue work items but the default action is only to advise nominated resources of deadline expires. No intervention occurs. |
| ACA-CWC-NIL | Notification mechanisms are provided for overdue work items but the default action is only to advise nominated resources of deadline expires. No intervention occurs. |
| SCE-CWC-NIL | Notification mechanisms are provided for overdue work items but the default action is only to advise nominated resources of deadline expires. No intervention occurs. |
FLOWer
This evaluation is based on FLOWer 3.1.
Pattern |
Explanation |
Work Item Deadline |
|
| AFC-CWC-NIL | Allocated work items can be automatically completed once a deadline is reached. |
| SFC-CWC-NIL | Work items in progress can be automatically completed once a deadline is reached. |
Constraint Violation |
|
| AFC-CWC-NIL | A sequential plan can be auto-completed when a specified condition evaluates to true. |
| SFC-CWC-NIL | A sequential plan can be auto-completed when a specified condition evaluates to true. |
| AFC-CWC-COM | A sequential plan can be automatically created when a specified condition evaluates to true. |
| SFC-CWC-COM | A sequential plan can be automatically created when a specified condition evaluates to true. |
COSA
This evaluation is based on COSA 5.1.
Pattern |
Explanation |
Work Item Failure |
|
| SRS-CWC-RBK | An activity can deal with a detected failure by rolling back work in progress and restarting the activity vian the COSA_activity_cancel function. |
Work Item Deadline |
|
| OCO-CWC-COM | A compensating activity can be triggered for an activity that has not reached a specified state by a nominated time. |
| ACA-CWC-COM | A compensating activity can be triggered for an activity that has not reached a specified state by a nominated time. |
| SCE-CWC-COM | A compensating activity can be triggered for an activity that has not reached a specified state by a nominated time. |
External Trigger |
|
| OCO-CWC-COM | A compensating activity can be initiated for an activity via an external trigger. |
| ACA-CWC-COM | A compensating activity can be initiated for an activity via an external trigger. |
| SCE-CWC-COM | A compensating activity can be initiated for an activity via an external trigger. |
iPlanet
This evaluation is based on Sun ONE iPlanet Integration Server 3.1.
Pattern |
Explanation |
Work Item Failure & Work Item Deadline |
|
OFF-CWC-NIL |
Outgoing router constructs from an activity provide a range of options for dealing with failures and deadline expiration including signalling to subsequent activities that the preceding activity completed successfully or failed, initiating alternative compensation tasks and allowing other activities in the case to continue or forcing them to terminate. |
XPDL
This evaluation is based on XPDL 2.0
Pattern |
Explanation |
Work Item Failure |
|
| SFF-CWC-COM | An activity can have Error, Cancel and Compensation triggers defined for it enabling it to respond to errors, cancellation and compensation requests which occur during execution. Once one of these is detected, the thread of control can be passed to an alternative compensation activity (or sequence of activities). The thread of control can be return to the normal execution sequence at a later stafe in the process once the required compensation activity has been completed. |
| SFF-CWC-NIL | An activity can have an empty set of compensation activities. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the compensation activity (or sequence of activities) is concluded with an end event node thus cancelling any other activity in the process that may currently be executing. |
| SFF-RCC-NIL | As for SFF-CWC-NIL except that the compensation is simply an event event node thus cancelling any other activity in the process that may currently be executing with undertaking any form of compensation. |
Work Item Deadline |
|
| SCE-CWC-COM | An activity can have a Deadline associated with it that specifies an alternative activity (or set of activities) that should be undertaken if a deadline is reached before the activity has completed. The ASYNCHR node results in the activity being continued and the alternative (deadline) activity sequence also being initiated. |
| SCE-CWC-NIL | The alternative activity sequence can be empty. |
| SFF-CWC-COM | As for SCE-CWC-COM except the SYNCHR node is specified resulting in the activity on which the deadline is specified being terminated and the alternative activity sequence being initiated. |
| SFF-CWC-NIL | As for SCE-CWC-NIL except the SYNCHR node. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the alternative activity sequence is concluded with an end event node thus cancelling any other activities in the process that may currently be executing. |
| SFF-RCC-NIL | As for SFF-CWC-NIL except that the compensation is simply an end event node thus cancelling any other activity in the process that may currently be executing without undertaking any form of compensation. |
External Trigger |
|
| SFF-CWC-COM | Message events can be specified for an activity which, when the required message is received, result in the activity being terminated and an alternative sequence of activities being initiated. |
| SFF-CWC-NIL | The alternative activity sequence for a message event can be empty. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the alternative activity sequence is concluded with an end event node thus cancelling any other activities in the process that may currently be executing. |
| SFF-RCC-NIL | As for SFF-CWC-NIL except that the compensation is simply an end event node thus cancelling any other activity in the process that may currently be executing without undertaking any form of compensation |
Constraint Violation |
|
| SFF-CWC-COM | Trigger rules can be specified for an activity which, when the specified trigger rule evaluates to true, result in the activity being terminated and an alterative sequence of activities being initiated. |
| SFF-CWC-NIL | The alternative activity sequence for a trigger rule can be empty. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the alternative activity sequence is concluded with an end event node thus cancelling any other activities in the process that may currently be executing. |
| SFF-RCC-NIL | As for SFF-CWC-NIL except that the compensation is simply an end event node thus cancelling any other activity in the process that may currently be executing without undertaking any form of compensation. |
BPEL
This evaluation is based on BPEL4WS version 1.1.
Patterns |
Explanation |
Work Item Failure |
|
| SFF-CWC-COM | An activity can have a fault handler specified for it that defines the actios to be undertaken should the activity fail. |
| SFF-CWC-NIL | The fault handler for an activity can be empty. |
| SFF-RCC-COM | A fault handler can compensate for the failed activity. The last action in the fault handler could be a <terminate> activity thus ending all activities in the current process instance. Alternatively, the fault handler could rethrow a detected fault to a higher level. Where it is thrown to the global scope, this could be used to terminate all other activities being executed in the process instance. |
| SFF-RCC-NIL | As for SFF-CWC-NIL except that the fault handler is simply a <terminate> activity. |
Work Item Deadline |
|
| SCE-CWC-COM | Alarm events can be specified for an activity which initiate a sequence of actions when a specified deadline is reached. These actions execute concurrently with the activity on when the alarm was raised. |
| SCE-CWC-NIL | The alarm event can have an empty set of actions associated with it. |
| SFF-CWC-COM | An alarm event can be associated with an activity which invokes a fault handler when a deadline is exceeded. When this occurs the activity is terminated and the fault handler initiates a sequence of compensating activities. |
| SFF-CWC-NIL | As for SFF-CWC-COM except that the fault handler is empty. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the last activity in the fault handler is a <terminate> activity which chancels all activities in the current process instance. |
| SFF-RCC-NIL | Similar to SFF-RCC-COM except that <terminate> is the only activity in the fault handler. |
External Trigger |
|
| SCE-CWC-COM | A message event handler can be specified for an activity which initiates a series of compensating activities when a nominated message is received. The activity which receives the message continues to execute. |
| SCE-CWC-NIL | As for SCE-COM-NIL except the message event handler can be empty. |
| SFF-CWC-COM | An activity can have a message event handler associated with it which initiates compensating activities when a nominated message is received. The last action of the message event handler is to invoke a fault handler which terminates the activity. |
| SFF-CWC-NIL | As for SFF-CWC-NIL except the only action of the message event handler is to invoke the fault handler hence no compensating activities are initiated. |
| SFF-RCC-COM | As for SFF-CWC-COM except the last action in the message event handler is a <terminate> |
| SFF-RCC-NIL | Similar to SFF-RCC-COM except that the only action in the message event handler is a <terminate>. |
BPMN
This evaluation is based on BPMN version 1.0.
Pattern |
Explanation |
Work Item Failure |
|
| SFF-CWC-COM | An activity can have an error, cancel or compensating event associated with it that terminates the activity and routes control to an exception flow of activities to resolve the issue detected. Other activities are unaffected by the event. |
| SFF-CWC-NIL | As for SFF-CWC-COM except that there are no compensating activities in the exception flow. |
| SFC-CWC-COM | As for SFF-CWC-COM except once the exception flow activities are completed, the thread of control is immediately routed to the activities immediately following the failed activity in the normal process flow. |
| SFC-CWC-NIL | As for SFC-CWC-NIL except that the exception flow does not contain any compensating activities. |
| SRS-CWC-COM | As for SFC-CWC-COM except that the exception flow routes the thread of control back to the beginning of the failed activity (i.e. it restarts it) once the compensating activities have been completed. |
| SRS-CWC-NIL | As for SRS-CWC-COM except there are no compensating activities in the exception flow. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the last node in the exception flow is an end event thus terminating all other active activities in the process instance. |
| SFF-RCC-NIL | As for SFF-RCC-COM except that the only node is the exception flow is an end event. |
Work Item Deadline |
|
| SFF-CWC-COM | An activity can have a timer event associated with it that terminates the activity and routes control to an exception flow of activities to manage the implications of the deadline expiration. Other activities are unaffected by the event. |
| SFF-CWC-NIL | As for SFF-CWC-COM except that there are no compensating activities in the exception flow. |
| SFC-CWC-COM | As for SFF-CWC-COM except once the exception flow activities are completed, the thread of control is immediately routed to the activities immediately flowing the failed activity in the normal process flow. |
| SFC-CWC-NIL | As for SFC-CWC-NIL except that the exception flow does not contain any compensating activities. |
| SRS-CWC-COM | As for SFC-CWC-COM except that the exception flow routes the thread of control back to the beginning of the failed activity (i.e. it restarts it) once the compensating activities have been completed. |
| SRS-CWC-NIL | As for SRS-CWC-COM except there are no compensating activities in the exception flow. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the last node in the exception flow is an end event thus terminating all other active activities in the process instance. |
| SFF-RCC-NIL | As for SFF-RCC-COM except that the only node in the exception flow is an end event. |
External Trigger |
|
| SFF-CWC-COM | An activity can have a message event associated with it have triggers when a specific message type is received by the activity. When this occurs, the activity is terminated and control is routed to an exception flow of activities to manage the implications of the trigger received. Other activities are unaffected by the event. |
| SFF-CWC-NIL | As for SFF-CWC-COM except that there are no compensating activites in the exception flow. |
| SFC-CWC-COM | As for SFF-CWC-COM except once the exception flow activities are completed, the thread of control is immediately routed to the activities immediately flowing the failed activity in the normal process flow. |
| SFC-CWC-NIL | As for SFC-CWC-NIL except that the exception flow does not contain any compensating activities. |
| SRS-CWC-COM | As for SFC-CWC-COM except that the exception flow routes the thread of control back to the beginning of the failed activity (i.e. it restarts it) once the compensating activities have been completed. |
| SRS-CWC-NIL | As for SRS-CWC-COM except there are no compensating activities in the exception flow. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the last node in the exception flow is an end event thus terminating all other active activities in the process instance. |
| SFF-RCC-NIL | As for SFF-RCC-COM except that the only node in the exception flow is an end event. |
Constraint Violation |
|
| SFF-CWC-COM | An activity can have a rule event associated with it that triggers when a specific set of specified conditions based on process data elements evaluate to true. When this occurs, the activity is terminated and control is routed to an exception flow of activities to manage the implications of the constraint violation. Other activities are unaffected by the event. |
| SFF-CWC-NIL | As for SFF-CWC-COM except that there are no compensating activities in the exception flow. |
| SFC-CWC-COM | As for SFF-CWC-COM except once the exception flow activities are completed, the thread of control is immediately routed to the activities immediately flowing the failed activity in the normal process flow. |
| SFC-CWC-NIL | As for SFC-CWC-NIL except that the exception flow does not contain any compensating activities. |
| SRS-CWC-COM | As for SFC-CWC-COM except that the exception flow routes the thread of control back to the beginning of the failed activity (i.e. it restarts it) once the compensating activities have been completed. |
| SRS-CWC-NIL | As for SRS-CWC-COM except there are no compensating activities in the exception flow. |
| SFF-RCC-COM | As for SFF-CWC-COM except that the last node in the exception flow is an end event thus terminating all other active activities in the process instance. |
| SFF-RCC-NIL | As for SFF-RCC-COM except that the only node in the exception flow is an end event. |
Previous - Bibliography