实例介绍
【实例简介】
BPMN2.0规范，详细描述了bpmn的元素以及相关信息。是了解Activiti等开源工作流的必备条件。
DISCLAIMER OF WARRANTY WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE IT IS PROVIDED AS IS AND MAY CONTAIN ERRORS OR MISPRINTS. THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND. EXPRESS OR IMPLIED. WITH REGARD TO THIS PUBLICATION INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OBJECT MANAGEMENT GROUP OR ANY OF THE COMPANIES LISTED ABOVE BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS. REVENUE DATA OR USE INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING. PERFORMANCE OR USE OF THIS MATERIAL EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification RESTRICTED RIGHTS LEGEND Use, duplication or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph(c)(1 (i of The Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph(c) (1) and (2)of the Commercial Computer Software-Restricted Rights clauses at 48 C F R. 52.227-19 or as specified in 48 C F.R. 227-7202-2 of the DoD. A.R. Supplement and its successors, or as specified in 48 C.F. R. 12. 212 of the Federal Acquisition Regulations and its successors, as applicable. The specification copyright owners are as indicated above and may be contacted through the object Management Group, 140 Kendrick Street, Needham, Ma 02494.U.S.A TRADEMARKS MDA, Model Driven Architecture(R, UMLR, UML Cube logoR, OMG Logo, CORBA and XMI are registered trademarks of the Object Management Group, Inc, and Object Management Group Tm, oMgtm, unified Modeling Language IM, Model Driven Architecture LogoIM. Model Driven Architecture DiagramM, CORBA logosTM, XMI LogoTM, CWMTM, CWM LogoTM, IIOPTM, MOFTM, OMG Interface Definition Language(IDL)TM and oMg SysMLTM are trademarks of the Object Management Group All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners COMPLIANCE The copyright holders listed above acknowledge that the Object Management Group(acting itself or through ils designees) is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use certification marks, trademarks or other special designations to indicate compliance with these materials Software developed under the terms of this license may claim compliance or conformance with this specification if and only if the software compliance is of a nature fully matching the applicable compliance points as stated in the specification Software developed only partially matching the applicable compliance points may claim only that the software was based on this specification, but may not claim compliance or conformance with this specification. In the event that testing suites are implemented or approved by object Management Group, Inc, software developed using this specification may claim compliance or conformance with the specification only if the software satisfactorily completes the testing suites OMGs Issue Reporting Procedure All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the Issue reporting Formlistedonthemainwebpagehttp://www.omg.org,underDocumentsReportaBug/issue (http://www.omg.org/technology/agreement.) Table of contents 1 Scope 1 2 Conformance 3 Normative references 4 Additional Information 4.1 Changes to Adopted OMG Specifications.....,.,...,......2 42 Acknowledgements,………………2 5 Small EXamples introducing Core Concepts. 5. 1 Shipment Process of a Hardware Retailer.s 5.2 The pizza collaboration 5.3 Order fulfillment and procurement,………… 6 Incident management. 8 6. 1 High level model for quick understanding 8 6.2 Detailed Collaboration and choreography 9 6.3 Human- driven vs, system- driven control flows………1 7 Models and Diagrams… …19 7.1 Lane and pool 7.1.1 Lane 19 7.1.2 Pool 72 Sub process and call activi!y.…… 7.2.1 Expanded Sub Process Example 7.2.2 Collapsed Sub Process Example.. 7.2. 3 Call Activity Example.. 23 8 Nobel Prize Example.... 25 8. 1 The nobel prize process scenario 25 82 The nobel prize pre。 cess Diagram,…26 9 Travel Booking Example.. 27 9.1 The Travel Booking Scenario……27 9.2 The Travel Booking Diagram 28 BPMn 2.0 by Example, Version 1.0 10 EXamples from Diagram Interchange Chapter. 29 0.1 Expanded Sub Process Example... 29 10.2 Collapsed Sub Process Example……29 10.2.1 Process Diagram...... 10.2.2 Sub Process Diagram 0.3 Multiple Lanes and Nested Lanes Example.. 29 10.4 Vertical Collaboration EXample.... 30 10.5 Conversation Example.... 30 10.6 Choreography Example.. 30 11 Correlation EXample...... 31 12 E-Mail voting example. 35 12.1 The first sub-Process 37 12.2 The Second sub-Process 38 12.3 The end of the process gwm.38 Annex A: XML Serializations for all presented models... 39 BPMn 2.0 by Example, Version 1.0 Preface OMG Founded in 1989, the Object Management Group, Inc (OMG) is an open membership, not-for-profit computer industry standards consortium that produces and maintains computer industry specifications for interoperable, portable, and reusable enterprise applications in distributed, heterogeneous environments. Membership includes Information Technology vendors, end users, government agencies, and academia OMG member companies write, adopt, and maintain its specifications following a mature, open process. OMGS specifications implement the Model Driven ArchitectureR(MDA), maximizing Roi through a full-lifecycle approach to enterprise integration that covers multiple operating systems, programming languages, middleware and networking infrastructures, and software development environments. OMGS specifications include: UMLR(Unified Modeling Language TM): CORBAiR(Common Object Request Broker Architecture); CWMTM(Common Warehouse Metamodel) and industry-specific standards for dozens of vertical markets MoreinformationontheOmgisavailableathttp://www.omg.org OMG Specifications As noted, OMG specifications address middleware, modeling and vertical domain frameworks. A Specifications Catalog is available from the omg website at http://www.omg.org/technology/documents/speccataloghtm Specifications within the Catalog are organized by the following categories OMG Modeling specifications UML MOF XMI CWM Profile specifications OMG Middleware Specifications ORBAIIOP IDL/Language Mappings Specialized cOrBa specifications CORBA Component Model (CCm) Platform Specific Model and Interface Specifications CORBAservices CORBAfacilities OMG Domain specifications OMG Embedded Intelligence specifications OMG Security specifications All of OMG's formal specifications may be downloaded without charge from our website. (Products implementing OMG specifications are available from individual suppliers )Copies of specifications, available in PostScript and PdF format, BPMn 2.0 by Example, Version 1.0 may be obtained from the Specifications Catalog cited above or by contacting the Object Management Group, Inc.at: CertainOmgspecificationsarealsoavailableasisOstandardsplEaseconsulthttp://www.iso.org Typographical Conventions The type styles shown below are used in this document to distinguish programming statements from ordinary english However, these conventions are not used in tables or section headings where no distinction is necessary Helvetica/Arial -10 pt. Bold Helvetica/Arial -10 pt Terms that appear in italics are defined in the glossary. Italic text also represents the name of a document specification, or other publication BPMN 2.0 by EXample, Version 1.0 Scope This document provides a number of BPmn 2.0 examples, which are non-executable bPmn 2.0 models conforming to the Process Modeling Conformance class as defined in the the OMG specification Business Process Model and Notation(BPMN)Version 2. 0. It is a non-normative document and its main goal is to assist in interpreting and implementing various aspects of the BPMn 2.0 specification. The examples are provided in form of Collaboration diagrams, Process diagrams, and Choreography diagrams as well as machine-readable files using the extensible Markup language (Xml) 2 Conformance As this is a non-normative document, an implementation which claims con formance to any of the conformance classes defined in section 2 of the BPMn 2.0 specification, is NOT Required to comply to statements made in this document Furthermore, if there are any inconsistencies between the bpmn 2.0 specification and this document, the statements of the bPmn 2.0 specification always have precedence 3 normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. Business Process Model and Notation(BPMN) Version 2.0 OMG, May 2010 http:/www.omg.org/spec/bpmn/2.0 c-2119 Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, IETF RFC 2119, March 1997 http://www.ietf.org/rfc/rfc2119.txt BPMn 2.0 by Example, Version 1.0 Additional information Changes to Adopted OMG Specifications If there are any inconsistencies between the BPMn 2.0 specification and this document, the statements of the BPMN 2.0 specification are considered to be correct 4.2 Acknowledgements The following companies contributed to the content of this document camunda services gmbh IBM Corp PNA Group SAP AG Trisotech. Inc The following persons were members of the core teams that contributed to the content of this document John Bulles (pna group) Jakob Freund(camunda services GmbH) Denis gagne(Trisotech, Inc. Falko Menge(camunda services GmbH) Matthias Kloppmann(IBm Corp SJir Nijssen(PNA group Gerardo Navarro-Suarez(camunda services GmbH) Ivana TrickOVIC (SAP AG) Stephen A. White(IBM Corp. In addition, the following persons contributed valuable ideas and feedback that improved the content and the quality of this document Joram Barrez(Alfresco) Mariano Benitez(oracle) Conrad Bock(NISt) John Hall (Model Systems) Bernd rucker(camunda services GmbH) BPMn 2.0 by Example, Version 1.0 【实例截图】
【核心代码】
BPMN2.0规范，详细描述了bpmn的元素以及相关信息。是了解Activiti等开源工作流的必备条件。
DISCLAIMER OF WARRANTY WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE IT IS PROVIDED AS IS AND MAY CONTAIN ERRORS OR MISPRINTS. THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND. EXPRESS OR IMPLIED. WITH REGARD TO THIS PUBLICATION INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OBJECT MANAGEMENT GROUP OR ANY OF THE COMPANIES LISTED ABOVE BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS. REVENUE DATA OR USE INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING. PERFORMANCE OR USE OF THIS MATERIAL EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification RESTRICTED RIGHTS LEGEND Use, duplication or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph(c)(1 (i of The Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph(c) (1) and (2)of the Commercial Computer Software-Restricted Rights clauses at 48 C F R. 52.227-19 or as specified in 48 C F.R. 227-7202-2 of the DoD. A.R. Supplement and its successors, or as specified in 48 C.F. R. 12. 212 of the Federal Acquisition Regulations and its successors, as applicable. The specification copyright owners are as indicated above and may be contacted through the object Management Group, 140 Kendrick Street, Needham, Ma 02494.U.S.A TRADEMARKS MDA, Model Driven Architecture(R, UMLR, UML Cube logoR, OMG Logo, CORBA and XMI are registered trademarks of the Object Management Group, Inc, and Object Management Group Tm, oMgtm, unified Modeling Language IM, Model Driven Architecture LogoIM. Model Driven Architecture DiagramM, CORBA logosTM, XMI LogoTM, CWMTM, CWM LogoTM, IIOPTM, MOFTM, OMG Interface Definition Language(IDL)TM and oMg SysMLTM are trademarks of the Object Management Group All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners COMPLIANCE The copyright holders listed above acknowledge that the Object Management Group(acting itself or through ils designees) is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use certification marks, trademarks or other special designations to indicate compliance with these materials Software developed under the terms of this license may claim compliance or conformance with this specification if and only if the software compliance is of a nature fully matching the applicable compliance points as stated in the specification Software developed only partially matching the applicable compliance points may claim only that the software was based on this specification, but may not claim compliance or conformance with this specification. In the event that testing suites are implemented or approved by object Management Group, Inc, software developed using this specification may claim compliance or conformance with the specification only if the software satisfactorily completes the testing suites OMGs Issue Reporting Procedure All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the Issue reporting Formlistedonthemainwebpagehttp://www.omg.org,underDocumentsReportaBug/issue (http://www.omg.org/technology/agreement.) Table of contents 1 Scope 1 2 Conformance 3 Normative references 4 Additional Information 4.1 Changes to Adopted OMG Specifications.....,.,...,......2 42 Acknowledgements,………………2 5 Small EXamples introducing Core Concepts. 5. 1 Shipment Process of a Hardware Retailer.s 5.2 The pizza collaboration 5.3 Order fulfillment and procurement,………… 6 Incident management. 8 6. 1 High level model for quick understanding 8 6.2 Detailed Collaboration and choreography 9 6.3 Human- driven vs, system- driven control flows………1 7 Models and Diagrams… …19 7.1 Lane and pool 7.1.1 Lane 19 7.1.2 Pool 72 Sub process and call activi!y.…… 7.2.1 Expanded Sub Process Example 7.2.2 Collapsed Sub Process Example.. 7.2. 3 Call Activity Example.. 23 8 Nobel Prize Example.... 25 8. 1 The nobel prize process scenario 25 82 The nobel prize pre。 cess Diagram,…26 9 Travel Booking Example.. 27 9.1 The Travel Booking Scenario……27 9.2 The Travel Booking Diagram 28 BPMn 2.0 by Example, Version 1.0 10 EXamples from Diagram Interchange Chapter. 29 0.1 Expanded Sub Process Example... 29 10.2 Collapsed Sub Process Example……29 10.2.1 Process Diagram...... 10.2.2 Sub Process Diagram 0.3 Multiple Lanes and Nested Lanes Example.. 29 10.4 Vertical Collaboration EXample.... 30 10.5 Conversation Example.... 30 10.6 Choreography Example.. 30 11 Correlation EXample...... 31 12 E-Mail voting example. 35 12.1 The first sub-Process 37 12.2 The Second sub-Process 38 12.3 The end of the process gwm.38 Annex A: XML Serializations for all presented models... 39 BPMn 2.0 by Example, Version 1.0 Preface OMG Founded in 1989, the Object Management Group, Inc (OMG) is an open membership, not-for-profit computer industry standards consortium that produces and maintains computer industry specifications for interoperable, portable, and reusable enterprise applications in distributed, heterogeneous environments. Membership includes Information Technology vendors, end users, government agencies, and academia OMG member companies write, adopt, and maintain its specifications following a mature, open process. OMGS specifications implement the Model Driven ArchitectureR(MDA), maximizing Roi through a full-lifecycle approach to enterprise integration that covers multiple operating systems, programming languages, middleware and networking infrastructures, and software development environments. OMGS specifications include: UMLR(Unified Modeling Language TM): CORBAiR(Common Object Request Broker Architecture); CWMTM(Common Warehouse Metamodel) and industry-specific standards for dozens of vertical markets MoreinformationontheOmgisavailableathttp://www.omg.org OMG Specifications As noted, OMG specifications address middleware, modeling and vertical domain frameworks. A Specifications Catalog is available from the omg website at http://www.omg.org/technology/documents/speccataloghtm Specifications within the Catalog are organized by the following categories OMG Modeling specifications UML MOF XMI CWM Profile specifications OMG Middleware Specifications ORBAIIOP IDL/Language Mappings Specialized cOrBa specifications CORBA Component Model (CCm) Platform Specific Model and Interface Specifications CORBAservices CORBAfacilities OMG Domain specifications OMG Embedded Intelligence specifications OMG Security specifications All of OMG's formal specifications may be downloaded without charge from our website. (Products implementing OMG specifications are available from individual suppliers )Copies of specifications, available in PostScript and PdF format, BPMn 2.0 by Example, Version 1.0 may be obtained from the Specifications Catalog cited above or by contacting the Object Management Group, Inc.at: CertainOmgspecificationsarealsoavailableasisOstandardsplEaseconsulthttp://www.iso.org Typographical Conventions The type styles shown below are used in this document to distinguish programming statements from ordinary english However, these conventions are not used in tables or section headings where no distinction is necessary Helvetica/Arial -10 pt. Bold Helvetica/Arial -10 pt Terms that appear in italics are defined in the glossary. Italic text also represents the name of a document specification, or other publication BPMN 2.0 by EXample, Version 1.0 Scope This document provides a number of BPmn 2.0 examples, which are non-executable bPmn 2.0 models conforming to the Process Modeling Conformance class as defined in the the OMG specification Business Process Model and Notation(BPMN)Version 2. 0. It is a non-normative document and its main goal is to assist in interpreting and implementing various aspects of the BPMn 2.0 specification. The examples are provided in form of Collaboration diagrams, Process diagrams, and Choreography diagrams as well as machine-readable files using the extensible Markup language (Xml) 2 Conformance As this is a non-normative document, an implementation which claims con formance to any of the conformance classes defined in section 2 of the BPMn 2.0 specification, is NOT Required to comply to statements made in this document Furthermore, if there are any inconsistencies between the bpmn 2.0 specification and this document, the statements of the bPmn 2.0 specification always have precedence 3 normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. Business Process Model and Notation(BPMN) Version 2.0 OMG, May 2010 http:/www.omg.org/spec/bpmn/2.0 c-2119 Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, IETF RFC 2119, March 1997 http://www.ietf.org/rfc/rfc2119.txt BPMn 2.0 by Example, Version 1.0 Additional information Changes to Adopted OMG Specifications If there are any inconsistencies between the BPMn 2.0 specification and this document, the statements of the BPMN 2.0 specification are considered to be correct 4.2 Acknowledgements The following companies contributed to the content of this document camunda services gmbh IBM Corp PNA Group SAP AG Trisotech. Inc The following persons were members of the core teams that contributed to the content of this document John Bulles (pna group) Jakob Freund(camunda services GmbH) Denis gagne(Trisotech, Inc. Falko Menge(camunda services GmbH) Matthias Kloppmann(IBm Corp SJir Nijssen(PNA group Gerardo Navarro-Suarez(camunda services GmbH) Ivana TrickOVIC (SAP AG) Stephen A. White(IBM Corp. In addition, the following persons contributed valuable ideas and feedback that improved the content and the quality of this document Joram Barrez(Alfresco) Mariano Benitez(oracle) Conrad Bock(NISt) John Hall (Model Systems) Bernd rucker(camunda services GmbH) BPMn 2.0 by Example, Version 1.0 【实例截图】
【核心代码】
标签：
好例子网口号：伸出你的我的手 — 分享！
相关软件
小贴士
感谢您为本站写下的评论，您的评论对其它用户来说具有重要的参考价值，所以请认真填写。
- 类似“顶”、“沙发”之类没有营养的文字，对勤劳贡献的楼主来说是令人沮丧的反馈信息。
- 相信您也不想看到一排文字/表情墙，所以请不要反馈意义不大的重复字符，也请尽量不要纯表情的回复。
- 提问之前请再仔细看一遍楼主的说明，或许是您遗漏了。
- 请勿到处挖坑绊人、招贴广告。既占空间让人厌烦，又没人会搭理，于人于己都无利。
关于好例子网
本站旨在为广大IT学习爱好者提供一个非营利性互相学习交流分享平台。本站所有资源都可以被免费获取学习研究。本站资源来自网友分享，对搜索内容的合法性不具有预见性、识别性、控制性，仅供学习研究，请务必在下载后24小时内给予删除，不得用于其他任何用途，否则后果自负。基于互联网的特殊性，平台无法对用户传输的作品、信息、内容的权属或合法性、安全性、合规性、真实性、科学性、完整权、有效性等进行实质审查；无论平台是否已进行审查，用户均应自行承担因其传输的作品、信息、内容而可能或已经产生的侵权或权属纠纷等法律责任。本站所有资源不代表本站的观点或立场，基于网友分享，根据中国法律《信息网络传播权保护条例》第二十二与二十三条之规定，若资源存在侵权或相关问题请联系本站客服人员，点此联系我们。关于更多版权及免责申明参见 版权及免责申明
网友评论
我要评论