1. What can BX make from Sense? Arend Rensink, University of Twente Banff, December 2013

2. Context: EU-project SENSATION 3 December 2013What can BX made from Sense? 2 SDF3 (Synchronous Data Flow) UPPAAL (Timed Automata) sdf3 xml (w. xsd) uppaal xml (w. xsd) models results sense ecore uppaal ecore Not well- structured, too large Lot of plain- text elements

3. Dataflow graphs 3 December 2013What can BX made from Sense? 3  Elements  Actors (nodes): name  Ports: name, direction (in, out), rates  Channels (edges): name, initial tokens, source/target port  Processors with execution time for subset of actors  Petri Net-like semantics  Actors = transitions, channels = places, rates = weights  Non-atomic transition firing (actors take time)

4. Challenge 3 December 2013What can BX made from Sense? 4  Language differences SDF3Sense Many spurious elementsDedicated language Source/target portsSource/target actors References all by nameReferences by identity Processor type implicitProcessor type explicit  Bidirectionality  Sense-to-SDF3 should be (provably) left inverse to SDF3-to-Sense  Executability  Transformation definition must be executable  Underlying technology  XSD-backed XML versus Ecore  Simplified option: Ecore-euivalent on SDF3 side Is there a solution that allows a proof of bidirectionality, and is directly executable on concrete models?

5. SDF3 3 December 2013What can BX made from Sense? 5

6. Sense metamodel 3 December 2013What can BX made from Sense? 6