1 / 21

WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web

WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web. Stefano Butti , Marco Brambilla , Piero Fraternali Web Models Srl, Italy. Eclipse-IT, Bergamo, September 29 th, 2009. Agenda. Introduction Development Process WebML Workflow Primitives

elita
Download Presentation

WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web Stefano Butti, Marco Brambilla, PieroFraternali Web Models Srl, Italy Eclipse-IT, Bergamo, September 29th, 2009

  2. Agenda • Introduction • Development Process • WebML Workflow Primitives • Model Transformation • Conclusions

  3. Introduction • Web applications, Web services, and BPM are the de facto standard of modern enterprise integration • Web services enable system-to-system interaction; • Web applications allow distributed and ubiquitous user interaction • Business process specification languages ease the definition of the business constraints, by orchestrating service execution • We propose a model-driven approach for multiparty business processes, based on Web Service orchestration and Web user interface design. • BPMN • WebML

  4. Model-driven Development Process • Manual specification of (extended) BPMN process model • Automatic transformation of BPMN to WebML • Possible manual refinement of WebML models • Automatic running code generation on J2EE platform

  5. The contribution • an intuitive Rich Process Model to precisely specify the service choreography for a given application (including user interaction, if needed) • A set of extensions to BPMN • Model transformation and code generation techniques to implement and deploy the process

  6. Background • Business Process Design • representing processes (of heterogeneous nature) in terms of related, structured activities or tasks that produce a specific service or product • several proposals for visual modeling languages (e.g., UML, YAML, BPMN) • Model Driven Architectures • abstraction (separation of platform independent and platform dependent concerns) and models in Web application design and development • Web Engineering • use of models (and model transformations) as the key artifacts for application developments • several proposals (e.g., UML, Hera, OOHDM, UWE, W2000, WebML)

  7. Background: BPMN(Business Process Model Notation) • Description of business activities (technology- and platform- independent) • Activities • FlowsConstraints(OR-XOR-AND gateways) • Artifacts (Data Objects and data associations) • Events • Running example: • Banking • application • for processing • leasing requests • (cars or houses)

  8. Background: WebML (Web Modeling Language)www.webml.org • Web Modeling Language • Specification of interactive, integrated Web applications through orthogonal models. • Domain Models (ER or UML class diagrams for defining “the content”) • Navigation Models ( content publication and manipulation, page computation, hypertextual links, side effects) • Service definition and composition Models ( Web service invocation and publication, XML management)

  9. Extensions to BPMN • BPMN • does not provide support for: • Process data • Formalized data flows • does not convey information about the activity’s business logic • Formalized extensions to the BPMN language, introducing: • Activity typing (2) • Typed attributes and parameters • Typed and named data, consumed (3) and produced (4) • Links with guard conditions and mapped parameters (5)

  10. BPMN  WebML transformation (1) One control siteview per pool: Human interaction (3) One site view per lane: user navigation (4) One site view per lane: business logics of activities and gateways (4) One site view per lane: business logics of activities and gateways (5) Orchestration view: a controller component invokes the activities (2) One control serviceview per pool: WS Choreography • Transformation rules • finer-grained Application Model, needing few refinements by the designer • typed activities enables reusable application models • data dependencies are specified at a higher level • less errors in Application Model design • Faster development

  11. The NEXT unit • The Next unit encapsulates the process control logic • It exploits the information stored in the Process Metadata • It calculates the current process status and the enabled state transitions • It needs the following input parameters: • caseID(the currently executed process instance ID) • activityInstanceID(the current activity instance ID) • conditionParameters(the values to evaluate the conditions) NEXT

  12. The NEXT unit (cont.d) 4 execution modes: • Process start. Instantiates and starts a case for the given ProcessID. • Process end. Given the activityInstanceID of the last activity, sets the Case to “Ended”. • Calculate and execute. Given the actInstID of the last concluded activity, enables the execution of the subsequent activities. • Execute. Given an actInstID, sets its status to “Active” and launches its execution. NEXT

  13. A step-by-step example (1): Extended BPMN model • Enrichment of the BPMN example

  14. A step-by-step example (2): Content model • The metadata needed for tracking the process execution  enacting the web service orchestration + application- specific data

  15. A step-by-step example (3): Site- and Service- view • Views for starting the process / orchestration (manual and service-based)

  16. A step-by-step example (4): Orchestration siteview • Views for orchestrating the call to the modules (services, hypertext, or gateways)

  17. A step-by-step example (4): Business logics of activities • Business logics for the XOR gateway (Car vs. House) and the Credit Score remote activity (WS invocation)

  18. Implementation • Extensions to WebRatio, a commercial tool for the automatic generation of Web applications • Creation of a extended BPMN editor for the specification of the process models • Set of model to model and model to text transformations WebRatio BPMN Editor

  19. Additional investigations • Backward engineering (2): modularization of hypertext pieces and reuse as activity types through catalogues • Reverse Engineering (3): decomposition of the web application and extraction of the BP model

  20. Conclusions and future work • A modeling framework • a model-driven design process for service orchestrations • Helps the initial design of the process • Helps for its evolution when requirements change • the extensibility of the model, through the concept of activity types • the availability of well-established code generation technology • great improvement in productivity • Ongoing and future work • industrial implementation • reverse engineering of BP models

  21. Thank You! Questions? Contact: Stefano Butti Marco Brambilla Piero Fraternali Stefano.butti@webratio.com Marco.brambilla@webratio.com Piero.fraternali@webratio.com www.webratio.com

More Related