UML Profile for BPMN 2 Processes Conrad Bock DPG, MSID May 4, - PowerPoint PPT Presentation

UML Profile for BPMN 2 Processes Conrad Bock DPG, MSID May 4, 2011 1

OMG Model Architecture Diagram    Graphics: Domain terms: What happens: – Circles – Lathes, Feeders – Geometry changed. – Lines – Drying, Shaping – Pieces mounted onto machine. – Rectangles – Water removed. Standardized as Standardized as    Concrete syntax Abstract syntax Semantics 2

Enterprise Workflow (No Models) Real world enterprise observing affecting communicating about  People communicating with each other about the real world enterprise. – Using computers without modeling (beyond typical office suites). 3

Enterprise Workflow (Paper or Proprietary Electronic) BPMN BPMN Semantics Semantics BPMN BPMN Notation Notation (Concrete (Concrete Syntax) Syntax)  Using printed graphical models. – Or proprietary electronic exchange – BPMN 1.x 4

Enterprise Workflow (Standard Electronic) BPMN BPMN Semantics Semantics BPMN BPMN Notation Notation (Concrete (Concrete Syntax) Syntax) Metamodel / XSD Metamodel / XSD (Abstract syntax) (Abstract syntax) Interchange file <?xml version="1.0" encoding="UTF-8"?> Interchange file <?xml version="1.0" encoding="UTF-8"?> <definitions id="def" <definitions id="def" targetNamespace="http://www.example.org/Proce targetNamespace="http://www.example.org/Proce typeLanguage="http://www.w3.org/2001/XMLSche typeLanguage="http://www.w3.org/2001/XMLSche (instances xsi:schemaLocation="http://www.omg.org/bpmn20 (instances xsi:schemaLocation="http://www.omg.org/bpmn20 <dataPath>tns:nextTopicId</dataPath> <dataPath>tns:nextTopicId</dataPath> </correlationPropertyBinding> </correlationPropertyBinding> </correlationSubscription> of MM / XSD) Network </correlationSubscription> of MM / XSD) </process> </process> </definitions> </definitions>  Graphics translated to domain terminology. 5

Automation Workflow BPMN Semantics BPMN Notation (Concrete Syntax) Metamodel / XSD (Abstract syntax) Workflow or execution / Interchange file automation engine <?xml version="1.0" encoding="UTF-8"?> <definitions id="def" targetNamespace="http://www.example.org/Proce typeLanguage="http://www.w3.org/2001/XMLSche (instances xsi:schemaLocation="http://www.omg.org/bpmn20 <dataPath>tns:nextTopicId</dataPath> </correlationPropertyBinding> BPMN of MM / XSD) </correlationSubscription> </process> </definitions> Semantics  Machines directly affecting enterprise. 6

Equivalent Semantics BPMN Notation (Concrete Syntax) Instances of BPMN 2 Instances of the UML / SysML MM / XSD MM with profile applied. UML / SysML BPMN semantics semantics adapted for BPMN  Enterprise works the same regardless of 7 metamodel.

OMG Requirements  Mapping between BPMN 2 semantics and the profiled UML / SyML semantics.  XSLT and QVT transforms between BPMN and profiled UML interchange formats (abstract syntax).  Scope: – Internal enterprise processes. – Interactions between enterprises. 8

BPMN Processes Send Process Invoice Payment Receive Close Order Order Fill Deliver Order Order  Usually internal to enterprises. 9

BPMN Collaborations Credit Agency Participant Credit Credit Response Request Seller Evaluate Process Credit Search Internal Records Message flow Order Customer Response Order Buyer  Collaborations show message flows between participants. 10

BPMN Conversations Buyer Requesting Handling Quote Order Order Seller Order Response Request Shipping Shipping Request Confirmation Quote Quote Request Shipping Order Shipper  Conversations group message flows. 11

BPMN Conversations Negotiate Order Factory Supplier Schedule Plan Delivery Shipment Consignee Plan Shipment Choose Consolidator Shipper Pickup Location  Collaborations can show only conversations – No processes or message flow. – Informally called a “conversation diagram”. 12

UML / SysML Activities Send Process Invoice Payment Receive Close Order Order Fill Deliver Order Order  Very similar to BPMN processes, but some notational and semantic differences. 13

Activities ≠ BPMN Collaborations Back Office «external» Send Process Invoice Payment Receive Close Factory Order Order Fill Deliver Order Order  Activities model a single process. – Not interactions between processes. – Same for BPMN processes. 14

UML Collaborations Collaboration Uses Negotiate Order Collaboration Role Factory Supplier Plan Schedule Consignee Delivery Shipment Plan Shipment Choose Consolidator Shipper Pickup Location  Similar to conversation-only BPMN Collaboration.  Does not have notation for activities inside collaboration roles. – But the UML metamodel supports roles referring to activities, so the profile can support BPMN notation. 15

BPMN Processes in Profile  Stereotypes introduced generally, then restricted. – Process stereotype applies to UML Activity, gobal task stereotypes to UML OpaqueBehavior.  Semantic constraint: – isClosed prevents actions taken that are not in the model.  Application constraints: BPMN specifies how the various global tasks are to be used. 16 – Affect modeler, not language semantics.

BPMN Activities in Profile  Syntactic extension: – BPMN supports properties on activities. – Profile extends UML actions with classes.  Semantic constraint: – Properties of AdHocProcesses constrain execution of UML Activities that do not have flows between actions.  17 Renaming: UML Image => BPMN Rendering

BPMN Activities in Profile Process Payment Close Order will happen Close twice in BPMN, once in UML Order Deliver Order  Semantic modification: – BPMN normally starts activities when one incoming sequence flow provides input. – UML normally starts actions when all incoming control flows provide input. – BPMNActivity stereotype modifies UML 18 semantics for the models it is applied to.

BPMN Metamodel Navigation «metaclass» «metaclass» Process Activity ownedAttribute flowElements properties edge node «metaclass» «metaclass» «metaclass» «metaclass» «metaclass» FlowElement BPMN::Property ActivityNode ActivityEdge UML::Property «stereotype» Process / flowElements / properties  Stereotypes have properties for BPMN derived from UML properties.  Can navigate a profiled UML model as if it were a BPMN model. 19

Other Process Elements BPMN UML Accept Event Actions, Catch Events Initial Nodes Events Call Operation Actions, Throw Events Activity Final Nodes Event Definitions Events Exclusive Gateways DecisionNodes, MergeNodes Gateways Parallel, Complex, Inclusive Gateways JoinNodes, ForkNodes Event-based Gateways ForkNodes + Interruptible Regions Data Inputs, Data Outputs Input Pins, Activity Parameter Nodes, Output Pins Data Data Associations Object Flows Data Objects Data Store Nodes Input Sets, Output Sets Parameter Sets & Resources Lanes, LaneSets Activity Partitions Lanes Resources, Item Definitions Classes 20 Resource Roles / Parameters / Bindings Properties, Slots

Collaborations in Profile Negotiate Order Factory Supplier Schedule Shipment Plan Delivery UML Collaboration Consignee in underlying model Supply Chain Plan Shipment Choose Consolidator Shipper Pickup factory Location supplier consignee consolidator Negotiate Order shipper Factory Schedule Supplier Plan Consignee Shipment Delivery Plan Shipment Choose Consolidator Shipper Pickup Location  UML Collaborations are Classifiers.  Collaboration roles are properties. 21

Collaborations in Profile  Participants are UML Properties. – Typed by Classes or Activities.  Message Flow are constrained UML Information Flows. – Link actions in separate activities of the participants.  Conversations are UML CollaborationUses, or 22 Information Flow is locally defind.

Summary  Profile extends UML / SysML with BPMN terminology, syntax, and equivalent semantics. – Profiled UML / SysML model can be navigated as if it were a BPMN model. – UML / SysML semantics is constrained, extended or modified as needed for equivalence.  BPMN Processes => UML / SysML Activities  BPMN Collaborations => UML Collaborations  BPMN Message Flow => UML / SysML Information Flow 23