Modeling Service Orchestrations with a Rule-enhanced Business Process Language


Published on

Presentation of a CASCON 2009 paper:

Business process modeling has been a promising direction in developing service compositions, including both service orchestrations and choreographies. This paper fully focuses on the problem of modeling service orchestrations. Despite many promising aspects of using business process modeling (BPM) languages for modeling service orchestrations, this paper aims to demonstrate that: i) best practices (workflow patters) for control flows (primary concern of service orchestrations) are not fully covered in present languages; ii) complete service compositions cannot be completely generated from business process models; and iii) BPM languages have limited support for representing logical expressions, business vocabularies, and business rules, which severely limits their flexibility and expressiveness. To address these challenges, we have integrated business rule mod-eling constructs of the REWERSE Rule Markup Language (R2ML) with the Business Process Modeling Notation (BPMN), resulting in our rBPMN proposal.

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

  • Be the first to like this

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

No notes for slide
  • BPMN -> OMG specification.
  • In the contingent requests pattern, a participant sends a request to another participant. If this second participant does not respond within a given period of time, the request is sent to another (third) participant. Again, if no response comes back, a fourth participant is contacted, and so on. For the decision about delayed responses, we propose using rule gateways with attached reaction rules. If a late (time-outdated) response from some earlier participant came during the processing of the contingent request (by a Pool 2 participant in Fig. 2), a reaction rules attached to the rule gateway R 1 decides if such a response should be accepted or not.
  • Modeling Service Orchestrations with a Rule-enhanced Business Process Language

    1. 1. Modeling Service Orchestrations with a Rule-enhanced Business Process Language Milan Milanović 1 , Dragan Gašević 2 , Gerd Wagner 3 , and Vladan Deved žić 1 1 University of Belgrade, Serbia 2 Athabasca University, Canada 3 Brandenburg University of Technology, Germany
    2. 2. Problem Domain <ul><li>Process modeling and service composition </li></ul><ul><ul><li>Orchestrations </li></ul></ul><ul><ul><ul><li>Business processes from one participant’s side </li></ul></ul></ul><ul><ul><li>Choreographies – MODELS 2009 </li></ul></ul><ul><ul><ul><li>Business processes from a global perspective </li></ul></ul></ul>
    3. 3. Orchestration Modeling <ul><li>Available languages (e.g., BPMN) </li></ul><ul><li>Challenges </li></ul><ul><ul><li>to support business vocabularies </li></ul></ul><ul><ul><li>to define message typing </li></ul></ul><ul><ul><li>to formalize a language for defining conditions </li></ul></ul><ul><ul><li>to support dynamic changes of business processes </li></ul></ul>MODELS 2009
    4. 4. <ul><li>Extension of BPMN </li></ul><ul><ul><li>building on the previous related work </li></ul></ul><ul><ul><ul><li>AORML [Taveter, 2004] </li></ul></ul></ul><ul><ul><li>adding support for vocabularies and rules </li></ul></ul><ul><ul><li>rules and business processes </li></ul></ul><ul><ul><ul><li>everything to be modeled by rules </li></ul></ul></ul><ul><ul><ul><li>hybrid approaches </li></ul></ul></ul><ul><ul><li>definition by metamodeling </li></ul></ul>Approach MODELS 2009
    5. 5. <ul><li>Rule-enhanced BPMN - rBPMN </li></ul><ul><ul><li>support for modeling orchestrations </li></ul></ul><ul><ul><li>evaluation mechanism – expressiveness </li></ul></ul><ul><ul><ul><li>workflow patterns </li></ul></ul></ul>Result MODELS 2009
    6. 6. BPMN Language MODELS 2009 Submission by BEA, IBM, SAP, and Oracle
    7. 7. <ul><li>REWERSE I1 Rule Markup Language </li></ul><ul><ul><li>with a UML-based graphical concrete syntax </li></ul></ul>Rule Modeling MODELS 2009
    8. 8. <ul><li>REWERSE I1 Rule Markup Language </li></ul>Extension for Rule Models MODELS 2009
    9. 9. Workflow Patterns <ul><li>Exclusive choice pattern </li></ul>MODELS 2009
    10. 10. Workflow Patterns <ul><li>Milestone pattern </li></ul>
    11. 11. EDOC 2009 On a customer book request, if the requested book is available and its quantity is > 0, send the book available message with book price. Otherwise, send a book not avilable message.
    12. 12. Book request scenario
    13. 13. Expressiveness comparison <ul><li>Workflow Patterns </li></ul>
    14. 14. <ul><li>Integration of rules and processes - rBPMN </li></ul><ul><li>Externalizing business logic in rules </li></ul><ul><li>Not a language for business analysts </li></ul><ul><ul><li>Intermediary between informal (PPT and visio) and technical (SoaML) </li></ul></ul><ul><li>Increases the level of agility </li></ul><ul><ul><li>service interaction and message exchange patterns </li></ul></ul>Conclusion MODELS 2009
    15. 15. Future Work <ul><li>Support for new class of agility of patterns </li></ul><ul><li>Additional scenarios for other types of rules </li></ul><ul><li>Verbalization of rules (SBVR) </li></ul><ul><li>Usability vs. expressivity </li></ul><ul><li>Transformations into extended BPEL </li></ul><ul><li>rBPMN model checking (e.g., mCRL2/mCRL) </li></ul>
    16. 16. Thank you! Questions?