Business Process Definition MetaModel (BPDM)

From Training Material
Revision as of 10:19, 21 November 2012 by Bernard Szlachta (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


title
Business Process Definition MetaModel (BPDM)
author
Bernard Szlachta (NobleProg Ltd)

Source: http://www.omg.org/cgi-bin/doc?dtc/08-05-10

What is BPDM ⌘

"framework for understanding and specifying the processes of an organization or community"

Why BPDM ⌘

  • Many methodologies (TQM, 6σ, BPR, BPM, etc..)
  • No common language between the methodologies
  • There are only "island" of technology, methodology or notation
  • BPDM allows to represent and model BP independent of notation or methodology
  • MOF
  • Transferring models between tools and notations


Orchestration vs Choreography ⌘

  • "Two sides of the same coin

Orchestration:

  • flow chart
  • under the authority of some entity
  • defined order

Choreography:

  • semi-independent and collaboration entities
  • each of entities has their own internal processes
  • captures interactions of rules

BPMN 2.0 and BPDM ⌘

  • BPMN 2.0 has its own metamodel
  • Since most of the vendors support BPMN 2.0 BPDM is not that important anylonger

Others ⌘

  • Tool vendors are the primary audience
  • Separating concerns: intended outcome of a processes from how that outcome is achieved
  • BPDM is technology independent
  • More reusability -> better Return on IT Investment

Procsess Concepts supported by BPDM ⌘

BPDM standardizes the underlying semantics, model and exchange mechanisms

  • All BPMN notation concepts
  • Processes, activities, tasks and sub-processes
  • Workflow
  • Sophisticated control of alternatives and parallel processes
  • Conditional execution paths
  • Signals and events
  • Time-based events and conditions
  • Events based on change in data or external conditions
  • Integration with rules and rules engines through event-based semantics
  • Process groups and swim-lanes
  • Transactions, rollback and compensation
  • Process data and data flow
  • Artifacts and artifact production and dependencies
  • A combination of human and automated process participants
  • Service Oriented Architectures and business services
  • Resource and entity selection
  • Roles, responsibilities & collaborations
  • Bi-directional and composite interactions between entities
  • Automated execution with MDA and process execution engines such as BPEL (See non-normative mapping to BPEL)
  • Interaction protocols, services and design by contract
  • Composite processes
  • UML activity, collaboration and interaction diagram concepts
  • Process specialization, derivation and refinement

Conformance ⌘

To Processes a Model Compliance:

  • Reading a BPDM model (MOF-2 XMI)
  • Writing a BPDM model (MOF-2 XMI)
  • Executing a model
  1. BPDM Full Compliance
  2. BPDM Collaboration Protocol Compliance
  3. BPDM Orchestration Process Compliance
  4. BPDM BPMN Compliance

See Also

http://www.omg.org/cgi-bin/doc?omg/08-06-32