Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network


Rule driven workflow enactment

Uploaded on

Rule driven workflow enactment. Adriaan van Os, Tim Verwaart. ESUG 2005, Brussels

Rule driven workflow enactment. Adriaan van Os, Tim Verwaart. ESUG 2005, Brussels

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Rule driven workflow enactment Adriaan van Os www.soops.nl Tim Verwaart www.lei.wageningen-ur.nl Brussels, August 18th, 2005 13th European Smalltalk User Group Joint Event
  • 2. Subject • Last year we presented Artis: a system for model driven development and deployment • In Artis, workflow is driven by the information need • Data models and business rules can be used to specify the information need • In this presentation we explain how we realized workflow enactment by comparing database content with business rules
  • 3. Workflow enactment Rule violation entered into workload for responsible employee Enact procedure
  • 4. Information need What? When?
  • 5. In our case: farming
  • 6. Regional offices
  • 7. Information need drives workflow What? Workload When? Central Database
  • 8. Information need can be represented as a data structure model, for instance (attributes not shown): owns Holding has made Asset Payment payed for Demo: an artis data model (context)
  • 9. Data model is not sufficient to define the information need • We do not need to know all attribute values in all cases • We want the data to satisfy integrity constraints • We need the information in time
  • 10. Attach rules to each attribute Demo: RIA rule formulation and representation
  • 11. Act in case of rule violations
  • 12. Keeper determines workload Relevant? Complete and consistent? Current? Who is responsible? Data repository rules facts responsibility
  • 13. Keeper algorithm • for each entity in some designated population as a starting point: – for each attribute: • determine responsible employee and add rule violation to the workload: –if the attribute is relevant and the value is not current –or if the attribute is relevant and the value is current but does not satisfy the integrity constraint
  • 14. Two remarks 1. Attributes may be multi-valued (have a collection of entities as value). In that case, execute the keeper algorithm for all entities in the collection too. 2. Evaluation of actuality rules requires a temporal data representation. We represent the value of facts not as a simple value but as a pair of value and validity time. Demo: data representation (viewer)
  • 15. Who is responsible? • We record responsibility for entities in the repository as an entity-employee-association • No need to designate responsibility for each entity. The keeper traces back to the entity in the population it used as starting point. responsibility Entity Employee Collection
  • 16. What shoud she do? • The workflow is described in procedures • We record applicability of procedures as an association of procedure and rule applicability Procedure Rule • We use this knowledge to “enact” workflow: enter first task of procedure into responsible employees to-do list Demo: workload (Mole) and start
  • 17. Conclusion • Workflow can be enacted by comparing database content with business rules • This can only be generically achieved by applying a temporal data model • We need knowledge about: – responsibility (of persons) – applicability (of procedures)
  • 18. Questions? Data repository rules facts responsibility