IASA Perspective on BPM+SOA, Kuala Lumpur, 2008

1. Emerging SOA + BPM Standards,
Software and Platforms
Date 10/03/2008
Credit Suisse, Tarmo Ploom
Final Version

2. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 2

3. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 3

4. Emergence of SOA, 1
Is SOA something new?
UNIX kernel of 1970's with clear application programming interface (API)?
Desktop applications of 1980's in which presentation logic was separated
from
client business logic by an API?
Enterprise Application Integration (EAI) of 1990s?
Definitions
Service-Oriented Architecture (SOA) is an architectural style that supports
service orientation (Open Group)
Service orientation is a way of thinking in terms of services and service-
based
development and the outcomes of services (Open Group)
Service
Is a logical representation of a repeatable business activity that has a
specified outcome (Open Group)
Is a “black box” to consumers of the service (Open Group)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 4

5. Emergence of SOA, 2
SOA is architectural style
SOA is based on the design of services – which mirror real-world business
activities – comprising the enterprise (or inter-enterprise) business
processes (Open Group).
SOA is a way to describe logical architecture
Every technology can be used as basis for SOA
There have always been interfaces but designing of services, which reflect
real-world business activities is relatively new
SOA places unique requirements on the infrastructure – it is
recommended that implementations use open standards to realize
interoperability and location transparency (Open Group).
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 5

6. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 6

7. Service description, convergence of standards
Development of service description languages = development of abstraction
1980s
proprietary service definition languages (C, C++, PL1, COBOL)
proprietary socket based transport protocols
abstraction on Platform Specific Model (OMG) level
1990s
IDL, standardized interface definition language (OMG)
standardized transport protocol IIOP (OMG)
abstraction on Platform Independent Model (OMG) level
2000s
WS-family, standardized service definition language
standardized message exchange patterns => transport and definition decoupled
abstraction on slightly higher level than Platform Independent Model (OMG)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 7

8. Service description, message exchange patterns
Classification of services in OMG IDL
synchronous (request-response, in-out)
asynchronous (fire-and-forget or notification or out-only)
Additions in W3C WSDL 1.0
+ solicit-response operation
+ one-way operation (in-only)
Additions in W3C WSDL 2.0
+ out-in pattern
+ robust in-only pattern
+ robust out-only pattern
+ in-optional-out pattern
+ out-optional-in pattern
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 8

9. Service description, WS-family
Business process related
WS-BPEL (BPEL) – executable process definition
WS-Coordination – context management for BPEL
WS-BusinessActivity – long term business activities
WS-AtomicTransaction – classical ACID transactions
WS Extensions
WS-Adressing - standardize representation of service endpoint locations
WS-ReliableMessaging – guaranteed delivery of SOAP messages
WS-Policy – express metadata about security, processing, content
WS-MetadataExchange – standardizes service description metadata exchange
WS-Security – end-to-end security, authentication, authorization
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 9

10. Service description, semantic interoperability
We have achieved technical interoperability
But did we achieve semantic interoperability?
Do clients understand service providers?
SAP integration projects
10% effort technology
90% semantic understanding
How to achieve semantic interoperability?
Glossaries
BOM – Business Object Model
Industry standardizations (insurance, telecom,
banking)
OWL – Web Ontology Language
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 10

11. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 11

12. SOA technology, focus on ESB
Definition
ESB is a new architecture that exploits Web services, messaging middleware,
intelligent routing, and transformation (Roy Schulte)
ESB is convergence of current middleware technologies which involves
WS-family standards
Message exchange patterns
Message transformation/routing
Orchestration
....
Future
Forrester suggests convergence
between ESB and system-to system integration
BPM engines (Forrester Research)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 12

13. SOA technology, ESB and beyond
Limits of ESB
Does ESB support high transaction volume platform (> 1 Million Tx/hour)?
Does ESB support bulk data transfer (> 100 MB)?
Latency in international SOA?
Scalability issues?
Complexity ad manageability of solutions?
Our cognitive limits to handle complexities in ESB-s?
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 13

14. SOA technology, future is open
Service Integration Maturity Model (Ali Arsanjani )
Level one – ad hoc integration
Level two – Enterprise Application Integration (EAI) with proprietary connectors
Level three – componentization of existing landscapes, integration of components
through their interfaces
Level four – organization starts to define and expose SOA services internally or
for business partners
Level five – organization extends its influence to value chain
Level six – organization creates virtualized infrastructure to run applications.
Decoupling of applications, its services, components and processes
Level seven – organization has dynamically reconfigurable software architecture.
It can compose services at run-time using externalized policy description,
management and monitoring
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 14

15. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 15

16. Emergence of BPM
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 16

17. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 17

18. Business process classification
Predefined versus non-predefined processes
Integration versus human interaction oriented
Intra company versus Inter company processes
Collaboration versus document oriented processes
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 18

19. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 19

20. Process definition languages, overview
(Michael zur Muehlen)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 20

21. Process definition languages, convergence
(Martin Bartonitz, modified)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 21

22. Process definition languages, example FDL
Proprietary versus standard process definition language, comparison based on
workflow patterns
(Axel Glaser)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 22

23. Process definition languages, future is open
Developments by orchestration standards
BPEL4BPEL: BPEL for people
BPEL-SPE: extension for sub processes
Developments by choreography standards
WS-CDL – Web Services Choreography Description language
Standards are still evolving
Expect changes in process definition standards
Accept proprietary vendor extensions
Require mapping of processes definitions to Business Process Modeling
Meta-model
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 23

24. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 24

25. BPM technology, convergence
(Michael zur Muehlen)
Produced by: Tarmo Ploom
CREDIT SUISSE Private Banking Date: 06/09/2009 Slide 25

26. BPM technology, emergence of BPM suites
(Forrester Research)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 26

27. BPM technology, future is open
Structured processes platform
Human workflow and process orchestration platforms have matured
Human workflow and process orientation will probably converge into
one structured processes platform
Ad hoc workflow platform
Collaborative platforms are in development phase
Semi-structured workflow platforms are more mature then collaboration
platforms
Inter company workflow platform
These platforms are still in the R&D phase
Importance of this platform will grow in future with increase of supply chain
automation
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 27

28. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 28

29. SOBA - Service Oriented Business Applications, definitions
Gartner calls them "SOBA"
Service Oriented Business Applications (SOBAs) will enable enterprises to
dynamically compose and decompose applications according to business
needs
Forrester calls them "Dynamic Applications"
Dynamic applications — software that adds more visibility and collaboration
to today's business processes, while adapting more quickly and cost-effectively
to their changes — represent IT's worthiest hope for enabling real business agility.
Aberdeen Group calls them "Composite Applications"
Composite apps, logic and data collected from multiple IT sources, harnessed with
web services standards, are rapidly becoming the development standard of choice
in all IT organizations.
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 29

30. SOBA - Service Oriented Business Applications, vision
Definition
Highly agile, highly flexible business applications, which can be dynamically
composed by business specialists
Precondition
Library of existing software assets (SOA services + business processes), which
can dynamically composed into applications based on business needs
Elements of software product lines approach (SEI)
Impact
Programming on very high abstraction level
Higher focus on business architecture
More emphasis on MDA to transform
Transformation of code centric development processes to model centric
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 30

31. SOBA - Service Oriented Business Applications, vision
SOBA meets MDA
Conventional programming is on the
MDA
Code level
MDAAbstraction levels
CIM
In MDA usually we dream about MDA
programming on the PIM level PIM
In SOBA we dream about programming MDA
on CIM level PSM
Dream about programming on the CIM MDA
(Computing Independent Model) level Code level
SOBA meets SOA and BPM
Dream that business customers can themselves compose executable
business processes from library of business services and executable
business processes
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 31

32. SOA and BPM based application architectures
Increase flexibility, increase time to market, increase agility
Thomas Erl, Service-Oriented Architecture: Concepts, Technology, and Design
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 32

33. Agenda
Emergence of SOA
Service description
SOA technology
Emergence of BPM
Classification of process types
Process definition languages
BPM technology
SOBA - Service Oriented Business Applications
SOBA development paradigms
Questions
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 33

34. SOBA development paradigms, tradition
Traditional SOA + BPM
Hard coded service bindings
Process change requires model change, reassembly & deployment
Difficult to handle variations in process definitions
Business Process
Services: A A A B B C C
Service Bus Registry
(IBM slide used)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 34

35. SOBA development paradigms, future?
SOBA
loosely coupled service bindings
use business rules to select appropriate service and handle process
variability
Business Process
Services: A A D D
End Points: a1 a2 d1 d2
Business Services: B C
Business Services Dynamic Assembler
End Points: b1 b2 b3 c1 c2 c3 c4 ……. N
Service Bus Registry (IBM slide used)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 35

36. SOBA development paradigms, long journey
SOBA-s combine following approaches:
SOA BR
BPM
Business rules SOA SOBA BPM
MDA
MDA
Before starting with SOBA-s enterprise level high maturity SOA, BPM and
Business Rules implementations have to be in place
SOBA-s leverage results of long term SOA, BPM and Business Rules
investments
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 36

37. Questions?
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 37

38. References
1. Ali Arsanjani and Kerrie Holley, Increase flexibility with the Service
Integration Maturity Model, 30.09.2005, IBM developerWorks
2. Roy Schulte, 2003, Predicts 2003: Enterprise Service Buses Emerge,
Gartner
3. Thomas Erl, 2005, Service-Oriented Architecture: Concepts, Technology,
and Design
4. Michael zur Muehlen: Workflow-based Process Controlling. Foundation,
Design, and Implementation of Workflow-driven Process Information Systems.,
Bd. 6 von Advances in Information Systems and Management Science, Logos,
Berlin, 2004, ISBN 3-8325-0388-9.
5. Martin Bartonitz: Wachsen die BPM- und Workflow-Lager zusammen?, 2006,
http://www.bpm-guide.de/articles/66 (2007-08-16)
Produced by: Tarmo Ploom
Date: 06/09/2009 Slide 38