Chapter 7 Working with Business Process Models
The following BPM model checks are made on flows:
| Check | Description and Correction |
|---|---|
| Flow without source or destination | A flow must have a source and a destination object.
Manual correction: Assign a source or a destination to the flow Automatic correction: None |
| Flow undefined message format | A flow should have a defined message format or the message format set to <None>.
Manual correction: Define the message format for the flow or delete it Automatic correction: None |
| Flow incoherent message format | The message format of a flow coming out of a composite process (child process) must also exist on the flow going to the end inside the child process. The message format of a flow coming in a composite process must also exist on the flow going out from the start inside the child process.
Manual correction: Add any missing message formats to the appropriate flows of the decomposed processes Automatic correction: None |
| Invalid event condition | Outgoing flows from start, decision and synchronization objects cannot have fault, compensation, or signal event. Besides, outgoing flows from synchronization objects cannot have message type events. Also, a decision object can only have flows with Message, Signal or Timer event. You can mix Message and Timer events or Signal and Timer events on the same decision.
Manual correction: Removes the inappropriate Event condition on the flow or change the source extremity of the flow Automatic correction: Removes the inappropriate Event condition on the flow |
| Invalid exception flow destination | A flow with Exception stereotype must target a process that is implemented by an operation and whose Action Type is Receive Request.
Manual correction: Change the flow stereotype or select a process that is implemented by an operation and whose Action Type is Receive Request Automatic correction: None |
| Copyright (C) 2008. Sybase Inc. All rights reserved. |
| |