WebRatio BPM: a Tool <br />for Design and Deployment <br />of Business Processes on the Web<br />Stefano Butti, Marco Bram...
Agenda<br />Introduction<br />Development Process<br />WebML Workflow Primitives<br />Model Transformation<br />Conclusion...
Introduction<br />Web applications, Web services, and BPM are the de facto standard of modern enterprise integration<br />...
Model-driven Development Process<br />Manual specification of BPMN process model <br />Automatic transformation of BPMN to...
The contribution<br />Adoption of Process Model to precisely specify the workflow for a given application <br />including ...
Background<br />Business Process Design<br />representing processes (of heterogeneous nature) in terms of related, structu...
Background: BPMN(Business Process Model Notation)<br />7<br />Description of business activities (technology- and platform...
FlowsConstraints(OR-XOR-AND gateways)
 Artifacts (Data Objects and data associations)
 Events</li></ul>Running example:<br />Banking <br />application<br />for processing<br />leasing requests <br />(cars or ...
Background: WebML (Web Modeling Language)www.webml.org<br />8<br />Web Modeling Language<br />Specification of interactive...
 Navigation Models ( content publication and manipulation, page computation, hypertextual links, side effects)
 Service definition and composition Models ( Web service invocation and publication, XML management)</li></li></ul><li>9<b...
BPMN WebMLtransformation<br />Transformation rules<br />finer-grained Application Model, needing few refinements by the d...
The NEXT unit<br />The Next unit encapsulates the process control logic<br />It exploits the information stored in the Pro...
A step-by-step example (1): Extended BPMN model<br />the complete BPMN example <br />12<br />
A step-by-step example (2): Content model<br /><ul><li>The metadata needed for tracking the process execution  enacting t...
A step-by-step example (3): Site- and Service- view<br />14<br />Views for starting the process / orchestration 				(manua...
A step-by-step example (4): Orchestration siteview<br />15<br />Views for orchestrating the call to the modules (services,...
16<br />A step-by-step example (4): Business logics of activities<br />Business logics for the XOR gateway (Car vs. House)...
Upcoming SlideShare
Loading in...5
×

WebRatio BPM: a Tool for Designing and Deploying Business Processes on the Web

2,596

Published on

See also:
http://www.webratio.com
http://dbgroup.como.polimi.it/brambilla/webratio-bpm
http://www.youtube.com/watch?v=jRS1LTazxFk (demo video)

We present WebRatio BPM, an Eclipse-based tool that supports the design and deployment of business processes as Web applications. The tool applies Model Driven Engineering techniques to complex, multi-actor business processes, mixing tasks executed by humans and by machines, and produces a Web application running prototype that implements the speci ed process. Business processes are described through the standard BPMN notation, extended with information on task assignment, escalation policies, activity semantics, and typed dataflows, to enable a two-step generative approach: first the Process Model is automatically transformed into a Web Application Model in the WebML notation, which seamlessly expresses both human- and machine-executable tasks; secondly, the Application Model is fed to an automatic transformation capable of producing the running code. The tool provides various features that increase the productivity and the quality of the resulting application: one-click generation of a running protoype of the process from the BPMN model; fine-grained refinement of the resulting application; support of continuous evolution of the application design after requirements changes (both at business process and at application levels).

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,596
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
102
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

WebRatio BPM: a Tool for Designing and Deploying Business Processes on the Web

  1. 1. WebRatio BPM: a Tool <br />for Design and Deployment <br />of Business Processes on the Web<br />Stefano Butti, Marco Brambilla, PieroFraternali<br />Web Models Srl, Italy<br />ICWE 2010, July 7th 2010, Vienna<br />
  2. 2. Agenda<br />Introduction<br />Development Process<br />WebML Workflow Primitives<br />Model Transformation<br />Conclusions<br />
  3. 3. Introduction<br />Web applications, Web services, and BPM are the de facto standard of modern enterprise integration<br />Web services enable system-to-system interaction;<br />Web applications allow distributed and ubiquitous user interaction<br />Business process specification languages ease the definition of the business constraints, by orchestrating service execution<br />We propose a model-driven approach for multiparty business processes, based on Web Service orchestration and Web user interface design. <br />BPMN<br />WebML<br />3<br />
  4. 4. Model-driven Development Process<br />Manual specification of BPMN process model <br />Automatic transformation of BPMN to WebML<br />Possible manual refinement of WebML models<br />Automatic running code generation on J2EE platform<br />Virtuous development cycle<br />4<br />
  5. 5. The contribution<br />Adoption of Process Model to precisely specify the workflow for a given application <br />including user interaction and service orchestration<br />Model transformation and code generation techniques to implement and deploy the process<br />5<br />
  6. 6. Background<br />Business Process Design<br />representing processes (of heterogeneous nature) in terms of related, structured activities or tasks that produce a specific service or product<br />several proposals for visual modeling languages (e.g., UML, YAML, BPMN) <br />Model Driven Architectures <br />abstraction (separation of platform independent and platform dependent concerns) and models in Web application design and development<br />Web Engineering<br />use of models (and model transformations) as the key artifacts for application developments<br />several proposals (e.g., UML, Hera, OOHDM, UWE, W2000, WebML)<br />6<br />
  7. 7. Background: BPMN(Business Process Model Notation)<br />7<br />Description of business activities (technology- and platform- independent)<br /><ul><li> Activities
  8. 8. FlowsConstraints(OR-XOR-AND gateways)
  9. 9. Artifacts (Data Objects and data associations)
  10. 10. Events</li></ul>Running example:<br />Banking <br />application<br />for processing<br />leasing requests <br />(cars or houses)<br />
  11. 11. Background: WebML (Web Modeling Language)www.webml.org<br />8<br />Web Modeling Language<br />Specification of interactive, integrated Web applications through orthogonal models.<br /><ul><li> Domain Models (ER or UML class diagrams for defining “the content”)
  12. 12. Navigation Models ( content publication and manipulation, page computation, hypertextual links, side effects)
  13. 13. Service definition and composition Models ( Web service invocation and publication, XML management)</li></li></ul><li>9<br />Background: BPMN<br />BPMN<br /> does not provide support for:<br />Process data<br />Formalized data flows<br />does not convey information about the activity’s business logic<br />BPMN language, with 2.0 crucial features:<br />Activity typing (2)<br />Typed attributes and parameters<br />Typed and named data, consumed (3) and produced (4)<br />Links with guard conditions and mapped parameters (5)<br />
  14. 14. BPMN WebMLtransformation<br />Transformation rules<br />finer-grained Application Model, needing few refinements by the designer<br />typed activities enables reusable application models<br />data dependencies are specified at a higher level<br />less errors in Application Model design<br />Faster development<br />10<br />(1) One control siteview per pool: Human interaction<br />(2) One control serviceview per pool: WS Choreography<br />(3) One site view per lane: user navigation<br />(4) One site view per lane: business logics of activities and gateways<br />(4) One site view per lane: business logics of activities and gateways<br />(5) Orchestration view: a controller component invokes the activities<br />
  15. 15. The NEXT unit<br />The Next unit encapsulates the process control logic<br />It exploits the information stored in the Process Metadata <br />It calculates the current process status and the enabled state transitions <br />It needs the following input parameters: <br />caseID(the currently executed process instance ID)<br />activityInstanceID(the current activity instance ID)<br />conditionParameters(the values to evaluate the conditions)<br />11<br />NEXT<br />
  16. 16. A step-by-step example (1): Extended BPMN model<br />the complete BPMN example <br />12<br />
  17. 17. A step-by-step example (2): Content model<br /><ul><li>The metadata needed for tracking the process execution  enacting the web service orchestration</li></ul>+ application-<br /> specific data<br />13<br />
  18. 18. A step-by-step example (3): Site- and Service- view<br />14<br />Views for starting the process / orchestration (manual and service-based)<br />
  19. 19. A step-by-step example (4): Orchestration siteview<br />15<br />Views for orchestrating the call to the modules (services, hypertext, or gateways)<br />
  20. 20. 16<br />A step-by-step example (4): Business logics of activities<br />Business logics for the XOR gateway (Car vs. House) and the Credit Score remote activity (WS invocation)<br />
  21. 21. Implementation<br />Extensions to WebRatio, a commercial tool for the automatic generation of Web applications<br />Creation of a extended BPMN editor for the specification of the process models<br />Set of model to model and model to text transformations<br />17<br />WebRatio BPMN Editor<br />
  22. 22. Additional investigations <br /><ul><li>Backward engineering (2): modularization of hypertext pieces and reuse as activity types through catalogues
  23. 23. Reverse Engineering (3): decomposition of the web application and extraction of the BP model</li></ul>18<br />
  24. 24. Conclusions and future work<br />19<br />A modeling framework<br /><ul><li> a model-driven design process for service orchestrations
  25. 25. Helps the initial design of the process
  26. 26. Helps for its evolution when requirements change
  27. 27. the extensibility of the model, through the concept of activity types
  28. 28. the availability of well-established code generation technology
  29. 29. great improvement in productivity </li></ul>Ongoing and future work<br /><ul><li> industrial implementation
  30. 30. reverse engineering of BP models</li></li></ul><li>20<br />Thank You! Questions?<br />Come and see us at the booth!<br />(And video on youtube)<br />Contact:<br />Stefano Butti<br />Marco Brambilla<br />Piero Fraternali<br />Stefano.butti@webratio.com<br />Marco.brambilla@webratio.com<br />Piero.fraternali@webratio.com<br />www.webratio.com<br />

×