Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ontologizing Business Processes

578 views

Published on

Talk at the Research Seminar on Process Modelling Patterns, ISTC, Rome
24th of February 2009

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

  • Be the first to like this

Ontologizing Business Processes

  1. 1. Ontologizing Business Processes talk at the Research Seminar of Process Modelling Patterns Institute for Cognitive Science and Technology, CNR, Rome, Italy 24th of February, 2009 Dr. Violeta Damjanovic Salzburg Research Forschungsgesellschaft m.b.H. Jakob Haringer Straße 5/3 | 5020 Salzburg, Austria T +43.662.2288-427 | F +43.662.2288-222 [email_address] www.salzburgresearch.at
  2. 2. Outline <ul><li>Introduction </li></ul><ul><ul><li>Problem </li></ul></ul><ul><ul><li>History </li></ul></ul><ul><ul><li>A Big Picture </li></ul></ul><ul><li>Hypothesis </li></ul><ul><ul><li>A Big Picture </li></ul></ul><ul><li>Strategy </li></ul><ul><ul><li>A Big Picture </li></ul></ul><ul><li>Results </li></ul><ul><ul><li>WSDL-DDPO </li></ul></ul><ul><ul><li>BPEL-DDPO </li></ul></ul><ul><li>Discussion </li></ul>
  3. 3. Introduction: Problem <ul><li>Business Process Management (BPM) </li></ul><ul><ul><li>Design and Modeling </li></ul></ul><ul><ul><li>Execution via workflow engine </li></ul></ul><ul><ul><li>Operation and Monitoring </li></ul></ul><ul><ul><li>Evaluation and Optimization </li></ul></ul><ul><li>Classification of BPM levels (Gadatsch, 2005) </li></ul><ul><ul><li>Strategic level </li></ul></ul><ul><ul><li>Functional level </li></ul></ul><ul><ul><li>Operational level </li></ul></ul><ul><li>Problem definition </li></ul><ul><ul><li>Ontology based workflow model </li></ul></ul>
  4. 4. Introduction: History <ul><li>Strategic level </li></ul><ul><ul><li>Using specific procedure in designing processes (e.g. V-model) </li></ul></ul><ul><li>Functional level </li></ul><ul><ul><li>Moving from a cognitive model to a computational model (e.g. business processes) </li></ul></ul><ul><ul><li>Involving foundational ontology (e.g. DOLCE, DDPO module) </li></ul></ul><ul><li>Operational level </li></ul><ul><ul><li>Business process execution (e.g. BPEL, WSDL) </li></ul></ul>
  5. 5. Introduction: A Big Picture A A2B B
  6. 6. Hypothesis <ul><li>MDA approach </li></ul><ul><ul><li>OMG MOF – defines the metadata architecture for MDA </li></ul></ul><ul><ul><li>OMG ODM – standard model for model driven ontology development </li></ul></ul><ul><li>Metamodels </li></ul><ul><ul><li>OWL </li></ul></ul><ul><ul><li>BPEL </li></ul></ul><ul><ul><li>WSDL </li></ul></ul><ul><li>Transformations </li></ul><ul><ul><li>Problem: lack of ontologically specified knowledge about business processes </li></ul></ul>
  7. 7. Hypothesis: A Big Picture
  8. 8. Strategy <ul><li>Ontology reengineering </li></ul><ul><ul><li>SE & KE </li></ul></ul><ul><ul><li>Design Patterns (SE) & Ontology Patterns (KE) </li></ul></ul><ul><ul><li>Classification of Ontology Patterns: </li></ul></ul><ul><ul><ul><li>Content pattern </li></ul></ul></ul><ul><ul><ul><li>Structural pattern (Architectural + Logical) </li></ul></ul></ul><ul><ul><ul><li>LexicoSyntactic pattern </li></ul></ul></ul><ul><ul><ul><li>Reasoning pattern </li></ul></ul></ul><ul><ul><ul><li>Presentation pattern (Naming + Annotation) </li></ul></ul></ul><ul><ul><ul><li>Correspondance pattern (Reengineering + Alignment) </li></ul></ul></ul><ul><li>Reenginering ODP </li></ul>
  9. 9. Strategy: A Big Picture
  10. 10. Results: WSDL-DDPO <ul><li>edns : description </li></ul><ul><ul><li>--- wsdlDefinition : wsdlTargetNamespace (>0) </li></ul></ul><ul><ul><li>--- wsdlMessage : wsdlName (=1) : dol:proper_part some wsdlPartOfMessage </li></ul></ul><ul><ul><li>--- wsdlPartOfMessage: wsdlName (=1) : wsdlType (=1) </li></ul></ul><ul><ul><li>´ : wsdlElement (optional) : dol:proper_part some wsdlPortType </li></ul></ul><ul><ul><li>--- wsdlPortType : wsdlName (=1) : dol:proper_part some wsdlOperation </li></ul></ul><ul><ul><li>--- wsdlOperation : wsdlName(=1) : wsdlInputMessage(=1) : wsdlOutputMessage(=1) : wsdlFaultName(optional) : wsdlFaultMessage(optional) : edns:d_uses some edns:task </li></ul></ul><ul><ul><li>--- wsdlBinding : wsdlName(=1) : wsdlType(=1) : wsdlSoapBinding(=1) : edns:d_uses some wsdlOperation </li></ul></ul><ul><ul><li>--- wsdlService : wsdlName(=1) : wsdlDocumentation (=1) : edns:d_uses some wsdlPort </li></ul></ul><ul><ul><li>--- wsdlPort : wsdlName(=1) : edns:d_uses some wsdlBinding : wsdlSoapLocation(=1) </li></ul></ul><ul><ul><li>--- plnkPartnerLinkType: wsdlName(=1) : dol:proper_part some plnkPartnerRole </li></ul></ul><ul><ul><li>--- plnkPartnerRole: wsdlName(=1) : edns:d_uses some wsdlPortType </li></ul></ul><ul><ul><li>--- wsdlSoapBinding: soapStyle(rpc I document) : edns:d_uses some soapTransport </li></ul></ul>
  11. 11. Results: BPEL-DDPO <ul><li>edns:description </li></ul><ul><ul><li>--- bpelProcess : bpelName(=1) : bpelTargetNamespace(>0) : bpelImportLocation(=1) : bpelImportNamespace(=1) : dol:proper_part some bpelPartnerLink : dol:proper_part some bpelVariable : dol:proper_part some bpelFlow </li></ul></ul><ul><ul><li>--- bpelPartnerLink : bpelName(=1) : bpelPartnerLinkType </li></ul></ul><ul><ul><li>--- bpelMyRoleLink : bpelMyRole </li></ul></ul><ul><ul><li>--- bpelPartnerRoleLink : bpelPartnerRole </li></ul></ul><ul><ul><li>--- bpelVariable : bpelName(=1) : bpelMessageType </li></ul></ul><ul><ul><li>--- bpelCatch : bpelFaultName(=1) </li></ul></ul><ul><ul><li>--- bpelFlow : bpelLink(>0) : dol:proper_part some bpelReceive : dol:proper_part some bpelSource : dol:proper_part some bpelReply : dol:proper_part some bpelInvoke </li></ul></ul><ul><ul><li>--- bpelReceive : bpelName(=1) : bpelOperation : bpelPartnerLinkReference : edns:d_uses some wsdlPortType : bpelVariableReference : dol:proper_part some bpelSource </li></ul></ul><ul><ul><li>--- bpelSource : bpelLinkName(=1) => bpelTransitionRule </li></ul></ul><ul><ul><li>--- bpelReply : bpelName(=1) : bpelOperation : bpelPartnerLinkReference : bpelVariableReference : edns:d_uses some wsdlPortType : bpelTarget(>0) </li></ul></ul><ul><ul><li>--- bpelInvoke : bpelName(=1) : bpelOperation : bpelPartnerLinkReference : edns:d_uses some wsdlPortType : bpelInputVariable(restrictedString) : bpelOutputVariable(restrictedString) : bpelTarget(>0) : edns:d_uses some bpelSource </li></ul></ul><ul><ul><li>… </li></ul></ul>
  12. 12. Discussion: Transition Rule
  13. 13. Discussion: Transition Rule <bpel:sources> <bpel:source linkName=&quot;target-to-request&quot;> <bpel:transitionCondition>$decision.tRequest ='yes' and $decision.changes ='no' </bpel:transitionCondition> </bpel:source> <bpel:source linkName=&quot;target-to-assign&quot;> <bpel:transitionCondition>$decision.tRequest ='no' and $decision.changes ='no' </bpel:transitionCondition> </bpel:source> </bpel:sources>
  14. 14. Discussion
  15. 15. Kontakt Violeta Damjanovic Salzburg Research Forschungsgesellschaft m.b.H. Jakob Haringer Straße 5/3 | 5020 Salzburg, Austria T +43.662.2288-427 | F +43.662.2288-222 [email_address] www.salzburgresearch.at

×