Catalog of Business Modeling
and Management Specifications
This page provides a catalog of OMG business modeling
specifications that provide automated and interoperability support for Business
Process Management (BPM) and business modeling.
Specifications are listed alphabetically.
Description of Catalog Entries
Click
here
for a description of each field for specifications catalogued below.
Understanding Terms Used
In order to understand the various terms used to identify an OMG
specification as it moves through its editing cycles, consult the
OMG Specifications Tutorial.
| Specification Name: |
Business
Motivation Model (BMM) |
| Description: |
The Business
Motivation Model specification provides a scheme or structure for
developing, communicating, and managing business plans in an organized
manner. Specifically, the Business Motivation Model does all of the
following:
• It identifies factors that motivate the establishing of business
plans.
• It identifies and defines the elements of business plans.
• It indicates how all these factors and elements inter-relate.
Among these elements are those that provide
governance for and guidance to the business — Business Policies and
Business Rules. |
| Keywords: |
concept, enterprise, fact, fact type,
necessity, noun concept, verb concept |
| Latest / past specifications: |
|
Current version: 1.1 |
Past
versions: 1.0
|
|
| Related OMG Specifications: |
SBVR, UML
(non-normative), XMI |
| OMG Cross Reference: |
Domain
Specifications |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Business
Process Definition Metamodel (BPDM) |
| Description: |
BPDM provides
the capability to represent and model business processes independent of
notation or methodology, thus bringing these different approaches together
into a cohesive capability. This is done using a "meta model"1
– a model of how to describe business processes – a kind of shared
vocabulary of process with well defined connections between terms and
concepts. This meta model captures the meaning behind the notations and
technologies in a way that can help integrate them and leverage existing
assets and new designs. The meta model behind BPDM uses the OMG "Meta
Object Facility" (MOF) standard to capture business processes in this
very general way and to provide an XML syntax for storing and transferring
business process models between tools and infrastructures. Various tools,
methods and technologies can then map their way to view, understand and
implement processes to and through BPDM. |
| Keywords: |
activity,
actor, behavioral change, condition, happening, interaction, performer
role, part, process, protocol, step group, succession |
| Latest/past
specifications: |
|
Current version: 1.0 |
|
Past versions: n/a |
|
| Revision
Information: |
|
| Related OMG Specifications: |
MOF, XMI |
| OMG Cross Reference: |
Domain
Specifications |
| Most recent IPR
and Implementation questionnaire responses: |
|
|
| Specification Name: |
Business
Process Maturity Model (BPMM) |
| Description: |
BPMM is
intended for anyone interested or involved in improving an organization's
business process related to their products and services - whether the
products and services are for internal or external use. This includes
members of appraisal teams, members of process engineering groups,
managers, and professional staff. BPMM can be used as a process model by
itself or it can be used as a framework for improvement efforts based on
other models. |
| Keywords: |
adoption,
certification program, conformance, implementation, maturity model,
method. model-based, open standard, process, program, transactional |
| Latest / past specifications: |
|
Current version: 1.0 |
Past
versions: n/a
|
|
| Contact Information: |
|
| OMG Cross Reference: |
Domain
Specifications |
| Related Industry Standards: |
Control
OBjectives for Information and related Technology (COBIT);
Information Technology Infrastructure Library (ITIL); ISO-9000 |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Business
Process Model and Notation (BPMN) |
| Description: |
Business
people are very comfortable with visualizing business processes in a
flow-chart format. There are thousands of business analysts studying
the way companies work and defining business processes with simple
flow charts. This creates a technical gap between the format of the
initial design of business processes and the format of the languages,
such as BPEL4WS, that will execute these business processes. This gap
needs to be bridged with a formal mechanism that maps the appropriate
visualization of the business processes (a notation) to the
appropriate execution format (a BPM execution language) for these
business processes.
Interoperation of business processes at the human level, rather than
the software engine level, can be solved with standardization of the
Business Process Modeling Notation (BPMN). BPMN provides a Business
Process Diagram (BPD), which is a Diagram designed for use by the
people who design and manage business processes. BPMN also provides a
formal mapping to an execution language of BPM Systems (BPEL4WS).
Thus, BPMN provides a standard visualization mechanism for
business processes defined in an execution optimized business process
language.
NOTE: The OMG specification begins with
Version 1.1 as a previous 1.0 existed in industry.
|
| Keywords: |
activity,
abstract, arbitrary cycles, artifact, association, business analyst,
business process, case, choice, choreography, collaboration,
collapsed, compensation, compound, context, discriminator, event,
exception, flow, fork, implicit termination, join, lane, merge,
milestone, parent, participant, pool, process, result, sequence,
split, swimlane, synchronization, task, token, transaction, trigger |
| Latest / past specifications: |
|
| Practitioner
Certification: |
|
| Related OMG Specifications: |
UML
(non-normative) |
| OMG Cross Reference: |
Domain
Specifications |
| Related Industry Standards: |
BPEL4WS 1.1,
http://www.ebpml.org/bpel4ws.htm |
| Most
recent IPR and Implementation questionnaire responses: |
|
| Specification Name: |
Date-Time
Vocabulary (DTV) |
| Description: |
This document addresses two
different, but complementary, aspects of time:
Type 1:
Temporal noun concepts (such as time coordinate,
duration, calendar,
etc.) that model attributes of SBVR noun concepts, and temporal verb
concepts (such as time coordinate
is in the past, time interval1
is before time interval2,
time interval1
includes time interval2,
etc.) that model relationships between temporal noun concepts.
Type 2: Fact types that relate
situation models and occurrences
(such as a person being married to another person) to temporal concepts
(e.g., to a time interval). |
| Finalization
Information: |
|
Working Document - FTF Beta 1: TBD |
Working document: bmi/11-08-01 |
|
| |
|
|
| Specification Name: |
Production
Rule Representation (PRR) |
| Description: |
This
specification provides a standard production rule representation that is
compatible with rule engine vendors' definitions of production rules. It
can be used for interchange of business rules amongst rule modeling tools
(and other tools that support rule modeling as a function of some other
task). • It provides a standard production rule representation that is
readily mappable to business rules, as defined by business rule management
tool vendors. • It provides a standard production rule definition that
supports and encourages system vendors to support production rule
execution. • It provides an OMG MDA PIM model with a high probability of
support at the PSM level from the contributing rule engine vendors and
others, and can be included to add production rule capabilities to other
OMG metamodels. • It provides examples of how the OMG UML can be used to
support production rules in a standardized and useful way. • It provides
a standard production rule representation that can be used as the basis
for other efforts such as the W3C Rule Interchange Format and a production
rule version of RuleML. |
| Latest / past specifications: |
|
Current version: 1.0 |
Past
versions: n/a
|
|
| Revision
Information: |
|
| Related OMG Specifications: |
XMI |
| OMG Cross Reference: |
Domain Specifications |
| Most
recent IPR and Implementation questionnaire responses: |
|
| Specification Name: |
Semantics of Business
Vocabulary and Business Rules (SBVR) |
| Description: |
This specification defines
the semantics of business vocabulary, business
facts, and business rules; as well as an XMI schema for the interchange of
business vocabularies and business rules among organizations and between
software tools. |
| Keywords: |
business modeling, business vocabulary,
business rules |
| Latest / past specifications: |
|
Current version: 1.0 |
Past
versions: n/a
|
|
| Revision
Information: |
|
| Related OMG Specifications: |
BMM, CWM,
MOF, UML,
XMI |
| OMG Cross Reference: |
Domain Specifications |
| Related Industry Standards: |
BRML;
ORM;
OWL;
RDF;
RuleML;
SRML;
SWRL;
ISO: 1087-1,
704-2000, 10241, & 12620 Terminology; 11179 Metadata Registry;
12620 & 13250-2 Topic Maps; 13211 Prolog; 17115 Health Informatics
- Vocabulary for Terminological System; 24707 Common Logic; 2788 &
5964 Thesaurus;
ISO
N458 Topic Map Constraint Language |
| Most
recent IPR and Implementation questionnaire responses: |
|
| Specification Name: |
Workflow
Management Facility |
| Description: |
Standard
interfaces for workflow execution control, monitoring, and
interoperability between workflows defined and managed independently
of each other. The interfaces are based on a model of workflow
objects, which includes their relationships and dependencies with
requesters, assignments, and resources. |
| Domain: |
cross-domain |
| Keywords: |
business
object, pattern, process data, process enactment, process monitoring,
workflow |
| Latest / past specifications: |
|
| Contact Information: |
|
| OMG Cross Reference: |
Domain Specifications |
| Related Industry Standards: |
WfMC-TC-1003; WfMC-TC-1009;
WfMC-TC-1012; WfMC TC-1015 |
[ top ] [ Index Page
]
Edited by Linda on
April 12, 2013
|
|
