OMG OCEB BPM Technical Intermediate: Difference between revisions

Revision as of 12:12, 27 October 2014

OMG Certified Expert in BPM™ (OCEB™): Technical Intermediate

Official Literature, Coverage Map, ...
Local Folder C:\Uwes\Documents\Beruf\OCEB\OCEB Technical Intermediate

Books

Ronald G. Ross, Business Rule Concepts

Basic are:
- Semantics of Business Vocabularies and Business Rules (SBVR), standard released 2007 by the OMG
- RuleSpeak, Business Rule Solutions for expressing business rule notation for expressing business rules in structural natural language, one of three reference notations of SBVR
Fact Model:
- Structure given by Business Vocabulary
- the skeleton, is provided by basic noun concepts as represented by terms, and verb-ish connections (ligaments) between those noun concepts as represented by wordings
- every term needs requires a careful definition
- terms refer to classes rather than to instances
- fact types are the classes in the area of wordings (e.g. customer places order compared to Mr.Müller had placed order 1234)
Power, the muscless, is provided by processes, control by nerves, the Business Rules
- Rule Independence means seperating Business Rules from processes
- Rules are documented in the General Rulebook System (GRBS)
- Rules build directly on Fact Types
- Rules have to be declarative
- A Rule statement is also the guidance message used for business workers
- Business rule enable decision making

Papers

OCEB Definition of Business Process

OCEB_Definition_Of_Business_Process.pdf
6 different Definitions

Orchestration or Choreography?

Mike Rosen, BPTrends; 04-08-COL-BPMandSOA-OrchestrationorChoreography- 0804-Rosen v01 _MR_final.doc
difference between Orchestration and Choreography. First:
- Defines a single master controls of all aspects of a process (top-down approach)
- Supports a graphical view of the sequence
- Easily maps to SOA
- Is usually simpler to start with; but often harder to scale to more complex processes
- Is driven by the graphical sequence model, i.e. function follows form
- Represents the state-of-the-practice, and is supported by the majority of tools
There are currently two principle approaches to choreography,and workcomponent-based:
- message-based, define behaviors by exhaustively capturing the message contracts between collaborating parties, supported by the WS-CDL standard (Web Service Choreography Definition Language) and is often used for B2B applications
- The overall process behavior “emerges” from the working of its parts (bottom up). No global perspective is required
- Complex work processes are decomposed into work agendas where each autonomous element controls its own agenda
- Easily maps to event and agent based systems
- Is usually more difficult to start, but often easier to scale to complex processes
- Graphical representations can be derived from the process, i.e. form follows function
- Represents the state-of-the-art, and is gaining support with emerging tools

Starting the BPM Center of Excellence

Glenn Smith, Starting_the_BPM_COE_(Appian).pdf
Typical activities of a COE include:
- Defining BPM methodologies and best practices
- Providing reusable tools and templates
  - tools for configuration management and version control
- Ensuring consistency of BPM projects with applicable corporate standards
- Providing expertise in the use of the selected tools
  - providing proven approaches
- Providing guidance and performing reviews for all projects
Roles
- BPM executive sponsor
  - not from IT, but from Business
  - controls BPM budget
- Visionary
- Expert in the corperate infrastructure
- BPM tool specialist
- Business Analyst
- Tool developer

ebXML Business Process Specification Schema Technical Specification v2.0.4

ebxmlbp-v2.0.4-Spec-os-en.pdf
eBusiness eXtensible Markup Language (ebXML) defines a standard language by which business systems may be configured to support execution of Business Collaborations consisting of Business Transactions
The ebBP technical specification supports the specification of Business Transactions and the choreography of Business Transactions into Business Collaborations
A Choreography is an ordering of Business Activities within a Business Collaboration
The choreography is specified in terms of Business States, and transitions between those Business States.
When a transition is validated: it does not mean that the target Business Activity would start immediately, it means that the Business Activity is “enabled” and the initiating party MAY now send the request whenever appropriate, provided that it remains within the TimeToPerform of the Binary (Business) Collaboration
It is merely the execution of the backend systems, which instruct the BSI (Business Service Interface) to send or receive messages that advance the state of a collaboration
There is no execution engine associated to the collaboration itself.
The Business Collaboration is either in the state of performing a given Business Activity (or multiple concurrent Business Activities) or waiting to start a Business Activity, unless it has reached a completion state
Once a Business Activity completes a transition from this Business Activity, it navigates to another Business Activity
A business message initiates a Business Collaboration or advances its state

Workflow Patterns

BPM-06-22 Workflow Patterns Revised.pdf
- see here

SLAs: A CIO's Guide to Success

Source
Penalties and rewards
focus on consumables that are consumed
Simple is hard
clear relation between cost and level of support
ask for expectations and set expectations
variable areas with resource pools
ties SLAs to variable component of staff salaries
devide SLA into performance level (e.g. basic, enhanced, premium)
automate SLA performance
99% average availability hide outage of critical application at an important time
more business oriented SLAs:
- measuring what is possible might not be what is needed e.g. for a call-center operations measuring availability of servers, applications, desktops will not measure processes or capacity => research on vital data, select the right layer e.g. application availability is more important than networt or server availability
- definition in business terms, but be careful because what you can't measure you can't manage
- put someone in charge for end-to-end
- revisit SLAs

Establishing Service Level Agreements

by Naomi Karten

Specifications

OMG, Business Process Definition Metamodel; dtc-08-05-10 BPDM BusinessProcessDefinitionMetamodel.pdf
- Framework for understanding and specifying the processes of an organization or community
- Reason
  - Many methodologies (TQM, 6σ, BPR, BPM, etc..)
  - No common language between the methodologies
  - There are island of technology, methodology or notation
  - BPDM allows to represent and model BP independent of notation or methodology
- Provides the capability to represent and model business processes independent of notation or methodology, done by using a meta model
- uses the OMG Meta Object Facility (MOF) to provide an XML syntax for storing and transferring business process models
- supports two fundamental and complementary views: orchestration and choreography
  - 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
  - Procsess Concepts supported by BPDM*****
    - 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
OASIS; ebXML Business Process Specification; ebxmlbp-v2.0.4-Spec-os-en.pdf

@@ Line 9: / Line 9: @@
 ** Semantics of Business Vocabularies and Business Rules (SBVR), standard released 2007 by the OMG
 ** RuleSpeak, Business Rule Solutions for expressing business rule notation for expressing business rules in structural natural language, one of three reference notations of SBVR
-* A business is very much like a body - a living organism:
 * Fact Model:
 ** Structure given by '''Business Vocabulary'''
@@ Line 16: / Line 15: @@
 ** terms refer to classes rather than to instances
 ** '''fact types''' are the classes in the area of wordings (e.g. customer places order compared to Mr.Müller had placed order 1234)
-* Power, the muscless, is provided by processes
+* Power, the muscless, is provided by processes, control by nerves, the Business Rules
-* Control and coordination, the nerves, are provided by business rules
+** '''Rule Independence''' means seperating Business Rules from processes
+** Rules are documented in the General Rulebook System (GRBS)
+** Rules build directly on Fact Types
+** Rules have to be declarative
+** A Rule statement is also the guidance message used for business workers
+** Business rule enable decision making
 ===Papers===