Milan Milanović 1  and  Dragan Gašević 2   1 University of Belgrade, Serbia 2 Athabasca University, Canada Towards a Langu...
<ul><li>Connecting process models and vocabularies </li></ul><ul><li>Effective updates of process models </li></ul><ul><li...
Approach <ul><li>Language that combines  business rules and business processes </li></ul><ul><li>Following model-driven en...
<ul><li>Background </li></ul><ul><li>Rule-enhanced BPMN </li></ul><ul><ul><li>BPMN language and metamodel </li></ul></ul><...
Background <ul><li>Business processes </li></ul><ul><ul><li>Coordinated set of activities </li></ul></ul><ul><ul><li>Busin...
Background <ul><li>Business rules </li></ul><ul><ul><li>“ A statement that defines or constraints some aspect of the busin...
Background <ul><li>Business processes and business rules </li></ul><ul><ul><li>Fully rule-based </li></ul></ul><ul><ul><ul...
Goal <ul><li>Systematic definition of  a rule-based business modeling language </li></ul>
Rule-enhanced BPMN <ul><li>MDE as a solution  </li></ul><ul><ul><li>Language engineering with metamodeling </li></ul></ul>...
<ul><li>Modeling elements </li></ul><ul><ul><li>Flow object </li></ul></ul><ul><ul><li>Connecting objects </li></ul></ul><...
<ul><li>Business Process Model and Notation (BPMN) Specification 2.0, initial submission,  </li></ul><ul><li>http://www.om...
<ul><li>REWERSE I1 Rule Markup Language </li></ul><ul><ul><li>Four rule types </li></ul></ul><ul><ul><li>Organization </li...
R2ML Metamodel EDOC 2009
URML Details <ul><li>Extension of UML for rule modeling </li></ul><ul><li>Vocabularies by using UML class models  </li></u...
EDOC 2009 On a patient information request,  if the user is registered and provided valid credentials,  retrieve the reque...
rBPMN Metamodel EDOC 2009
rBPMN metamodel EDOC 2009
<ul><li>Activity extensions: Tasks and Subprocesses </li></ul>rBPMN metamodel EDOC 2009
<ul><li>rBPMN data model:  Correlation information </li></ul>rBPMN Metamodel EDOC 2009
<ul><li>Service-oriented health information system </li></ul><ul><li>Message Exchange Patterns </li></ul><ul><ul><li>Types...
<ul><li>In-Out MEP (with fault replaces message) </li></ul>Message Exchange Patterns EDOC 2009
 
<ul><li>Out-In Pattern (with fault) </li></ul>Message Exchange Patterns EDOC 2009
Related Work
Conclusion <ul><li>Integration of rules and processes </li></ul><ul><li>Supported patterns by Graml et al. </li></ul><ul><...
Future Work <ul><li>Workflow and service-interaction patterns </li></ul><ul><li>Mapping onto and extending BPEL </li></ul>...
Thank You !
Upcoming SlideShare
Loading in …5
×

Towards a Language for Rule-enhanced Business Process Modeling

1,339 views
1,238 views

Published on

Presentation of the EDOC 2009 paper:

Business process modeling is a commonly used approach in the development of service-oriented architectures. The previous research on this topic demonstrated that process-oriented models might be too rigid for dynamic adaptations of the business logic. Rule-based approaches are considered an alternative, which offers more flexibility thanks to the declarative nature of rules and their underlying reasoning algorithms. However, modeling a business process through rules is a tedious process for developers in terms of the overall business process comprehension. In this paper, we propose a hybrid solution – a modeling language that integrates both rule- and process-oriented modeling perspectives. The language (Rule-based BPMN –rBPMN) is based on the integration of the Business Process Modeling Notation with the REWERSE Rule Markup Language. In this paper, after introducing rBPMN, we report on the experience in modeling of Service-Oriented Architectures (SOA) from the perspective of message exchange patterns.

http://dx.doi.org/10.1109/EDOC.2009.12

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,339
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
45
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Context R2MLMessageType R2MLMessageType.allInstances()-&gt;forAll(p1, p2 | p1 &lt;&gt; p2 implies p1.structure.type &lt;&gt; p2.structure.type)
  • In-Out pattern consists of exactly two messages: a message received by a service (i.e., input message) from some other node, followed by a message (i.e., output message) sent to the other node The second message may be replaced by a fault as specified in the &amp;quot;Fault Replace Message&amp;quot; model
  • Towards a Language for Rule-enhanced Business Process Modeling

    1. 1. Milan Milanović 1 and Dragan Gašević 2 1 University of Belgrade, Serbia 2 Athabasca University, Canada Towards a Language for Rule-enhanced Business Process Modeling
    2. 2. <ul><li>Connecting process models and vocabularies </li></ul><ul><li>Effective updates of process models </li></ul><ul><li>Smaller chunks of business logic in processes </li></ul><ul><li>Visualizing business logic exchange </li></ul>Motivation EDOC 2009
    3. 3. Approach <ul><li>Language that combines business rules and business processes </li></ul><ul><li>Following model-driven engineering </li></ul><ul><li>Evaluation on message exchange patterns </li></ul>EDOC 2009
    4. 4. <ul><li>Background </li></ul><ul><li>Rule-enhanced BPMN </li></ul><ul><ul><li>BPMN language and metamodel </li></ul></ul><ul><ul><li>R2ML language and metamodel </li></ul></ul><ul><ul><li>rBPMN language and metamodel </li></ul></ul><ul><li>Case study </li></ul><ul><ul><li>Message Exchange Patterns </li></ul></ul><ul><li>Conclusion and future work </li></ul>Outline EDOC 2009
    5. 5. Background <ul><li>Business processes </li></ul><ul><ul><li>Coordinated set of activities </li></ul></ul><ul><ul><li>Business goals </li></ul></ul><ul><ul><li>Model: activities, participants, organizational structures, goals, policies, and vocabularies </li></ul></ul><ul><ul><li>Model perspectives </li></ul></ul><ul><ul><ul><li>Control flow, data flow, interaction, … </li></ul></ul></ul><ul><ul><li>BPMN language </li></ul></ul>
    6. 6. Background <ul><li>Business rules </li></ul><ul><ul><li>“ A statement that defines or constraints some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business.” </li></ul></ul><ul><ul><li>BRG, 2009 </li></ul></ul><ul><li>Types [Wanger, 2005] </li></ul><ul><ul><li>Derivation, integrity, production, and reaction </li></ul></ul><ul><li>Standardization efforts: RIF, SBVR, and PRR </li></ul>
    7. 7. Background <ul><li>Business processes and business rules </li></ul><ul><ul><li>Fully rule-based </li></ul></ul><ul><ul><ul><li>Reaction and production rules </li></ul></ul></ul><ul><ul><ul><ul><li>Comprehension </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Execution flow at run-time </li></ul></ul></ul></ul><ul><ul><ul><ul><li>No support for different rules & low-level representation </li></ul></ul></ul></ul><ul><ul><li>Hybrid approaches </li></ul></ul><ul><ul><ul><li>Graml et al., 2007: control flow decisions, data constraints, process composition </li></ul></ul></ul>
    8. 8. Goal <ul><li>Systematic definition of a rule-based business modeling language </li></ul>
    9. 9. Rule-enhanced BPMN <ul><li>MDE as a solution </li></ul><ul><ul><li>Language engineering with metamodeling </li></ul></ul><ul><ul><li>Business process and rule (meta)models </li></ul></ul><ul><ul><ul><li>Integration on the level of the metamodels </li></ul></ul></ul><ul><ul><ul><li>Validity of expressions in models </li></ul></ul></ul><ul><ul><li>Integration of BPMN and R2ML languages </li></ul></ul>EDOC 2009
    10. 10. <ul><li>Modeling elements </li></ul><ul><ul><li>Flow object </li></ul></ul><ul><ul><li>Connecting objects </li></ul></ul><ul><ul><li>Pools </li></ul></ul>BPMN Language EDOC 2009
    11. 11. <ul><li>Business Process Model and Notation (BPMN) Specification 2.0, initial submission, </li></ul><ul><li>http://www.omg.org/cgi-bin/doc?bmi/08-02-06 , 2008 </li></ul>BPMN Metamodel EDOC 2009
    12. 12. <ul><li>REWERSE I1 Rule Markup Language </li></ul><ul><ul><li>Four rule types </li></ul></ul><ul><ul><li>Organization </li></ul></ul><ul><ul><ul><li>R2ML MOF-based metamodel for rules </li></ul></ul></ul><ul><ul><ul><li>R2ML XML Schema </li></ul></ul></ul><ul><ul><ul><li>UML-based Rule Modeling Language (URML) </li></ul></ul></ul><ul><ul><ul><li>Transformations </li></ul></ul></ul>Rule Modeling Language Towards a Language for Rule-enhanced Business Process Modeling EDOC 2009
    13. 13. R2ML Metamodel EDOC 2009
    14. 14. URML Details <ul><li>Extension of UML for rule modeling </li></ul><ul><li>Vocabularies by using UML class models </li></ul><ul><ul><li>Rules are defined on top of such models </li></ul></ul>EDOC 2009
    15. 15. EDOC 2009 On a patient information request, if the user is registered and provided valid credentials, retrieve the requested information and notify the user. Otherwise, send a fault message.
    16. 16. rBPMN Metamodel EDOC 2009
    17. 17. rBPMN metamodel EDOC 2009
    18. 18. <ul><li>Activity extensions: Tasks and Subprocesses </li></ul>rBPMN metamodel EDOC 2009
    19. 19. <ul><li>rBPMN data model: Correlation information </li></ul>rBPMN Metamodel EDOC 2009
    20. 20. <ul><li>Service-oriented health information system </li></ul><ul><li>Message Exchange Patterns </li></ul><ul><ul><li>Types and order of messages </li></ul></ul><ul><ul><li>Inbound patterns </li></ul></ul><ul><ul><ul><li>Initiated by service requestors </li></ul></ul></ul><ul><ul><li>Outbound patterns </li></ul></ul><ul><ul><ul><li>Initiated by services themselves </li></ul></ul></ul><ul><li>MEPs modeled by reaction rules </li></ul>Case Study EDOC 2009
    21. 21. <ul><li>In-Out MEP (with fault replaces message) </li></ul>Message Exchange Patterns EDOC 2009
    22. 23. <ul><li>Out-In Pattern (with fault) </li></ul>Message Exchange Patterns EDOC 2009
    23. 24. Related Work
    24. 25. Conclusion <ul><li>Integration of rules and processes </li></ul><ul><li>Supported patterns by Graml et al. </li></ul><ul><li>Visualization for rule interchange </li></ul><ul><li>Verification of shared rules </li></ul>EDOC 2009
    25. 26. Future Work <ul><li>Workflow and service-interaction patterns </li></ul><ul><li>Mapping onto and extending BPEL </li></ul><ul><li>Structured natural language for rules </li></ul><ul><li>Policies with business processes </li></ul>EDOC 2009
    26. 27. Thank You !

    ×