Involving Business Users in Formal Modelling (EKAW 2010)


Published on

These are the slides presented by Ronald Heller and Jeroen van Grondelle at the 17th EKAW conference, october 2010 in Lisbon, Portugal.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Involving Business Users in Formal Modelling (EKAW 2010)

  1. 1. Involving Business Users in FormalModellingusingNaturalLanguagePatternSentences<br />Jeroen van Grondelle, Ronald Heller, Emiel van Haandel, Tim Verburg<br />Be Informed<br />EKAW 2010, Lisboa, Portugal<br />
  2. 2.
  3. 3.
  4. 4.
  5. 5. Business User Friendly Representation<br />
  6. 6. Business User Friendly Representation<br />
  7. 7. Business User Friendly Representation<br />
  8. 8. Business User Friendly Representation<br />
  9. 9. Business User Friendly Representation<br />
  10. 10. Our Typical Domain Expert<br />Domain Experts, close to the business of our Clients<br />Highly Educated<br />Very Experienced<br />Respected in their Fields<br />But<br />No training in Formal Representation<br />Averse to “Technology”<br />
  11. 11. Business User Tasks in Modeling<br />HolyGrail: Editing<br />“Single step policyimplementation: Business changesitsownsystems”<br />But even more important<br />Reviewing<br />Dissemination/Communication<br />Explainingindividual cases<br />Feedback<br />
  12. 12. Primary proces<br />!<br />!<br />!<br />Policy proces<br />Review & validation<br />
  13. 13. Be Informed model<br />?<br />
  14. 14. Early attempts to incorporate language<br />Language-like triples<br />Adding language to relation<br />Concatenation of Multiple Triples<br />One of our typical users:<br />“I don’t think that sentence is correct…”<br />Editing by parsing triples out of these sentences<br />Typical reaction:<br />“I keep getting it wrong…”<br />HTML EXPORT<br />
  15. 15. Early attempts to incorporate language<br />Domain Specific Languages<br />Many are very syntax oriented<br />Typical Reaction: <br /> “That’s programming!”<br />
  16. 16. Early lessons learned<br />Free typing is not a great editing metaphor<br />Is it freedom if there is more wrong than right?<br />Limiting users in the number of ways things can be expressed is a good thing<br />Consistency and quality<br />No need to make choices at every sentence<br />Guidelines are needed to avoid ambiguity<br />For instance from SBVR/Rulespeak<br />
  17. 17. IntroducingPatternSentences<br />Sentence Parts mapping to triple types in formal graph<br />Static Text<br />Introduction of concepts (Objects)<br />References to concepts (Subjects)<br />Editing operations based on pattern sentences<br />Choosing sentence parts<br />Name an introduced concept<br />Choose an existing concept to refer to<br />
  18. 18. WhyPatternSentences<br />Bridge the gap between formal and natural approach<br />The underlying model is the formal graph<br />The sentences are hand made for comprehensibility<br />Based on best practices in the BR community like RuleSpeak<br />Based on NLG<br />No parsing: on editing, widgets are NLG-ed in<br />Provides freedom in choosing pattern sentences<br />Ability to embed “explanation” inside the pattern <br />Example: next slide<br />
  19. 19. Example<br />A customerappliesfor the Triple Play by ordering all of the products Digital TV, Fast ADSL and BasicTelehony<br />
  20. 20. Additional Advantages<br />Pattern sentences on top of formal graph have other advantages<br />Multiple visualisations<br />Visual, tabular, textual<br />Multiple languages<br />Translated Patterns<br />Multiple target groups<br />Ie. Grammars for different Expert levels<br />
  21. 21. Demo: Textual Policy<br /> In telecommunications, triple play service is a marketing term for the provisioning of two bandwidth-intensive services, high-speed Internet access and television, and a less bandwidth-demanding (but more latency-sensitive) service, telephone, over a single broadband connection. Triple play focuses on a combined business model rather than solving technical issues or a common standard.<br />
  22. 22. Demo: The knowledge model<br />
  23. 23. Demo: The model driven service<br />
  24. 24. Demo: Reviewing based on Natural Language<br />4 februari 2008<br />24<br />
  25. 25. Demo: Business users write rules<br />
  26. 26. Demo: GrammarConfiguration<br />
  27. 27. RemainingChallenges<br />How to prevent large numbers of patterns<br />Language variations: <br />Inflectional morphology: Plurals,..<br />Other natural languages<br />Mathematical Expressions<br />Named things vs anonymous things<br />Extending/relating CNL’s like we extend/relate meta models<br />
  28. 28. Questions and Discussion<br />Do you have questions, ideas for improvement?<br />Want to see more?<br />Meet us this week<br />Short Talk on Acquiring and Modelling Legal Knowledge using Patterns<br />Today at 16:30<br />Poster Session<br />Tutorial 2 on Knowledge Infrastructures<br />Friday at 9:00<br />Contact us <br />{j.vangrondelle, r.heller}<br />