Information Technology Reference
In-Depth Information
Process modeling compliance
Process modeling only needs to worry about the visual representation of the business pro-
cess to comply with that part of the BPMN 2.0 standard. This usually provides graphical
tools to draw/model business processes and collaboration diagrams. The specification
defines two types of business processes:
• Non-executable
• Executable
Modeling tools only need to model non-executable processes, but they can also add all the
details necessary to make the process definitions they create executable in different envir-
onments.
Non-executable processes are something to still take into account. In a sense, all processes
start as non-executable processes until all the details necessary for their proper execution
are added in a BPMS environment. Non-executable processes can also be very useful for
documentation, sketching, and as common ground to discuss the internal processes of an
organization.
If we want to model executable processes, the specification creates a subcategory (such as
a subclass) of this compliance type called Common Executable Conformance , covering
the minimum requirements for an execution environment for executable business pro-
cesses. These requirements are as follows:
• The data types and data models that will be related with our business processes
must be XML schemas
• The default service interfaces must be WSDL service definitions
• The default data access language must be XML Path Language ( XPATH ), a
query language used to select nodes from an XML
Of course, different vendors can decide how to cover these requirements—by changing
technology stacks on different points or adding new possible implementations. It is a good
point of comparison between vendors to see what features each vendor implements and
how they implement them.
Search WWH ::




Custom Search