1. Dagstuhl 20071 How can we avoid ….. (closing panel EVENT Conference, 2012) “Currently, software designers have no guidelines on what should be implemented as event driven rules and what should not. The participants agreed that there is a need to provide tools for supporting event/rule features in the software development process…”

2. Dagstuhl 20072 Software Engineering Issues: old issues … (Dagstuhl workshop 1994) “In order to make this technology widely acceptable to users we require active DB design methodologies and tools. Unless we support the users early on we run the risk of causing disillusionment with this potentially powerful technology.” (closing panel RIDS’97) “methods and tools for designing active database systems”

3. Dagstuhl 20073 Software Engineering Issues Scenario Event driven application How? Active DBs.. other areas

4. Dagstuhl 20074 Implicit Focus: Example

5. Dagstuhl 20075 Explicit focus: Example

6. Dagstuhl 20076 Software Engineering Issues Implicit focus Derive events/rules from “traditional” modeling diagrams. How to derive? Explicit focus Graphical notation Process: Guidelines for modeling Extend existing (UML) diagrams and SE processes?

7. Dagstuhl 20077 Software Engineering Issues Events/rules => ruleMLs ruleMLs can be used by supporting tools for modeling, detecting design errors, … Heterogenity: Event: event language (ruleCore) Condition: condition language (Lisbon) Action: action language (Munich) http://rewerse.net/I5/

8. Dagstuhl 20078 Software Engineering Issues Guidelines: When to use events and rules? Use events/rules Do not use events/rules