2
TIBCO Business Studio™ is a trademark o TIBCO So tware Inc. in the United States and/or other countries. The BPMN logo is a trademark or registered trademark o the Object Management Group, Inc. in the United States and other countries. Copyright © 2004-2008 TIBCO Sotware Inc. ALL RIGHTS RESERVED. Events An Event in a process is something that happens that aects the sequence or timing o activities in a process, or example the receipt o a message. There are three main types o Event: Start, Intermediate and End. Gateways Gateways are a control mechanism or the Sequence Flow in the process. Gateways are used or branching, merging, orking and joining as well as or conditional decisions. No specic trigger or the event (or example, to start the process as a sub-process). Message is sent to start the process, resume fow or at the end o the process. Event is triggered at a specic date/time or at a regular interval (time cycle). Ends a sub-process with an error. On a task boundary, either catches the specied error or any error i no specic error is specied. Ends a transactional sub-process. On a task boundary, catches the cancel event thrown rom within the sub-process. Either throws or catches a call or compen- sation. Used to process compensating activities or previously executed tasks. Triggered based on the evaluation o conditions. Creates a “go to” or “o page connector” to break up a process or better legibility. Broadcasts or catches signals. Indicates that one o several possible triggers are to be thrown or caught. Ends the process and all activities within without compensation or error handling. A Data Object is used or inormational purposes to show how a document or other data relates to the Process. It may be associated with fows or fow-related objects. Groups are used to indicate a relationship between elements o a Process by enclosing them in a dashed line. Text Annotations explain or clariy the Process. They may be associ- ated with fow or fow-related objects. A Pool is used as a container or partitioning Processes in ways that make sense or your business. A lane is a subdivision o a Pool. Business Process Modeling Notation 1.2 The basic orm o sequence fow where no conditions apply. Denes a conditional process fow between objects. The deault fow o process i all other conditions are alse. User Tasks are those that require human interaction with a sotware application. Manual Tasks are those that are completed by a person without using sotware. Service Tasks complete without human interaction (or example, an automatic email notication or a web service). Script Tasks contain a set o instructions to execute. Send Tasks are used to send messages to a system or person outside o the Process (oten using a web service). Receive Tasks are used to wait or a message rom a system or person outside o the Process (oten using a web service). Reerence Tasks reer to another Task and prevent you rom having to duplicate the same Task several times in a Process. One output Sequence Flow is chosen based on expressions using process data. One output Sequence Flow is chosen based upon an external event (or example, a JMS message). Each output Sequence Flow is independently evaluated according to an expression. This means that anywhere rom zero to the maximum output Sequence Flows can be taken. A Complex Gateway is used to ork or merge depending on complex criteria. A Parallel Gateway is used to ork or merge several parallel paths (synchronization). None Catch Throw Message Timer Error Cancel Compensation Conditional Signal Multiple Terminate Link St art Interme di ate End Description Event Type Task A Task represents work that a company or organization perorms using business processes. Task T ype Description Gateway Description Artifacts Artiacts are used to make processes easier to ollow. Connections Connections join objects in the diagram. Sequence Flow indicates the fow o the Process between Tasks, Gateways, and Events. Exclusive XOR Data Exclusive XOR Event OR Complex Parallel Pool/Lane Sequence Fl ow De sc ri pt i on Uncontrolled Flow Conditional Flow Default Flow Artifact Description Data Object Group Text Annotation Indicates the fow o messages between objects in separate Pools or between Pools. Connects fow-related objects with non-fow related objects to make a Process more readable. Also used or speciying a compensation Task or a compensation Event on a Task boundary. Message Flow Association Process that is ully contained in the parent Process. Call a reusable Sub-Process that is dened outside o the Process. TIBCO Business Studio TM GANYMEDE
