The Behavioral Coordination Operator Language

Transcription

1 The Operator Language GL/\CE Day, May 10th, 2016 Julien Deantoni University of Nice, I3S CNRS, INRIA AOSTE

2 Discrete Time Behavior xdsml 1 ADAPTIVE CRUISE CONTROL SYSTEM 2

3 3 Discrete Time Behavior xdsml 2 xdsml 1 ADAPTIVE CRUISE CONTROL SYSTEM xdsml 3 BATTERY CONTROL GPS TRACKING Heterogeneous models and languages Emerging System Behavior difficult to apprehend

4 4 Discrete Time Behavior xdsml 2 xdsml 1 xdsml 3 ADAPTIVE CRUISE CONTROL SYSTEM GPS TRACKING BATTERY CONTROL Know-how of s System Designer Heterogeneous models and languages Emerging System Behavior difficult to apprehend

5 5 Outline State of the Art: Languages and ADLs Frameworks Our proposal: The Operator Language Conclusion

6 Running Example: the Coffee Machine 6 Activity Timed Finite State Machine () State-based language Action-based language

7 Running Example: the Coffee Machine 7 Activity Timed Finite State Machine () State-based language Action-based language?

8 8 Running Example: the Coffee Machine Activity Timed Finite State Machine () State-based language Action-based language e.g.,when the event selectcoffee occurs, the Action selectcoffee is started?

9 Languages & ADLs 9 Activity 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. Know-how System Designer def ine s of

10 Languages & ADLs 10 Activity 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. Know-how System Designer def ine s of

11 Languages & ADLs 11 Activity 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. Know-how System Designer def ine s of SelectCoffee: Event SelectCoffee: Action Glue Rapide:CoffeeCoin.selectCoffee => CoffeeAlgorithm.selectCoffee

12 Languages & ADLs 12 Activity 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 or MetaH. The coordination is modeled explicitly Know-how The coordination is defined rule by rule System Designer def ine s of SelectCoffee: Event SelectCoffee: Action Glue Rapide:CoffeeCoin.selectCoffee => CoffeeAlgorithm.selectCoffee

13 Patterns 13 Activity What?, When?,How? Know-how System Designer def ine s of

14 Frameworks 14 Activity Frameworks e.g. Ptolemy s de o c en Know-how frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. System Designer of

15 Frameworks 15 Activity Frameworks s ode c n e Know-how e.g. Ptolemy frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. System Designer of

16 Frameworks 16 Activity Frameworks s ode c n e Know-how e.g. Ptolemy frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. System Designer of

17 Frameworks 17 Activity Frameworks s ode c n e Know-how e.g. Ptolemy frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. System Designer of

18 Frameworks 18 Activity Frameworks s ode c n e Know-how e.g. Ptolemy frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. System Designer of

19 Frameworks 19 Activity Syntax Semantics Frameworks Language Language e.g. Ptolemy Language Language Syntax Semantics Director: Activity Director: s de o c en generates Know-how System Designer of

20 Frameworks 20 Activity Syntax Semantics Frameworks Language Language e.g. Ptolemy s de o c en What?, When? and How? the methods from the semantics s are invoked (Java) frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. generates Know-how Syntax Semantics Director: Activity Director: Language Language System Designer of

21 Frameworks 21 Activity Syntax Semantics Frameworks Language Language e.g. Ptolemy Language Language Syntax Semantics Director: Activity Director: s de o c en frameworks identified a systematic way to coordinate models, i.e., a coordination pattern. generates Know-how The coordination is generated automatically The coordination pattern is hidden/encoded in the tool in a GPL System Designer of

22 22 Take-Away Lessons Languages & ADLs: The coordination is modeled explicitly The coordination is defined rule by rule Frameworks: The coordination is generated automatically based on a coordination pattern The coordination pattern is hidden/encoded in the tool in a GPL

23 23 Outline State of the Art Languages Frameworks Our proposal: The Operator Language Conclusion

24 24 Syntax Semantics <<>> Language Language Activity Language Language Syntax Semantics es if n de Know-how generates System Designer of

25 25 <<>> es if n de Know-how generates System Designer of

26 26 <<>> generates of

27 27 <<>> State::entering State::leaving generates FSMEvent::occurs of

28 28 <<>> State::entering Alternates State::leaving generates FSMEvent::occurs of

29 29 <<>> State::entering Alternates State::leaving generates FSMEvent::occurs Locked:entering Locked:leaving Locked:entering Locked:leaving selectcoffee:occurs releasecoffee:occurs of

30 30 <<>> State::entering Alternates State::leaving generates FSMEvent::occurs Locked:entering a1:alternates Locked:leaving Locked:entering Locked:leaving selectcoffee:occurs releasecoffee:occurs a2:alternates of

31 31 <<>> Action::startAction Action::finishAction State::entering Alternates State::leaving generates FSMEvent::occurs Locked:entering a1:alternates Locked:leaving Locked:entering Locked:leaving selectcoffee:occurs releasecoffee:occurs a2:alternates of

32 32 <<>> Know-how generates System Designer es if n de of

33 33 <<>> Know-how generates System Designer es if n de of

34 34 FSMEvent::occurs Syntax Action::startAction <<>> Semantics Metamodel SyncFSMEventsAndActions.bcool

35 35 FSMEvent::occurs Syntax Action::startAction <<>> Semantics Metamodel SyncFSMEventsAndActions.bcool Import tfsm; Import Activity;

36 36 FSMEvent::occurs Syntax Action::startAction <<>> Semantics Metamodel SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction) End Operator;

37 37 FSMEvent::occurs Syntax Action::startAction <<>> Semantics Metamodel SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction) When(occurs.name = startaction.name); End Operator; OCL Boolean Expression between model elements

38 38 FSMEvent::occurs Syntax Action::startAction <<>> Semantics Metamodel SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; EventTypes EventType Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction) When(occurs.name = startaction.name); Rule: RendezVous (occurs, startaction) End Operator; Causal and Temporal relations between Events e.g., Rendezvous, Precedes, etc.

39 39 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Metamodel Import tfsm; Import Activity; Operator RendezVousWhenSameName (FSMEvent::occurs,Action::startAction) EventTypes EventType When(occurs.name = startaction.name); Rule: RendezVous (occurs, startaction) End Operator; Defined in MoCCML ( of Concurrency and Communication ing Language)

40 40 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; Locked:entering selectcoffee:startaction Locked:leaving makecoffee:startaction Locked:entering makecoffee:finishaction Locked:leaving selectcoffee:occurs releasecoffee:occurs releasecoffee:startaction releasecoffee:finishaction

41 41 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; selectcoffee:startaction makecoffee:startaction releasecoffee:startaction selectcoffee:occurs releasecoffee:occurs

42 42 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; selectcoffee:startaction makecoffee:startaction releasecoffee:startaction selectcoffee:occurs releasecoffee:occurs

43 43 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; selectcoffee:startaction releasecoffee:startaction selectcoffee:occurs releasecoffee:occurs

44 44 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; selectcoffee:startaction Rendezvous releasecoffee:startaction selectcoffee:occurs Rendezvous releasecoffee:occurs

45 45 FSMEvent::occurs Syntax Action::startAction <<>> Semantics SyncFSMEventsAndActions.bcool Import tfsm; Import Activity; Operator FSMEventsandActions (FSMEvent::occurs, Action::startAction) When(occurs.name = startaction.name); Rule: Rendezvous (occurs, startaction) End Operator; selectcoffee:startaction Heterogeneous Execution In the GEMOC Studio Rendezvous releasecoffee:startaction selectcoffee:occurs Rendezvous releasecoffee:occurs

46 Implemented into the GEMOC studio Editing facilities facilities Editing by using using Xtext Xtext by

47 Implemented into the GEMOC studio Schedule space space exploration exploration Schedule Coordinated Heterogeneous Heterogeneous Coordinated Execution Execution

48 Conclusion 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) 1

49 Thanks