词条 | Business Process Model and Notation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
释义 |
}} Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a business process model. Business Process Management Initiative (BPMI) developed BPMN, which has been maintained by the Object Management Group since the two organizations merged in 2005. Version 2.0 of BPMN was released in January 2011,[1] at which point the name was adapted to Business Process Model and Notation as execution semantics were also introduced alongside the notational and diagramming elements. Though it is an OMG specification, BPMN is also ratified as ISO 19510. The latest version is BPMN 2.0.2, published in January 2014. OverviewBusiness Process Model and Notation (BPMN) is a standard for business process modeling that provides a graphical notation for specifying business processes in a Business Process Diagram (BPD),[1] based on a flowcharting technique very similar to activity diagrams from Unified Modeling Language (UML).[2] The objective of BPMN is to support business process management, for both technical users and business users, by providing a notation that is intuitive to business users, yet able to represent complex process semantics. The BPMN specification also provides a mapping between the graphics of the notation and the underlying constructs of execution languages, particularly Business Process Execution Language (BPEL).[3] The primary goal of BPMN is to provide a standard notation readily understandable by all business stakeholders. These include the business analysts who create and refine the processes, the technical developers responsible for implementing them, and the business managers who monitor and manage them. Consequently, BPMN serves as a common language, bridging the communication gap that frequently occurs between business process design and implementation. Currently there are several competing standards for business process modeling languages used by modeling tools and processes. Widespread adoption of a single standard would help unify the expression of basic business process concepts (e.g., public and private processes, choreographies), as well as advanced process concepts (e.g., exception handling, transaction compensation). BPMN has been complemented by two new standards for building case management models and decision models, the Case Management Model and Notation and the Decision Model and Notation. TopicsScopeBPMN is constrained to support only the concepts of modeling applicable to business processes. Other types of modeling done by organizations for non-process purposes are out of scope for BPMN. Examples of modeling excluded from BPMN are:
In addition, while BPMN shows the flow of data (messages), and the association of data artifacts to activities, it is not a data flow diagram. ElementsBPMN models are expressed by simple diagrams constructed from a limited set of graphical elements. For both business users and developers, they simplify understanding of business activities' flow and process. BPMN's four basic element categories are:
Events, activities, gateways
Sequence flow, message flow, association
Pool, lane
Data object, group, annotation These four categories enable creation of simple business process diagrams (BPDs). BPDs also permit making new types of flow object or artifact, to make the diagram more understandable. Flow objects and connecting objectsFlow objects are the main describing elements within BPMN, and consist of three core elements: events, activities, and gateways.
An Event is represented with a circle and denotes something that happens (compared with an activity, which is something that is done). Icons within the circle denote the type of event (e.g., an envelope representing a message, or a clock representing time). Events are also classified as Catching (for example, if catching an incoming message starts a process) or Throwing (such as throwing a completion message when a process ends). ; Start event Acts as a process trigger; indicated by a single narrow border, and can only be Catch, so is shown with an open (outline) icon. ; Intermediate event Represents something that happens between the start and end events; is indicated by a double border, and can Throw or Catch (using solid or open icons as appropriate). For example, a task could flow to an event that throws a message across to another pool, where a subsequent event waits to catch the response before continuing. ; End event Represents the result of a process; indicated by a single thick or bold border, and can only Throw, so is shown with a solid icon.
An activity is represented with a rounded-corner rectangle and describes the kind of work which must be done. An activity is a generic term for work that a company performs. It can be atomic or compound. ; Task A task represents a single unit of work that is not or cannot be broken down to a further level of business process detail. It is referred to as an atomic activity. A task is the lowest level activity illustrated on a process diagram. A set of tasks may represent a high-level procedure. ; Sub-process Used to hide or reveal additional levels of business process detail. When collapsed, a sub-process is indicated by a plus sign against the bottom line of the rectangle; when expanded, the rounded rectangle expands to show all flow objects, connecting objects, and artifacts. A sub-process is referred to as a compound activity. Has its own self-contained start and end events; sequence flows from the parent process must not cross the boundary. ; Transaction A form of sub-process in which all contained activities must be treated as a whole; i.e., they must all be completed to meet an objective, and if any one of them fails, they must all be compensated (undone). Transactions are differentiated from expanded sub-processes by being surrounded by a double border. ; Call Activity A point in the process where a global process or a global Task is reused. A call activity is differentiated from other activity types by a bolded border around the activity area.
A gateway is represented with a diamond shape and determines forking and merging of paths, depending on the conditions expressed. ; Exclusive Used to create alternative flows in a process. Because only one of the paths can be taken, it is called exclusive. ; Event Based The condition determining the path of a process is based on an evaluated event. ; Parallel Used to create parallel paths without evaluating any conditions. ; Inclusive Used to create alternative flows where all paths are evaluated. ; Exclusive Event Based An event is being evaluated to determine which of mutually exclusive paths will be taken. ; Complex Used to model complex synchronization behavior. ; Parallel Event Based Two parallel processes are started based on an event, but there is no evaluation of the event.
Flow objects are connected to each other using Connecting objects, which are of three types: sequences, messages, and associations. ; Sequence Flow A Sequence Flow is represented with a solid line and arrowhead, and shows in which order the activities are performed. The sequence flow may also have a symbol at its start, a small diamond indicates one of a number of conditional flows from an activity, while a diagonal slash indicates the default flow from a decision or activity with conditional flows. ; Message Flow A Message Flow is represented with a dashed line, an open circle at the start, and an open arrowhead at the end. It tells us what messages flow across organizational boundaries (i.e., between pools). A message flow can never be used to connect activities or events within the same pool. ; Association An Association is represented with a dotted line. It is used to associate an Artifact or text to a Flow Object, and can indicate some directionality using an open arrowhead (toward the artifact to represent a result, from the artifact to represent an input, and both to indicate it is read and updated). No directionality is used when the Artifact or text is associated with a sequence or message flow (as that flow already shows the direction). Swim lanes and artifactsSwim lanes are a visual mechanism of organising and categorising activities, based on cross functional flowcharting, and in BPMN consist of two types:
Represents major participants in a process, typically separating different organisations. A pool contains one or more lanes (like a real swimming pool). A pool can be open (i.e., showing internal detail) when it is depicted as a large rectangle showing one or more lanes, or collapsed (i.e., hiding internal detail) when it is depicted as an empty rectangle stretching the width or height of the diagram.
Used to organise and categorise activities within a pool according to function or role, and depicted as a rectangle stretching the width or height of the pool. A lane contains the flow objects, connecting objects and artifacts. Artifacts allow developers to bring some more information into the model/diagram. In this way the model/diagram becomes more readable. There are three pre-defined Artifacts and they are:
Examples of business process diagramsBPMN 2.0.2The vision of BPMN 2.0.2 is to have one single specification for a new Business Process Model and Notation that defines the notation, metamodel and interchange format but with a modified name that still preserves the "BPMN" brand. The features include:
The current version of the specification was released in January 2014.[5] Comparison of BPMN versions{{Technical|section|date=December 2012}}{{update|section|date=February 2014}}
Types of BPMN sub-modelBusiness process modeling is used to communicate a wide variety of information to a wide variety of audiences. BPMN is designed to cover this wide range of usage and allows modeling of end-to-end business processes to allow the viewer of the Diagram to be able to easily differentiate between sections of a BPMN Diagram. There are three basic types of sub-models within an end-to-end BPMN model: Private (internal) business processes, Abstract (public) processes, and Collaboration (global) processes:
Within and between these three BPMN sub-models, many types of Diagrams can be created. The following are the types of business processes that can be modeled with BPMN (those with asterisks may not map to an executable language):
BPMN is designed to allow all the above types of Diagrams. However, it should be cautioned that if too many types of sub-models are combined, such as three or more private processes with message flow between each of them, then the Diagram may become difficult to understand. Thus, the OMG recommends that the modeler pick a focused purpose for the BPD, such as a private or collaboration process. Weaknesses{{unreferenced section|date=February 2014}}The weaknesses of BPMN could relate to:
BPEL and BPMNThe BPMN specification includes an informal and partial [https://web.archive.org/web/20100706013908/http://www.bpmn.org/Documents/Mapping_BPMN_to_BPEL_Example.pdf mapping] from BPMN to BPEL 1.1. A more detailed mapping of BPMN to BPEL has been implemented in a number of tools, including an open-source tool known as [https://code.google.com/p/bpmn2bpel/ BPMN2BPEL]. However, the development of these tools has exposed fundamental differences between BPMN and BPEL, which make it very difficult, and in some cases impossible, to generate human-readable BPEL code from BPMN models. Even more difficult is the problem of BPMN-to-BPEL round-trip engineering: generating BPEL code from BPMN diagrams and maintaining the original BPMN model and the generated BPEL code synchronized, in the sense that any modification to one is propagated to the other.{{Citation needed|date=July 2013}} See also
References1. ^[https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20050202022_2005202152.pdf An XML Representation for Crew Procedures], Richard C. Simpson (2004), Final Report NASA Faculty Fellowship Program (Johnson Space Center) 2. ^Process Modeling Notations and Workflow Patterns {{webarchive |url=https://web.archive.org/web/20100706013817/http://www.bpmn.org/Documents/Notations_and_Workflow_Patterns.pdf |date=July 6, 2010 }}, paper by Stephen A. White of IBM Corporation (2006) 3. ^{{cite web|author=Stephen A. White|title=Business Process Modeling Notation v1.0|url=http://www.omg.org/bpmn/Documents/BPMN_V1-0_May_3_2004.pdf|date=3 May 2004|deadurl=yes|archiveurl=https://web.archive.org/web/20130818123649/http://www.omg.org/bpmn/Documents/BPMN_V1-0_May_3_2004.pdf|archivedate=18 August 2013|df=}} for the Business Process Management Initiative (BPMI) 4. ^{{cite web|author=OMG|title=BPMN Working Draft|url=http://www.omg.org/bpmn/Documents/BPMN_Sections_1_and%202CMP.pdf|accessdate=2012-05-01}}{{dead link|date=July 2017 |bot=InternetArchiveBot |fix-attempted=yes }} 5. ^1 {{cite web|author=OMG|title=BPMN 2.0|url=http://www.omg.org/spec/BPMN/2.0/|accessdate=2011-03-29}} 6. ^{{cite web|author= |title=BPMN FAQ|url=http://bpmnforum.com/bpmn-faq/|accessdate=2015-02-05}} Further reading
External links{{Commons category|Business Process Modeling Notation}}
6 : Diagrams|Business process modelling|ISO standards|Specification languages|Modeling languages|Notation |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。