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.

BPMN-AProcesswithNormalFlow
Example of a Business Process Model and Notation for a process with a normal flow.

Overview

Business 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),[2] based on a flowcharting technique very similar to activity diagrams from Unified Modeling Language (UML).[3] 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).[4]

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.

Topics

Scope

BPMN 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:

  • Organizational structures
  • Functional breakdowns
  • Data models[5]

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.

Elements

BPMN 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:

Flow objects
Events, activities, gateways
Connecting objects
Sequence flow, message flow, association
Swim lanes
Pool, lane
Artifacts
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 objects

BPMN plain event types

Event

BPMN Activity Types

Activity

BPMN gateway types

Gateway

Different Types of BPMN connections

Connections

Flow objects are the main describing elements within BPMN, and consist of three core elements: events, activities, and gateways.

Event
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.
Activity
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.
Gateway
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.
Connections

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 artifacts

Swin Lane - BPMN 2.0 Artifact

Swimlanes

Data object - BPMN 2.0 Artifacts

Data objects

Group - BPMN 2.0 Artifacts

Groups

Annotation - BPMN 2.0 Artifacts

Annotation

Swim lanes are a visual mechanism of organising and categorising activities, based on cross functional flowcharting, and in BPMN consist of two types:

Pool
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.
Lane
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:

  • Data objects: Data objects show the reader which data is required or produced in an activity.
  • Group: A Group is represented with a rounded-corner rectangle and dashed lines. The group is used to group different activities but does not affect the flow in the diagram.
  • Annotation: An annotation is used to give the reader of the model/diagram an understandable impression.

Examples of business process diagrams

BPMN-DiscussionCycle

Discussion cycle

BPMN-E-MailVotingProcess

E-mail voting process

BPMN-CollectVotes

Collect votes

BPMN 2.0.2

The 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:

  • Formalizes the execution semantics for all BPMN elements.
  • Defines an extensibility mechanism for both Process model extensions and graphical extensions.
  • Refines Event composition and correlation.
  • Extends the definition of human interactions.
  • Defines a Choreography model.

The current version of the specification was released in January 2014.[1]

Comparison of BPMN versions

Attributes BPMN 1.0 BPMN 1.1 BPMN 1.2 BPMN 2.0
Consortium BPMI & iGrafx OMG OMG OMG
Date of release May 2004 January 2008 January 2009 January 2011
Models
  • Collaborative (public) B2B processes,
  • internal (private) business processes.
  • collaborative (public) B2B processes,
  • internal (private) business processes,
  • a choreography – expected behavior between two or more business participants,
  • collaborations, which is a collection of participants and their interaction and
  • a conversation – the logical relation of message exchanges.
event
  • start (none, message, timer, rule, link, multiple)
  • intermediate (none, message, timer, error, cancel, compensation, rule, link, multiple)
  • end (none, message, error, cancel, compensation, link, terminate, multiple)
  • start (none, message, timer, conditional, signal, multiple)
  • intermediate (none, message, timer, error, cancel, compensation, conditional, link, signal, multiple)
  • end (none, message, error, cancel, compensation, signal,terminate, multiple)
  • start
    • top-level (none, message, timer, conditional, signal, multiple, parallel multiple)
    • event sub-process interrupting (message, timer, escalation, conditional, error, compensation, signal, multiple, parallel multiple)
    • event sub-process non-interrupting (message, timer, escalation, conditional, signal, multiple, parallel multiple)
  • intermediate
    • catching (message, timer, conditional, link, signal, multiple, parallel multiple)
    • boundary interrupting (message, timer, escalation, conditional, error, cancel, compensation, signal, multiple, parallel multiple)
    • boundary non-interrupting (message, timer, escalation, conditional, signal, multiple, parallel multiple, terminate)
    • throwing (none, message, escalation, link, compensation, signal, multiple, parallel multiple)
  • end (none, message, escalation, error, cancel, compensation, signal, multiple, terminate)
activity
  • task (atomic)
  • process/sub-process (nonatomic)
    • collapsed sub-process
    • expanded sub-process
  • task (atomic)
  • choreography task
    • collapsed choreography sub-process
    • expanded choreography sub-process
  • process/sub-process (nonatomic)
    • collapsed sub-process
    • expanded sub-process
gateway
  • XOR – exclusive decision and merging. both data-based and event-based. data-based can be shown with or without the "x" marker.
  • OR – inclusive decision and merging
  • complex – complex conditions and situations
  • AND – forking and joining
  • exclusive decision and merging. both data-based and event-based. data-based can be shown with or without the "x" marker.
  • inclusive decision and merging.
  • complex – complex conditions and situations.
  • parallel forking and joining.
  • exclusive decision and merging. both data-based and event-based. exclusive can be shown with or without the "x" marker.
  • inclusive gateway decision and merging
  • complex gateway – complex conditions and situations
  • parallel gateway – forking and joining
sequence flow

normal flow
uncontrolled flow
conditional flow
default flow
exception flow

message flow message flow
association association
pool pool
lane lane
data objects data object
  • data object
    • collection
    • data input
    • data output
groups group
annotations annotations
message message
other elements
  • looping
    • activity looping
    • sequence flow looping
  • multiple instances
  • process break
  • transactions
  • nested/embedded sub-process
  • off-page connector
  • compensation association
  • looping
    • activity looping
    • sequence flow looping
  • multiple instances
  • process break
  • transactions
  • nested/embedded sub-process
  • off-page connector
  • compensation association
  • communication (subcommunication)
  • communication link
Number of all elements 48 55 55 116
Major changes
  • The new specification introduces a categorization of event triggers into "catching" and "throwing" events. I.e. there are two kinds of intermediate message events now – one kind responsible for reception of messages ("catching") and one kind responsible for sending messages ("throwing").
  • In addition to the old types, it introduces a new type, the signal event.
  • Start and end link events do not exist any longer in BPMN 1.1.
  • The old "rule events" were renamed to conditional events. The semantics and appearance have not changed.
  • The event-based gateway in BPMN 1.1 looks slightly different from what it looked like in 1.0. Instead of the hexagonal star it now has a pentagon in its center. The same shape is also used for the multiple events (start, intermediate, end).
  • There is an additional line separating your lane's description from its content.

The BPMN 1.2 minor revision changes consist of editorial corrections and implementation bug fixes. Consequently, these minor changes affect modeling tool vendors more than modelers (users).[6]

  • Choreographies
    • Choreographies-model
    • Conversation-model
  • Complete Metamodel
  • BPMN Core
  • BPMN Execution Semantics
  • BPMN – BPEL Mapping
  • XPDL (BPMN XML Serialization)
  • Diagram Interchange
  • Elements For Abstraction
    • Callable Element
    • Call Activity
    • Global Task
  • Gateways (Updated)
    • Exclusive/Parallel Event-based Gateway (they stand at the beginning of the process)
  • Tasks/SubProcesses (Updated)
    • Event-Subprocess (Used to handle events in the bounding subprocess)
    • BusinessRule task
    • Sequential Multi-Instance Activity
    • Service Task
  • Artifacts (Updated)
    • Data Objects (Collection, Data Input, Data Output)

Types of BPMN sub-model

Business 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:

Private (internal) business processes
Private business processes are those internal to a specific organization and are the type of processes that have been generally called workflow or BPM processes. If swim lanes are used then a private business process will be contained within a single Pool. The Sequence Flow of the Process is therefore contained within the Pool and cannot cross the boundaries of the Pool. Message Flow can cross the Pool boundary to show the interactions that exist between separate private business processes.
Abstract (public) processes
This represents the interactions between a private business process and another process or participant. Only those activities that communicate outside the private business process are included in the abstract process. All other “internal” activities of the private business process are not shown in the abstract process. Thus, the abstract process shows to the outside world the sequence of messages that are required to interact with that business process. Abstract processes are contained within a Pool and can be modeled separately or within a larger BPMN Diagram to show the Message Flow between the abstract process activities and other entities. If the abstract process is in the same Diagram as its corresponding private business process, then the activities that are common to both processes can be associated.
Collaboration (global) processes
A collaboration process depicts the interactions between two or more business entities. These interactions are defined as a sequence of activities that represent the message exchange patterns between the entities involved. Collaboration processes may be contained within a Pool and the different participant business interactions are shown as Lanes within the Pool. In this situation, each Lane would represent two participants and a direction of travel between them. They may also be shown as two or more Abstract Processes interacting through Message Flow (as described in the previous section). These processes can be modeled separately or within a larger BPMN Diagram to show the Associations between the collaboration process activities and other entities. If the collaboration process is in the same Diagram as one of its corresponding private business process, then the activities that are common to both processes can be associated.

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):

  • High-level private process activities (not functional breakdown)*
  • Detailed private business process
  • As-is or old business process*
  • To-be or new business process
  • Detailed private business process with interactions to one or more external entities (or “Black Box” processes)
  • Two or more detailed private business processes interacting
  • Detailed private business process relationship to Abstract Process
  • Detailed private business process relationship to Collaboration Process
  • Two or more Abstract Processes*
  • Abstract Process relationship to Collaboration Process*
  • Collaboration Process only (e.g., ebXML BPSS or RosettaNet)*
  • Two or more detailed private business processes interacting through their Abstract Processes and/or a Collaboration Process

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

The weaknesses of BPMN could relate to:

  • ambiguity and confusion in sharing BPMN models
  • support for routine work
  • support for knowledge work, and
  • converting BPMN models to executable environments
  • support for business rules and decision-making

BPEL and BPMN

The BPMN specification includes an informal and partial 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 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.

See also

References

  1. ^ a b OMG. "BPMN 2.0". Retrieved 2011-03-29.
  2. ^ An XML Representation for Crew Procedures, Richard C. Simpson (2004), Final Report NASA Faculty Fellowship Program (Johnson Space Center)
  3. ^ Process Modeling Notations and Workflow Patterns Archived July 6, 2010, at the Wayback Machine, paper by Stephen A. White of IBM Corporation (2006)
  4. ^ Stephen A. White (3 May 2004). "Business Process Modeling Notation v1.0" (PDF). Archived from the original (PDF) on 18 August 2013. for the Business Process Management Initiative (BPMI)
  5. ^ OMG. "BPMN Working Draft" (PDF). Retrieved 2012-05-01.
  6. ^ "BPMN FAQ". Retrieved 2015-02-05.

Further reading

  • Grosskopf, Decker and Weske. (Feb 28, 2009). The Process: Business Process Modeling using BPMN. Meghan Kiffer Press. ISBN 978-0-929652-26-9.
  • Ryan K. L. Ko, Stephen S. G. Lee, Eng Wah Lee (2009) Business Process Management (BPM) Standards: A Survey. In: Business Process Management Journal, Emerald Group Publishing Limited. Volume 15 Issue 5. ISSN 1463-7154. PDF
  • Stephen A. White; Conrad Bock (2011). BPMN 2.0 Handbook Second Edition: Methods, Concepts, Case Studies and Standards in Business Process Management Notation. Future Strategies Inc. ISBN 978-0-9849764-0-9.

External links

BiZZdesign Enterprise Studio

BiZZdesign Enterprise Studio, formerly BiZZdesign Architect, is a visual modeling and design tool for Enterprise Architecture, that supports the application of ArchiMate and TOGAF, as well other enterprise architecture frameworks.

The platform supports the modelling, visualisation, analysis and documentation of enterprise architecture from different viewpoints and with multiple views. Additionally it supports the modeling business goals and requirements. It also supports automatic data collection, and can import data from office applications.BiZZdesign Enterprise Studio is developed by BiZZdesign and first released in 2004 as BiZZdesign Architect. Its development is based on the results of the ArchiMate project, and intends to offer a high value enterprise architecture modelling tool which business management itself can control. In 2012 it is recognized by Gartner and Forrester Research as one of the leading enterprise architecture tools.

Bizagi

Bizagi is a privately owned software company established in 1989 with headquarters in the UK, and offices in USA, Spain & Latin America. Its name is a portmanteau of "business" and "agility".The company designs and develops enterprise software for Business Process Management (BPM). Its three products form the Bizagi BPM Suite.

Business Process Definition Metamodel

The Business Process Definition Metamodel (BPDM) is a standard definition of concepts used to express business process models (a metamodel), adopted by the OMG (Object Management Group). Metamodels define concepts, relationships, and semantics for exchange of user models between different modeling tools. The exchange format is defined by XSD (XML Schema) and XMI (XML for Metadata Interchange), a specification for transformation of OMG metamodels to XML. Pursuant to the OMG's policies, the metamodel is the result of an open process involving submissions by member organizations, following a Request for Proposal (RFP) issued in 2003. BPDM was adopted in initial form in July 2007, and finalized in July 2008.

BPDM provides abstract concepts as the basis for consistent interpretation of specialized concepts used by business process modelers. For example, the ordering of many of the graphical elements in a BPMN (Business Process Model and Notation) diagram is depicted by arrows between those elements, but the specific elements can have a variety of characteristics. For example, all BPMN events have some common characteristics, and a variety of specific events are designated by the type of circle and the icon in the circle. The abstract BPDM concepts ensure implementers of different modeling tools will associate the same characteristics and semantics with the modeling elements to ensure models are interpreted the same way when moved to a different

tool. Users of the modeling tools do not need to be concerned with the abstractions—they only see the specialized elements.

BPDM extends business process modeling beyond the elements defined by BPMN and BPEL (Business Process Execution Language) to include interactions between otherwise-independent business processes executing in different business units or enterprises (choreography). A choreography can be specified independently of its participants, and used as a requirement for the specification of the orchestration implemented by a participant. BPDM provides for the binding of orchestration to choreography to ensure compatibility. Many current business process models focus on specification of executable business processes that execute within an enterprise (orchestration).

The BPDM specification addresses the objectives of the OMG RFP on which it is based:

BPDM "will define a set of abstract business process definition elements for specification of executable business processes that execute within an enterprise, and may collaborate between otherwise-independent business processes executing in different business units or enterprises."

Common metamodel to unify the diverse business process definition notations that exist in the industry containing semantics compatible with leading business process modeling notations.

A metamodel that complements existing UML metamodels so that business processes specifications can be part of complete system specifications to assure consistency and completeness.

The ability to integrate process models for workflow management processes, automated business processes, and collaborations between business units.

Support for the specification of web services choreography, describing the collaboration between participating entities and the ability to reconcile the choreography with supporting internal business processes.

The ability to exchange business process specifications between modeling tools, and between tools and execution environments using XMI.The RFP seeks to "improve communication between modelers, including between business and software modelers, provide flexible selection of tools and execution environments, and promote the development of more specialised tools for the analysis and design of processes."

For exchange of business process models, BPDM is an alternative to the existing process interchange format XPDL (XML Process Definition Language) from the WfMC (Workflow Management Coalition). The two specifications are similar in that they can be used by process design tools to exchange business process definitions. They are different in that BPDM provides a specification of semantics integrated in a metamodel, and it includes additional modeling capabilities such as choreography, discussed above. In addition, XPDL has many implementations, though only some support for XPDL 2.x, needed for interchanging BPMN. BPDM implementations are in preparation, including support for BPMN, and translation to XPDL.

Business Process Execution Language

The Web Services Business Process Execution Language (WS-BPEL), commonly known as BPEL (Business Process Execution Language), is an OASIS standard executable language for specifying actions within business processes with web services. Processes in BPEL export and import information by using web service interfaces exclusively.

Business Process Modeling Language

Business Process Modeling Language (BPML) is an XML-based language for business process modeling.

It was maintained by the Business Process Management Initiative (BPMI) until June 2005 when BPMI and OMG (Object Management Group) announced the merger of their respective Business Process Management (BPM) activities to form the Business Modeling and Integration Domain Task Force (BMI DTF)[1]. It is deprecated since 2008.

BPML was useful to OMG in order to enrich UML with process notation.

Business process automation

Business process automation (BPA), also known as business automation or digital transformation, is the technology-enabled automation of complex business processes. It can streamline a business for simplicity, achieve digital transformation, increase service quality, improve service delivery or contain costs. It consists of integrating applications, restructuring labor resources and using software applications throughout the organization. Robotic process automation is an emerging field within BPA and uses artificial intelligence.

Business process modeling

Business process modeling (BPM) in business process management and systems engineering is the activity of representing processes of an enterprise, so that the current process may be analysed, improved, and automated. BPM is typically performed by business analysts, who provide expertise in the modeling discipline; by subject matter experts, who have specialized knowledge of the processes being modelled; or more commonly by a team comprising both. Alternatively, the process model can be derived directly from events' logs using process mining tools.

The business objective is often to increase process speed or reduce cycle time; to increase quality; or to reduce costs, such as labour, materials, scrap, or capital costs. In practice, a management decision to invest in business process modeling is often motivated by the need to document requirements for an information technology project.

Change management programs are typically involved to put any improved business processes into practice. With advances in software design, the vision of BPM models becoming fully executable (and capable of simulations and round-trip engineering) is coming closer to reality.

Comparison of Business Process Modeling Notation tools

This article provides a comparison of Business Process Model and Notation (BPMN) tools.

Flowable

Flowable is an open-source workflow engine written in Java that can execute business processes described in BPMN 2.0. It is an actively maintained fork of Activiti (software).

Function model

A function model or functional model in systems engineering and software engineering is a structured representation of the functions (activities, actions, processes, operations) within the modeled system or subject area.

A function model, similar with the activity model or process model, is a graphical representation of an enterprise's function within a defined scope. The purposes of the function model are to describe the functions and processes, assist with discovery of information needs, help identify opportunities, and establish a basis for determining product and service costs.

List of BPEL engines

This is a list of notable Business Process Execution Language (BPEL) and Business Process Model and Notation (BPMN) engines.

List of BPMN 2.0 engines

This is a list of notable Business Process Model and Notation 2.0 (BPMN 2.0) Workflow Management Systems (WfMSs).

MetaDONE

MetaDONE is a software environment for creating domain-specific modeling languages (DSML). MetaDONE is developed by the PReCISE Research Center of the University of Namur (Belgium). It supports multi-level modeling and is fully bootstrapped. User-defined languages can have several concrete notations that are defined declaratively with the GraSyLa language. This framework proposes several modeling languages (Business Process Model and Notation (BPMN), User Requirements Notation (URN), Goal-oriented Requirements Language (GRL), Petri Net) that can be freely customized by the users.

Model-driven engineering

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing (i.e. algorithmic) concepts.

Object Management Group

The Object Management Group (OMG) is a computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a range of technologies.

Petri net

A Petri net, also known as a place/transition (PT) net, is one of several mathematical modeling languages for the description of distributed systems. It is a class of discrete event dynamic system. A Petri net is a directed bipartite graph, in which the nodes represent transitions (i.e. events that may occur, represented by bars) and places (i.e. conditions, represented by circles). The directed arcs describe which places are pre- and/or postconditions for which transitions (signified by arrows). Some sources state that Petri nets were invented in August 1939 by Carl Adam Petri—at the age of 13—for the purpose of describing chemical processes.

Like industry standards such as UML activity diagrams, Business Process Model and Notation and EPCs, Petri nets offer a graphical notation for stepwise processes that include choice, iteration, and concurrent execution. Unlike these standards, Petri nets have an exact mathematical definition of their execution semantics, with a well-developed mathematical theory for process analysis.

Unified Modeling Language

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–1995, with further development led by them through 1996.In 1997 UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005 UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then the standard has been periodically revised to cover the latest revision of UML.

Workflow Management Coalition

Workflow Management Coalition (WfMC) is a consortium formed to define standards for the interoperability of workflow management systems.

ISO standards by standard number
1–9999
10000–19999
20000+

This page is based on a Wikipedia article written by authors (here).
Text is available under the CC BY-SA 3.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.