the behavioral coordination operator language · the behavioral coordination operator language...

$: The Behavioral Coordination Operator Language · The Behavioral Coordination Operator Language GL/\CE Day, May 10th, 2016 Julien Deantoni University of Nice, I3S CNRS, INRIA AOSTE$
The Behavioral Coordination Operator Language

GL/\CE Day, May 10th, 2016

Julien DeantoniUniversity of Nice, I3S CNRS, INRIA [email protected]

mailto:[email protected]

2

Conforms To

xDSML 1xDSML 1

Discrete Time Behavior

ADAPTIVE CRUISE

CONTROL SYSTEM

3

Conforms To

xDSML 1xDSML 1

Conforms To

xDSML 2xDSML 2

Conforms To

xDSML 3xDSML 3

Heterogeneous models and languages

Emerging System Behavior difficult to apprehend


BATTERYCONTROL

ADAPTIVE CRUISE

CONTROL SYSTEM

GPS TRACKING

4

Conforms To

xDSML 1xDSML 1

Heterogeneous models and languages

Emerging System Behavior difficult to apprehend


BATTERYCONTROL

ADAPTIVE CRUISE

CONTROL SYSTEM

GPS TRACKING

Coordinationof Behavioral

Models

Know-how

System Designer

Conforms To

xDSML 2xDSML 2

Conforms To

xDSML 3xDSML 3

5

Outline

● State of the Art:– Coordination Languages and ADLs– Coordination Frameworks

● Our proposal: – The Behavioral Coordination Operator Language

● Conclusion

6

Running Example: the Coffee MachineTimed Finite State Machine (TFSM)

Conforms To

when coin / !selectCoffee;

when releaseCoffee / doLock

Conforms To

Activity

State-based language

Action-based language

7


Conforms To



Conforms To

Activity

?



8


Conforms To



Conforms To

Activity

?



e.g.,When the event selectCoffee occurs, the Action selectCoffee is started

9

Coordination Languages & ADLs

defines

Know-how

System Designer

Model ofCoordination

TFSM



Conforms ToConforms To

Activity

Coordination Languages proposed to model the coordination by using a dedicated Language, e.g., Linda or Esper.

ADLs proposed component based languages to coordinate, possibly heterogeneous behaviors, e.g., Wright, Rapide or MetaH.

10


defines

Know-how

System Designer


TFSM



ModelBehavioralInterface




Conforms To Conforms To

Activity



11


Know-how

System Designer


TFSM







Glue


Activity



SelectCoffee: Event

Rapide:CoffeeCoin.selectCoffee => CoffeeAlgorithm.selectCoffee

SelectCoffee: Action

defines

12


Know-how

System Designer


TFSM







Glue


Activity


ADLs proposed component based languages to coordinate, possibly heterogeneous behaviors, e.g., Wright or MetaH.

SelectCoffee: Event

Rapide:CoffeeCoin.selectCoffee => CoffeeAlgorithm.selectCoffee

SelectCoffee: Action

defines

The coordination is modeled explicitly

The coordination is defined rule by rule

13

Coordination Patterns

defines

Know-how

System Designer


TFSM







What?, When?,How?


Activity

14

Coordination Frameworks

Know-how

System Designer


Coordination frameworks identified a systematic way to coordinate models, i.e., a coordination pattern.

CoordinationFrameworks

e.g. Ptolemy

enco

des

TFSM




Activity





15


Know-how

System Designer




e.g. Ptolemy

encodes

TFSM




Activity

16


Know-how

System Designer




e.g. Ptolemy

encodes

TFSM




Activity

17


Know-how

System Designer




e.g. Ptolemy

encodes

TFSM




Activity

18


Know-how

System Designer




e.g. Ptolemy

encodes

TFSM




Activity

19


e

ncodes


Know-how

System Designer


e.g. Ptolemy

TFSM



Syntax BehavioralSemantics

Director: TFSM

SyntaxBehavioralSemantics

Director: Activity

LanguageBehavioralInterface




Activity






generates

20


e

ncodes


Know-how

System Designer


e.g. Ptolemy

TFSM




Director: TFSM


Director: Activity





Activity






generates


What?, When? and How? the methods from the semantics

Interfaces are invoked (Java)

21


e

ncodes


Know-how

System Designer


e.g. Ptolemy

TFSM




Director: TFSM


Director: Activity





Activity






generates


The coordination is generated automatically

The coordination pattern is hidden/encoded in the tool in a GPL

22

Take-Away Lessons

● Coordination Languages & ADLs:

● Coordination Frameworks:

The coordination is modeled explicitly

The coordination is defined rule by rule

The coordination is generated automatically based on a coordination pattern

The coordination pattern is hidden/encoded in the tool in a GPL

23

Outline

● State of the Art– Coordination Languages

– Coordination Frameworks

● Our proposal: – The Behavioral Coordination Operator Language

● Conclusion

24






Know-how

System Designer

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>TFSM







Activity

defin

es

System Designer



generates

25




Know-how

System Designer

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

defin

es

System Designer



generates



26




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates





27




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates





State::entering

State::leaving

FSMEvent::occurs

28




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates





State::entering

State::leaving

FSMEvent::occurs

Alternates

29




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates





State::entering

State::leaving

FSMEvent::occurs

Alternates

releaseCoffee:occurs

Locked:entering

Locked:leaving

selectCoffee:occurs

Locked:entering

Locked:leaving

30




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates





State::entering

State::leaving

FSMEvent::occurs

Alternates

a1:Alternates

a2:Alternates


Locked:entering

Locked:leaving

selectCoffee:occurs

Locked:entering

Locked:leaving

31




BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

generates



Action::startAction

Action::finishAction



State::entering

State::leaving

FSMEvent::occurs

Alternates

a1:Alternates

a2:Alternates


Locked:entering

Locked:leaving

selectCoffee:occurs

Locked:entering

Locked:leaving

32


Know-how

System Designer

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

defin

es

System Designer



generates

33


Know-how

System Designer

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

<<Conforms To>>

defin

es

System Designer



generates

34

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM


Action::startActionFSMEvent::occurs

BCOoL Metamodel SyncFSMEventsAndActions.bcool

<<Conforms To>>

35

BCOoL Metamodel SyncFSMEventsAndActions.bcoolImportInterface tfsm;ImportInterface Activity;

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM



<<Conforms To>>

36


Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction)

End Operator;

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM



<<Conforms To>>

37


Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction) When(occurs.name = startAction.name);

End Operator;

OCL Boolean Expression between model elements

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM



<<Conforms To>>

38



CoordinationRule: RendezVous (occurs, startAction)

End Operator;

Causal and Temporal relations between Events

e.g., Rendezvous, Precedes, etc.

EventType

EventTypes

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM



<<Conforms To>>

39

BCOoL Metamodel SyncFSMEventsAndActions.bcool

EventType

EventTypes

ImportInterface tfsm;ImportInterface Activity;


CoordinationRule: RendezVous (occurs, startAction)

End Operator;

Defined in MoCCML(Model of Concurrency and

Communication Modeling Language)

BCOoLBCOoL

BCOoLSpecification

BCOoLSpecification

TFSM



<<Conforms To>>

40

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecificationImportInterface tfsm;

ImportInterface Activity;

Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startAction.name);CoordinationRule:

Rendezvous (occurs, startAction)End Operator;

SyncFSMEventsAndActions.bcool



selectCoffee:startAction

makeCoffee:startAction

releaseCoffee:startAction

releaseCoffee:finishAction

makeCoffee:finishAction



Locked:entering

Locked:leaving

selectCoffee:occurs

Locked:entering

Locked:leaving

BCOoLBCOoL

TFSM



<<Conforms To>>

41



selectCoffee:occurs






BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification


BCOoLBCOoL

TFSM



<<Conforms To>>




42



selectCoffee:occurs





Conforms ToConforms ToConforms To

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification


BCOoLBCOoL

TFSM



<<Conforms To>>




43



selectCoffee:occurs





BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification


BCOoLBCOoL

TFSM



<<Conforms To>>




44



selectCoffee:occurs




Conforms To

Rendezvous

Rendezvous

Conforms To

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification


BCOoLBCOoL

TFSM



<<Conforms To>>




45



selectCoffee:occurs




Conforms To

Rendezvous

Rendezvous

Conforms To

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification

BCOoLSpecification


BCOoLBCOoL

TFSM



<<Conforms To>>




Heterogeneous Execution

In the GEMOC Studio

Implemented into the GEMOC studio

Editing facilitiesby using XtextEditing facilitiesby using Xtext

Implemented into the GEMOC studio

Coordinated HeterogeneousExecutionCoordinated HeterogeneousExecution

Schedule space explorationSchedule space exploration

Conclusion

● BCOoL is a dedicated metalanguage to capture coordination patterns.

● It automates the coordination of models by relying on a formal language.

● It is associated to the GEMOC language/modeling workbench to execute and analyze the coordinated system.

➔ Future work:– Using the explicit coordination to generate master on co-simulation bus

– Understanding the interconnection with physical model (continuous time)

1http://timesquare.inria.fr/BCOoL

Thanks

http://timesquare.inria.fr/BCOoL

http://gemoc.org/ins

the behavioral coordination operator language · the behavioral coordination operator language...

Documents