Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enterprise SOA Chapter 7 (PPT)- Mohammed Syed


Published on

  • Be the first to comment

  • Be the first to like this

Enterprise SOA Chapter 7 (PPT)- Mohammed Syed

  1. 1. SOA and Business Process Management Mohammed Syed
  2. 2. Introduction to BPM <ul><li>BPM is a general management topic </li></ul><ul><li>Focuses on the strategic and operational aspects of process orientation in a given business area </li></ul><ul><li>Builds on and transforms that which already exists unlike BPR </li></ul><ul><li>Recommends incremental change and evolutionary optimization </li></ul>
  3. 3. Introduction to BPM <ul><li>Predecessors: </li></ul><ul><ul><li>Total Quality Management, late 1980s </li></ul></ul><ul><ul><li>Business Process Reengineering, early 1990s </li></ul></ul><ul><ul><ul><li>BPR completely reinvents the existing business processes </li></ul></ul></ul><ul><ul><ul><li>Possible Reasons of Reengineering Efforts’ High Failure Rates: </li></ul></ul></ul><ul><ul><ul><ul><li>Resistance to change </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Lack of Understanding of the business models </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Failure of nerve on the part of the client companies </li></ul></ul></ul></ul>
  4. 4. Two sides of BPM <ul><li>Business side: </li></ul><ul><ul><li>Accompanied by keywords such as ISO 9000 and Six Sigma </li></ul></ul><ul><li>IT Side: </li></ul><ul><ul><li>Accompanied by keywords such as process modeling and workflow management </li></ul></ul>
  5. 5. BPMS <ul><li>Business Process Management System </li></ul><ul><ul><li>Provides the technical platform for realizing BPM management initiatives </li></ul></ul><ul><li>Includes: </li></ul><ul><ul><li>BPM Engine </li></ul></ul><ul><ul><li>Facilities for business process monitoring </li></ul></ul><ul><ul><li>Design tools </li></ul></ul><ul><ul><li>Facilities for simulation </li></ul></ul>
  6. 6. BPMS <ul><li>Typical high level features encompass the discovery, design, and deployment of business processes, as well as the executive, administrative and supervisory control over them to ensure that they remain compliant with business objectives </li></ul>
  7. 7. BPMS, When and Why <ul><li>IT and Business must work hand in hand </li></ul><ul><ul><li>BPMS widely accepted at both the business and technological levels if: </li></ul></ul><ul><ul><ul><li>An enterprise has defined and documented key business processes </li></ul></ul></ul><ul><li>Utilize Process Templates </li></ul><ul><ul><li>BPM concepts are about incremental changes so using pre-defined process templates can be extremely valuable </li></ul></ul>
  8. 8. BPMS, When and Why <ul><li>Matching the Right Technology </li></ul><ul><ul><li>Understand the business process </li></ul></ul><ul><ul><li>Key Characteristics: </li></ul></ul><ul><ul><ul><li>Complexity, dynamism, degree of coordination required by the process </li></ul></ul></ul><ul><li>Adopting the development Model </li></ul><ul><ul><li>BPM platform provides a complete software development model that enforces a clean separation between business logic and low-level technical code </li></ul></ul>
  9. 9. Overview of a BPM System <ul><li>Modeling Languages </li></ul><ul><ul><li>Two most popular approaches: </li></ul></ul><ul><ul><ul><li>Business Process Execution Language for Web Services (BPEL4WS) </li></ul></ul></ul><ul><ul><ul><li>Business Process Modeling Language (BPML) </li></ul></ul></ul><ul><ul><ul><li>Business Process Modeling Notation (BPMN) is a language that supports standardized graphical representation of business process diagrams, similar to the UML approach </li></ul></ul></ul>
  10. 10. Overview of a BPM System <ul><li>Architecture of a BPM System </li></ul><ul><ul><li>Usually modeled graphically using based on BPMN notation stored in a block structured model (e.g., in BPEL4WS or BPML) </li></ul></ul><ul><ul><li>Process Engine creates and interprets runtime instances of formal process definitions </li></ul></ul><ul><ul><li>Process definitions and process instances are stored in repositories </li></ul></ul><ul><ul><li>System provides interfaces to design, deploy, and configure process definitions and to monitor and manage process instances </li></ul></ul>
  11. 11. BPM Vision <ul><li>Information and rules regarding important business processes are taken out of the application systems and are put under the control of a BPM System </li></ul><ul><li>BPM System facilitates the modification, reconfiguration, and optimization of process definitions with graphical tools that can be used by less technology-oriented business analysts </li></ul>
  12. 12. BPM and Process Enabled SOA <ul><li>The Emergence of SOA: The Past </li></ul><ul><ul><li>Data and Functionality were separated in the early days of programming </li></ul></ul><ul><ul><li>Object Orientation merged data and functionality into encapsulated, reusable object implementations </li></ul></ul><ul><ul><li>Object Orientation had severe limitations when distributed object technology was applied to large-scale projects </li></ul></ul><ul><ul><li>SOA emerged as a result with supporting platforms such as XML Web Services </li></ul></ul>
  13. 13. BPM and Process Enabled SOA <ul><li>Core Business Logic vs Process Control Logic: The Future </li></ul><ul><ul><li>Core business logic comprises basic data access services, complex calculations, and complex business rules </li></ul></ul><ul><ul><li>Process Control Logic deals with dynamic processes that are prone to frequent change and often require complex coordination with the process participants </li></ul></ul>
  14. 14. BPM and Process Enabled SOA <ul><li>Benefits of separating CBL and PCL are manifold </li></ul><ul><ul><li>Increases agility </li></ul></ul><ul><ul><li>Smooth Changes to existing processes and smooth introduction of new ones </li></ul></ul><ul><ul><li>Changing one process does not affect another process </li></ul></ul><ul><ul><li>Redundancies and Inconsistencies are reduced </li></ul></ul>
  15. 15. Design Implications for SOA Architects <ul><li>The Challenge: </li></ul><ul><ul><li>Identify and categorize services that represent core business logic and those that represent process control logic </li></ul></ul><ul><li>Aspects to be considered: </li></ul><ul><ul><li>Business and Process Requirements </li></ul></ul><ul><ul><li>The Existing Application Landscape </li></ul></ul><ul><ul><li>Make-vs-Buy Decisions </li></ul></ul><ul><ul><li>Resource Availability </li></ul></ul><ul><ul><li>SOA Design Considerations </li></ul></ul><ul><ul><li>Budget Constraints </li></ul></ul>