SOA meets BPM


Published on

In this presentation I will explain the connection between the paradigm of the service-oriented architecture and business process management.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SOA meets BPM

  1. 1. SOA meets BPM Prof. Dr. Michael Grö 1
  2. 2. Structure• Learning targets• BPM (Business Process Management)• Why business agility is required today• What SOA claims and how SOA makes the agile business happen• Questions and discussions 2
  3. 3. Learning targets• You have a basic understanding about BPM and how companies use it• Get an idea how SOA can be part of the solution to create an agile company 3
  4. 4. BP(M)• What is a Business Process? – A business process is a collection of interrelated tasks, which accomplish a particular goal. – Focus on value for the customer – Elements: Activities and events – Different views: Functions, Data, Organization, …• In process-oriented organizations the business processes are the business.• So what about Business Process Management? 4
  5. 5. BPM = Business Process Management• BPM is a systematic approach for improving a companys business processes.• BEA: “BPM is a strategy for managing and improving business performance through continuous optimization of business processes in a closed-loop cycle of modeling, execution, and measurement.” 5
  6. 6. BPM• Why do companies apply BPM? – Try „ARIS TV – Episode 1 – Why do companies need BPM?”• Today for large companies: analysis and documentation of processes are standard – Complete loop complex and cost-intensive – Small and medium-sized enterprises (SME, german: KMU) do have a backlog 6
  7. 7. BPM• Practical application requires methods, policies, metrics, management practices, tools.• Business teams use specific tools, e.g. – eEPK / ARIS-Toolset, IDS Scheer – BPMN (Business Process Modeling Notation) as a growing standard 7
  8. 8. BPM, agile Business and IT• Increasing dynamic of business: customers, competitors, products• IT as an enabler for business• Demand for IT solutions, which can be adopted fast• Can IT meet these demands? – Today, process models often serve only as a starting point – In a lot of cases there is no full BPM loop 8
  9. 9. Process execution („the traditional way“)• Fully functional BPM requires not only modeling but execution, monitoring and analysis• Traditional IT-Systems implement the processes – Business Process and functionality build (almost) unbreakable rocks – Changes require IT-Skills and a (time-consuming) project – This is in opposition to business agility and the need for easily adoptable IT-systems 9
  10. 10. There is a promise …• SOA claims to provide IT-Systems that can be adopted fast to changing business processes• We need to explain: – What is SOA? – How does it work? – More flexibility through SOA 10
  11. 11. What is SOA?• Service-Oriented Architecture• Architectural style for it-infrastructure, development and management• All functionality is provided in distinct units, called services 11
  12. 12. What are Services in SOA?• Services give a specific (business-related) functionality• Independent of operating system and programming language• Distributed over the network• Combined together and reused to realize business processes• Extracted from existing applications or supplied by external organisations• Example: IT-related service: credit card check 12
  13. 13. How does it work? (Technology)• Source: BPMN-modeled processes – Model consist of 2 Views • Graphical Model • XML – XML-Document contains (web) service calls – Ideally: 1 Process activity suits 1 Service• Runtime Environment: Enterprise Service Bus (ESB) – Software that provides a lot of functionality – Proces-Engine to execute the process – Service repository includes all available services 13
  14. 14. How does it work? (Technology) Process Manager uses …Service Repository Source: 14
  15. 15. More flexibility through SOATraditional IT-Architecture Service-Oriented Architecture• Processes „hard-coded“ • Functionality in small, in software reusable pieces• Inflexible „Rock“-Model • Services can be• Change requires pro- rearranged easily (and gramming by IT-Staff deployed into ESB) by process designer (Orchestration) • „Stone“-Model 15
  16. 16. Finally: SOA meets BPM!• SOA greatly simplifies BPM implementations and is an excellent technical base for contineous business process improvement• Business and IT are growing together• “If an SOA provides roads to your information, then BPM is the car that leverages that infrastructure to accomplish something useful.” ment_BPM_?page=4#soa 16