D1 4 200710 Poznan+Paris Xpdl


Published on

Published in: Business
  • Be the first to comment

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

No notes for slide

D1 4 200710 Poznan+Paris Xpdl

  1. 1. WfMC Forum Poland 2007 Tutoriel WfMC France 2007 BPM in Practice: Understanding & Implementing BPM Justin Brunt WIMC Vice Chair. Sr. Product Manager TIBCO Ken Mei WVMC Eiderml Relations Committee Michael zur Muehlen Professor. Stevens Institute of Technology Nathaniel Palmer WfMC Executive Diraclor Keith Swenson, Tecmlcal Committee Chair. WIMC. VP R&D, Fujitsu Computer Systems
  2. 2. lI; :’i>oLI Section 2 XPDL The XML Process Definition Language The XML Process Definition Language
  3. 3. It’s All About Processes WfMC defines a process as: “The representation of a business process in a form that supports automated manipulation, ‘ such as modeling, or enactment by a workflow [or business] management system. The process definition consists of a network of activities and their relationships, criteria to indicate the start and termination of the process, and information about the individual activities, such as participants, associated IT applications and data, etc. ” -. n . ‘ C
  4. 4. The Process Definition Activity Network — Nodes & Transitions — Sequential, Parallel, Conditional, and Message paths I I I T K. ‘ iv I I7 It Activity Definitions Arbitrarily complex graphs Resource Requirement Sequential Activities Work Assignment Parallel Activities Applications and Services Loops / Cycles Dale Def'”"'°“5 Conditional Paths . .n nu‘- C
  5. 5. Putting XPDL into Context Formulated by WfMC — Members from organizations developing and using Workflow and BPM products Concepts embodied in Meta-model and Glossary — wvvw. wfmc. org/ standards/ docs/ TC- 101 1_term_glossa ry_v3. pdf Reference Model defines the interfaces — wvvw. wfmc. org/ standards/ docs/ tc003v1 1 . pdf C
  6. 6. XPDL GOAL - Process Definition Interchange Allow tools to exchange process models Format to exchange Process Definitions between ‘ — components in a Workflow/ BPM Product — different BPM/ Workflow Products — Process Modeling / Simulation tools and BPM/ Norkflow Products Implemented by commercial products Interoperability demonstrated by WfMC member organizations at public events C
  7. 7. XPDL Flexibility Requirement ° Large variety of tools — Many differing requirements on what must be stored — Not acceptable if XPDL could store only a subset — Must be able to store all the information - XPDL is extensible — Handle information used by a variety of different tools - Different dialects of XPDL — Use extended attributes to define vendor specific features ° Can transform from one dialect to another
  8. 8. Design Interchange vs. Executable Format / Ex ____, ,_- Design *"’x, ,DL Design Tool A . ._. /»~: ”‘” Tool B ‘ . / . BPEL, ,’ BPEL, XPDL, This path / XPDL, or some hot _. -’ or some engine X I engine specific / ’————~ generally specific format / supported format . / Execution Execution Engine A Engine B C
  9. 9. XPDL Capabilities - Design Interchange XPDL is a design interchange format that represents the graphical diagram — Includes metadata about executable aspects ~ Many Engines have proprietary formats — They have a design tool — Even BPEL engines have proprietary extensions It is generally not possible to design a process with a tool from one vendor and execute it in another vendor’s engine — But exchange between design tools is possible C
  10. 10. Process Design Ecosystem F-‘: ¥“[: I T Modeling 3:3? iir Tools 7 Optimization 1 ' Simulation A ‘ Tools ""~--. .., __ . . / ,/ Tools ’; _; Repository ‘ ‘ts Vendor C (XPDL) . / K as Design Design j Tool Tool *if. !?i spa. I I BPEL or some or some engine engine specific E specific formal format _L A Execution M Execution Engine -: . - Engine C
  11. 11. Process Design Ecosystem We foresee an ecosystem of process tools at the design level — Business oriented and developer oriented modelers — Simulation tools & optimization tools ‘ — Analysis tools — Professional business modeling tools — Conversions to/ from other formats like Visio XPDL can be a common standard interchange format between these tools Each tool extends XPDL for its use — Tools can understand a common subset of each other — All tools understand the basics; the graphical “diagram "r7i7’" ‘M C
  12. 12. History Behind XPDL XPDL is an implementation of Interface 1 — Interchange of process definitions between different tools and vendors viewed as essential WPDL (Workfiow Process Definition Language) ‘ — First implementation of Interface 1 Text based (predated XML) definition Published November 1998 XPDL 1.0 — Popularity of XML for defining document formats for the lntemet — Experience in using WPDL, Retained semantics of WPDL — New Syntax using XML Schema — Published October 2002 Neither WPDL nor XPDL propose graphical representation C
  13. 13. What does XPDL define? ° Process Definition — Activities ' Human Activities, Automated Activities, Subflow — Transitions ° Sequential, Branches — Participants — Resources — Applications ° EJB, POJO, XSLT, Script, Web Service, Bus. Rule, Form — Workflow Relevant Data — System and Environmental Data — Data Types and Expressions
  14. 14. XPDL Basic Structure lnfomiation shared across Process Level Information mumpic pr0c¢55¢5_ Process Variablesl Data Fields Swim Lanes] Participants Information for a single process. includes swim lanes. artifacts, ,Amivny data items. participants Activity _ _ “ . The "activity structure IS used to represent all the “nodes” of BPMN. including activities, gateways, and Transition events- Transition Pmcess level Informatlon The “transition" stnrcture is used to represent all the “connections” including sequence flow. message flow. and associations.
  15. 15. Package & Process - The package is the root node of XPDL file ° Package has one or more separate processes - A package can have multiple BPMN diagrams — Each diagram is denoted as a “page”
  16. 16. XPDL Extended Attributes & Elements ° XPDL schema is extensible - Extended Attributes - Any Elements ° Allows vendors to extend XPDL — Adds arbitrary XML in a well defined manner - Defines how to handle “unrecognized" elements ° Each tool can add tool specifics — Tool specific graphical information — Multiple representations of process parts ° This is a necessity for successful interchange
  17. 17. Invisible Process Semantics In/ Out formal parameter, standard data formats Parameter transformation to/ from sub-process Date / Time formats Simulation parameters — estimated activity duration — branch percentage estimates — cost and resource usage estimates Script expression syntax: JavaScript and other References to external processes Process lifecycle and version information Web Service and EJB component invocation Business Rule Invocation C
  18. 18. XPDL 2.0 - Convergence with BPMN ° Enhancements based on feedback on XPDL 1.0 ° Includes support for BPMN constructs ° Can store process definitions drawn in BPMN — BPMN does not provide this ° XPDL 2.0 is compatible with XPDL 1.0 ° Published October 2005 — Already a number of implementations available ° XPDL and BPMN address the same modeling space
  19. 19. New Elements in XPDL 2.0 from BPMN ° Pools and lanes — used to define participants and roles - Message flows — used for communication between processes ° Associations and Artifacts — used to document the process definitions ° Graphic information for each entity ° All the BPMN elements are in XPDL 2.0
  20. 20. Future XPDL — WfMC will continue to maintain XPDL — Will update based on ~ 3 BPMN evolution (1.1 available soon) ~ Implementers comments * XPDL 2.1 in progress - Have started a conformance community Samples made available for testing interoperability WfMC Website — http: //www. wfmc. org — http: //wvvw. vvfmc. org/ standards/ XPDL. htm C
  21. 21. Section 2 Summary Summary — XPDL is the most widely used format for exchange of process diagrams, adopted by ‘ more than 60 process tools. — XPDL 2.0 includes support for all aspects of a BPMN diagram, while remaining compatible with 1.0. — XPDL 2.0 is available today. C
  22. 22. Workflow Management Coalition Wfts‘ Proces s Thought Leaders hip