Presentation is loading. Please wait.

Presentation is loading. Please wait.

AH-3 common errors Not using a separate pool for the client (consultant submitting his/her expense report) Consequence is no start event for the “main.

Similar presentations


Presentation on theme: "AH-3 common errors Not using a separate pool for the client (consultant submitting his/her expense report) Consequence is no start event for the “main."— Presentation transcript:

1 AH-3 common errors Not using a separate pool for the client (consultant submitting his/her expense report) Consequence is no start event for the “main process” Flows, not messages between client and process Not naming the pool as a role, but instead as a person’s name Not labeling message flows (if/when pool used) Using separate send/receive tasks for flows within a process (between swimlanes) Not needed; the flow itself takes care of this Having multiple, not ME/CE, flows out of an X-Or gateway Having activities with no outbound flow Where does that flow sequence go next? All flows must have an “End” event! Not doing processing before an X-OR gateway I.e. make decision without first checking if (say) expenses valid


Download ppt "AH-3 common errors Not using a separate pool for the client (consultant submitting his/her expense report) Consequence is no start event for the “main."

Similar presentations


Ads by Google