Towards Service-based Business Process Modeling, Prototyping and Integration


Published on

Rapid Integration of Software Engineering techniques workshop. 8-9 September, 2005. Heraklion Crete, GREECE

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

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

No notes for slide
  • Towards Service-based Business Process Modeling, Prototyping and Integration

    1. 1. Towards Service-based Business Process Modeling, Prototyping and Integration Ang Chen, Didier Buchs System Modeling and Verification Laboratory University of Geneva RISE 2005
    2. 2. Outline <ul><li>Business Process Management </li></ul><ul><li>COOPN Approach </li></ul><ul><li>Workflow Patterns </li></ul><ul><li>Prototyping & Integration </li></ul><ul><li>Conclusions & Future Work </li></ul>
    3. 3. Business Process Management
    4. 4. Business Process Management What is business process management? What is business process? What is the problem?
    5. 5. Example: RISE Workshop Activity, Case, Participant, Process, Resource, Data Call for papers Submission Review Selection Accepted? Accepted papers Rejected papers Registration Presentation yes no
    6. 6. Example: RISE Workshop cont. What to do if we want <ul><li>To add/remove an activity in the process? </li></ul><ul><li>To change the way of “review”? </li></ul><ul><li>The “selection” to be automatic? </li></ul>Is the process reusable? Entirely or partially? Is the process executable?
    7. 7. BPM <ul><li>Complexity comes from the change of requirements </li></ul><ul><li>Tends to process-aware or process-oriented systems (from data-oriented) </li></ul><ul><li>Make the distance between design and execution of process shorter </li></ul>
    8. 8. BPM: solutions <ul><li>Modeling Approaches </li></ul><ul><ul><li>UML activity diagram, Petri Nets, etc </li></ul></ul><ul><ul><li>Workflow patterns, perspectives </li></ul></ul><ul><li>Implementation (process enactment service) </li></ul><ul><ul><li>Centralized/Embedded workflow engine </li></ul></ul><ul><ul><li>Service Oriented </li></ul></ul><ul><ul><li>Standards: WfMC, BPEL, BPMI, OMG etc. </li></ul></ul>
    9. 9. BPM: Our solution Why do we propose to use a formal specification language? More precise semantic, no ambiguity Automatic verification and test generation Execution via prototype generation Enhanced reusability, modularity (Object-Orientation)
    10. 10. COOPN approach
    11. 11. COOPN <ul><li>Concurrent Object-Oriented algebraic Petri Nets </li></ul>Petri Nets Algebraic - all types are defined Object-Oriented - encapsulation Concurrent - synchronizations counter 0 x x+1 x==9? inc out counter 0 x x+1 x==9? inc out counter 0 x x+1 x==9? inc out // 0 0 0
    12. 12. COOPN cont. <ul><li>Three types of modules </li></ul><ul><ul><li>algebraic Abstract Data Type (ADT) </li></ul></ul><ul><ul><li>Class </li></ul></ul><ul><ul><li>Context </li></ul></ul><ul><li>Well-defined semantic with formal foundation, graphical representation </li></ul><ul><li>Axiomatic behavior description, declarative </li></ul><ul><ul><li>Event :: condition :: pre -> post Inc :: n<9 :: p (n) -> p (n+1) </li></ul></ul><ul><ul><li>When event Inc occurs, if ( n<9 ), take n from place p , and put n+1 into place p . </li></ul></ul>
    13. 13. Basic Workflow Constructs <ul><li>COOPN Workflow elements </li></ul><ul><li>ADT Case -> <ID, LocalState> </li></ul><ul><li>Class Activity; Objects -> Activity instances </li></ul><ul><li>Context Process </li></ul><ul><li>Methods Provided Services </li></ul><ul><li>Gates Required Services </li></ul><ul><li>Methods and Gates Input/Output Events </li></ul>Required service Output event Gate P A Provided service Input event Method B request response
    14. 14. Basic Workflow Constructs cont. AND-SPLIT MERGE + XOR SPLIT Minimum 2 reviews Submission Review Selection submission <,> <ID, submitted> Reviewer 1 <,> Reviewer 2 <,> Reviewer 3 <,> <ID, rank> selection <,> <,> <,> <ID, rejected> <ID, accepted> Send message to authors
    15. 15. Workflow Patterns
    16. 16. Workflow Patterns <ul><li>Initiator: Wil Van der Aalst, Eindhoven University of Technology, Netherlands </li></ul><ul><li>More than 20 patterns for control-flow </li></ul><ul><li>Flexible way to solve problems </li></ul><ul><li>Reusable </li></ul><ul><li>Perspectives: Control, Data, Resources etc. </li></ul>
    17. 17. Transactional Patterns <ul><li>Complement of common workflow patterns </li></ul><ul><li>States of process instance are transactional in the model </li></ul><ul><li>More interesting with resource perspective, e.g. dinning philosophers, resources allocation problem </li></ul>
    18. 18. Transactional Patterns cont. take free // // // // // // // // P2 eat P2 think P1 eat P1 think F1 * P2 * eat think P1 * eat think F2 * take free
    19. 19. Prototyping & Integration
    20. 20. Prototyping <ul><ul><li>Automatic Java code generation </li></ul></ul><ul><ul><ul><li>Embedded transition engine </li></ul></ul></ul><ul><ul><li>JavaBeans-liked prototype </li></ul></ul><ul><li>COOPNBuilder environment </li></ul><ul><li>Simulation before integration </li></ul>
    21. 21. Integration Service-Oriented Environment Enactment system DBMS ERP systems MIS systems Process controller Remote system Generated Pluggable process controller services services Process controller Process controller Process controller
    22. 22. Integration cont. <ul><li>Process enactment system should guarantee the execution of process </li></ul><ul><li>The responsibilities between the process controller and the enactment system should be clearly defined </li></ul><ul><li>Automatic integration is possible </li></ul>
    23. 23. Conclusions & Future Work
    24. 24. Conclusions <ul><li>Methodological approach </li></ul><ul><li>Technical design </li></ul><ul><li>Domain specific language, formal </li></ul><ul><li>Reusability: black-box, white-box, patterns </li></ul><ul><li>Rapid process prototyping and integration </li></ul>
    25. 25. Future works <ul><li>Develop transactional patterns </li></ul><ul><li>Add other perspectives (dimensions) to the model </li></ul><ul><ul><li>Data, Operational, Resources </li></ul></ul><ul><li>Verification </li></ul><ul><ul><li>Define high-level pertinent properties </li></ul></ul><ul><ul><li>Use model checking and theorem proving techniques </li></ul></ul><ul><li>Tools implementation </li></ul><ul><ul><li>Verification </li></ul></ul><ul><ul><li>Generalized workflow engine (enactment system) </li></ul></ul><ul><ul><li>Automatic integration of prototypes </li></ul></ul><ul><ul><li>Service-based interaction with external information systems </li></ul></ul>
    26. 26. Thanks for your attention <ul><li>Questions? </li></ul>