Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Aphorismen
Applications
Business Economics & Admin.
My Computers
Cooking
Devices
Folders
Food
Hardware
Infos
Software Development
Sports
Operation Instructions
Todos
Test
Help
Glossary
Community portal
adaptions
Sidebar anpassen
Wiki RB4
Search
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
OMG OCEB BPM Technical Intermediate
(section)
Page
Discussion
English
Read
Edit
View history
Toolbox
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====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
Summary:
Please note that all contributions to Wiki RB4 may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Uwe Heuer Wiki New:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Toggle limited content width