Business Process Modeling Notation (BPMN)

2y ago
60 Views
3 Downloads
2.64 MB
296 Pages
Last View : 21d ago
Last Download : 2m ago
Upload by : Melina Bettis
Transcription

Business Process Management Initiative (BPMI)Business Process Modeling Notation(BPMN)Version 1.0 - May 3, 2004Copyright 2004, BPMI.org. All Rights ReservedAbstractThe Business Process Modeling Notation (BPMN) specification provides a graphical notationfor expressing business processes in a Business Process Diagram (BPD). The objective ofBPMN is to support business process management by both technical users and businessusers by providing a notation that is intuitive to business users yet able to represent complexprocess semantics. The BPMN specification also provides a mapping between the graphics ofthe notation to the underlying constructs of execution languages, particularly BPEL4WS.Status of this DocumentThis document is version 1.0 of the BPMN specification submitted by members of the BPMIinitiative on May 3, 2004. It supersedes any previous version. It has been produced based onthe work of the members of the BPMI Notation Working Group. Comments on this documentand discussions of this document should be sent to BPMN-PublicReview@bpmi.org. It isexpected that as experience is gained with BPMN there will be feedback about this relativelyyoung specification, particularly the mapping from the notation to BPEL4WS. Thus, thisdocument may be updated, replaced, or made obsolete by other documents at any time.

BPMN 1.0AcknowledgementsThe author/editor of the specification:Stephen A. White, IBM Corporation (wstephe@us.ibm.com)The members of the BPMI Notation Working Group contributed to the development of thisspecification, including those who contributed to the text and editing of the specification:Ashish Agrawal, Intalio (ashish@intalio.com)Michael Anthony, International Performance Group (manthony@ipgl.com)Assaf Arkin, Intalio (arkin@intalio.com)Steve Ball, Sterling Commerce (steve ball@stercomm.com)Rob Bartel, iGrafx (rob.bartel@igrafx.com)Steinar Carlsen, Computas (sca@computas.com)Ugo Corda, SeeBeyond Technology Corporation (ucorda@seebeyond.com)Tony Fletcher (tony fletcher@btopenworld.com)Steven Forgey, SeeBeyond Technology Corporation (sforgey@seebeyond.com)Jean-Luc Giraud, Axway Software (jlgiraud@axway.com)Paul Harmon (pharmon@sbcglobal.net)Damion Heredia, Lombardi Software (damion.herediat@lombardisoftware.com)George Keeling, Casewise (george@casewise.co.uk)Brian James, Proforma (bjames@proformacorp.com)Antoine Lonjon, Mega International (alonjon@mega.com)Mike Marin, FileNet (mmarin@filenet.com)Lee Mason, webMethods (mason.lee@webmethods.com)Derek Miers, Enix Consulting Ltd. (miers@enix.co.uk)Alex Moffat, Lombardi Software (alex.moffat@lombardisoftware.com)Roberta Norin, Pegasystems (roberta.norin@pega.com)Martin Owen, Popkin Software (martin.owen@popkin.co.uk)Jog Raj, Popkin Software (jog.raj@popkin.co.uk)Bob Smith, Tall Tree Labs (robsmith5@1talltrees.com)Manfred Sturm, ITPearls AG (manfred.sturm@itpearls.com)Balasubramanian (Bala) Suryanarayanan, Infosys (balas@infosys.com)Roy Thompson, Casewise (roy.thompson@casewise.co.uk)Paul Vincent, Fair, Isaac & Company (paulvincent@fairisaac.com)Paul Wuethrich, Sybase (pwuethri@sybase.com)The members of the BPMI Notation Working Group would like to thank SeeBeyondTechnology Corporation and International Business Machines Corporation for their valuablesupport in the development of this specification.2 / 296Copyright 2004, BPMI.org All Rights Reserved

BPMN 1.0Notice of BPMI.org Policies on Intellectual Property Rights &CopyrightBPMI.org takes no position regarding the validity or scope of any intellectual property or otherrights that might be claimed to pertain to the implementation or use of the technologydescribed in this document or the extent to which any license under such rights might or mightnot be available; neither does it represent that it has made any effort to identify any suchrights. Information on BPMI.org's procedures with respect to rights in BPMI.org specificationscan be found at the BPMI.org website. Copies of claims of rights made available forpublication and any assurances of licenses to be made available, or the result of an attemptmade to obtain a general license or permission for the use of such proprietary rights byimplementers or users of this specification, can be obtained from the BPMI.org Chairman.BPMI.org invites any interested party to bring to its attention any copyrights, patents or patentapplications, or other proprietary rights, which may cover technology that may be required toimplement this specification. Please address the information to the BPMI.org Chairman.This document and translations of it may be copied and furnished to others, and derivativeworks that comment on or otherwise explain it or assist in its implementation may be prepared,copied, published and distributed, in whole or in part, without restriction of any kind, providedthat the above copyright notice and this paragraph are included on all such copies andderivative works. However, this document itself may not be modified in any way, such as byremoving the copyright notice or references to BPMI.org, except as needed for the purpose ofdeveloping BPMI.org specifications, in which case the procedures for copyrights defined in theBPMI.org Intellectual Property Rights document must be followed, or as required to translate itinto languages other than English.The limited permissions granted above are perpetual and will not be revoked by BPMI.org orits successors or assigns.This document and the information contained herein is provided on an "AS IS" basis andBPMI.org DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOTLIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOTINFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.Copyright The Business Process Management Initiative [BPMI.org], May 3, 2004. All RightsReserved.Copyright 2004, BPMI.org All Rights Reserved3 / 296

BPMN 1.0Table of ContentsAbstract . 1Status of this Document . 1Acknowledgements. 2Notice of BPMI.org Policies on Intellectual Property Rights & Copyright. 3Table of Contents . 4List of Figures . 8List of Tables. 12List of Examples . 161. Introduction . 171.1 Conventions. 181.1.1 Typographical and Linguistic Conventions and Style . 181.2 Dependency on Other Specifications . 191.3 Conformance. 192. BPMN Overview. 212.1 BPMN Scope . 222.1.1 Uses of BPMN . 222.1.2 Diagram Point of View . 262.1.3 Extensibility of BPMN and Vertical Domains. 263. Business Process Diagrams. 273.1 BPD Core Element Set. 273.2 BPD Complete Set . 313.3 Use of Text, Color, Size, and Lines in a Diagram. 383.4 Flow Object Connection Rules. 393.4.1 Sequence Flow Rules . 403.4.2 Message Flow Rules. 413.5 Business Process Diagram Attributes. 423.5.1 Changes Since 1.0 Draft Version . 423.6 Processes. 423.6.1 Attributes . 433.6.2 Changes Since 1.0 Draft Version . 444. Business Process Diagram Graphical Objects. 454.1 Common Graphical Object Attributes. 454.1.1 Changes Since 1.0 Draft Version . 454.2 Common Flow Object Attributes. 464.2.1 Changes Since 1.0 Draft Version . 464.3 Events . 464.3.1 Common Event Attributes. 474.3.2 Start . 474 / 296Copyright 2004, BPMI.org All Rights Reserved

BPMN 1.0Table of Contents4.3.3 End . 524.3.4 Intermediate. 574.4 Activities . 634.4.1 Common Activity Attributes. 634.4.2 Sub-Process . 674.4.3 Task . 754.5 Gateways . 824.5.1 Common Gateway Features . 844.5.2 Exclusive Gateways (XOR) . 854.5.3 Inclusive Gateways (OR) . 934.5.4 Complex Gateways . 974.5.5 Parallel Gateways (AND). 1004.6 Swimlanes (Pools and Lanes) . 1024.6.1 Common Swimlane Attributes . 1024.6.2 Pool. 1034.6.3 Lane . 1064.7 Artifacts. 1074.7.1 Common Artifact Definitions. 1074.7.2 Data Object. 1084.7.3 Text Annotation. 1104.7.4 Group. 1115. Business Process Diagram Connecting Objects. 1135.1 Graphical Connecting Objects. 1135.1.1 Common Connecting Object Attributes. 1135.1.2 Changes Since 1.0 Draft Version . 1135.1.3 Sequence Flow . 1145.1.4 Message Flow. 1165.1.5 Association . 1195.2 Sequence Flow Mechanisms . 1215.2.1 Normal Flow . 1215.2.2 Exception Flow . 1435.2.3 Ad Hoc . 1445.3 Compensation Association. 1466. Mapping to BPEL4WS . 1496.1 Business Process Diagram Mappings . 1496.2 Business Process Mappings . 1506.3 Common Flow Object Mappings . 1516.4 Events . 1526.4.1 Start Event Mappings . 1526.4.2 End Event Mappings . 1546.4.3 Intermediate Event Mappings . 1556.5 Activities . 161Copyright 2004, BPMI.org All Rights Reserved5 / 296

BPMN 1.06.5.1 Common Activity Mappings. 1616.5.2 Sub-Process Mappings . 1766.5.3 Task Mappings . 1786.6 Gateways . 1826.6.1 Common Gateway Mappings. 1826.6.2 Exclusive . 1836.6.3 Inclusive . 1856.6.4 Complex . 1896.6.5 Parallel. 1896.7 Pool . 1896.8 Lane . 1896.9 Artifacts. 1896.10 Sequence Flow . 1906.10.1 When to Map a Sequence Flow to a BPEL4WS Link . 1926.11 Message Flow . 1936.12 Association . 1936.13 Exception Flow . 1936.14 Compensation Association. 1996.15 Assignment Mapping . 2006.16 BPMN Supporting Type Elements . 2006.17 Determining the Extent of a BPEL4WS Structured Element. 2016.17.1 BPMN Elements that Span Multiple BPEL4WS Sub-Elements.

for expressing business processes in a Business Process Diagram (BPD). The objective of BPMN is to support business process management by both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics. The BP

Related Documents:

Business Process Modeling Notation (BPMN) BPMN is a grphical representation for specifying business processes in a workflow BPMN was developed by Business Process Management Initiative (BPMI) BPMN is currently maintained by the Object Management Group (OMG) since 2005 BPMN 2.0 p

BPMN is an internationally accepted process modeling standard. BPMN is independent of any process modeling methodology. BPMN creates a standardized bridge which reduces the gap between business processes and their implementation. BPMN enables you to model pro

The Business Process Modeling Notation (BPMN) is a standard for business process modeling that provides a graphical notation for specifying business processes in a Business Process Diagram (BPD). The notation is based on a flowcharting technique. The objective of BPMN is to support business

Business analysts use Business Process Modeling Notation (BPMN) to model business process diagrams. BPMN [32] has risen in recent years as the popular modeling “lan-guage” for business processes. Figure 1.1 is a simple example of a BPMN diagram. BPMN became the popular s

Figure 3: Results of Business Process Modeling Figure 2: Process model for each individual process About bPMn Figure 4: Activity types and markers BPMN (Business Process Modeling Notation) is a graphical notation for business process modeling. The objective of BPMN is to support business process modeling

iServer BPMN Stencil: Levels of BPMN Thanks for Downloading the Free BPMN 2.0 Stencil! Orbus Software have created a Visio BPMN Stencil that you are free to use. This Stencil was created based on the OMG s BPMN Specification v2.0 (January 2011), and to the best of our knowledge all shapes are fully supported as specified.

Definition of BPMN The Business Process Modeling Notation (BPMN) is a graphical notation that depicts the steps in a business process. – BPMN depicts the end to end flow of a business process. – Notation designed to co

BPMN is an internationally accepted process modeling standard. BPMN is independent of any process modeling methodology. BPMN creates a standardized bridge which reduces the gap between business processes and their implementation. BPMN enables you to model