What can BX make from Sense?Arend Rensink, University of TwenteBanff, December 2013

What can BX made from Sense? 2

Context: EU-project SENSATION

3 December 2013

SDF3(Synchronous

Data Flow)

UPPAAL(Timed

Automata)

sdf3 xml(w. xsd)

uppaal xml(w. xsd)

models

results

senseecore

uppaal

ecore

Not well-structured, too large

Lot of plain-text

elements

What can BX made from Sense? 3

Dataflow graphs

3 December 2013

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)

What can BX made from Sense? 4

Challenge

3 December 2013

Language differencesSDF3 SenseMany spurious elements Dedicated languageSource/target ports Source/target actorsReferences all by name References by identityProcessor type implicit Processor 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?

What can BX made from Sense? 5

SDF3

3 December 2013

What can BX made from Sense? 6

Sense metamodel

3 December 2013