Semantics for Model Debugging Simon Van Mierlo Yentl Van Tendeloo - - PowerPoint PPT Presentation

semantics for model debugging
SMART_READER_LITE
LIVE PREVIEW

Semantics for Model Debugging Simon Van Mierlo Yentl Van Tendeloo - - PowerPoint PPT Presentation

A Generalized Stepping Semantics for Model Debugging Simon Van Mierlo Yentl Van Tendeloo Hans Vangheluwe firstname.lastname@uantwerpen.be October 16, MDEbug18, Copenhagen, Denmark Motivation MS4Me DEVS Debugger (AToMPM)


slide-1
SLIDE 1

A Generalized Stepping Semantics for Model Debugging

Simon Van Mierlo Yentl Van Tendeloo Hans Vangheluwe

firstname.lastname@uantwerpen.be October 16, MDEbug’18, Copenhagen, Denmark

slide-2
SLIDE 2

Motivation

  • MS4Me
  • DEVS Debugger (AToMPM)
  • DEVS-Suite
  • Statecharts Debugger

(AToMPM)

slide-3
SLIDE 3

Motivation

  • Non-Standard Vocabulary:
  • Step, Big Step, Small Step, Combo Step, Iteration, Run Until, ...
  • Differs per formalism, per tool
  • Confusing for Users
  • Tool Completeness?
  • New Languages
slide-4
SLIDE 4

System Execution

System INPUT OUTPUT

EXECUTOR/INTERPRETER

slide-5
SLIDE 5

Parallel DEVS

Yentl Van Tendeloo and Hans Vangheluwe. Classic DEVS Modelling and Simulation. In Proceedings of the 2017 Winter Simulation Conference, pages 644-656, 2017. DOI: 10.1109/WSC.2017.8247822

slide-6
SLIDE 6

Example Model (Traffic Light)

Requirements:

  • 1. The traffic light should continuously cycle

between the three lights in this order: green, yellow, red, green, yellow, red, ...,

  • 2. The traffic light should stay green for 57

seconds, stay yellow for 3 seconds, and stay red for 60 seconds. Design:

slide-7
SLIDE 7

Debugging Process

Simon Van Mierlo, Erwan Bousse, Hans Vangheluwe, Manuel Wimmer, Martin Gogolla, Matthias Tichy, and Arnaud Blouin. Report on the 1st international workshop on debugging in model-driven engineering (MDEbug'17). In Proceedings of MODELS 2017 Satellite Events, volume 2019. CEUR-WS, September 2017.

REQ1 REQ2

slide-8
SLIDE 8

Simulation Step

REQ1 REQ2 PDEVS Model

slide-9
SLIDE 9

Black-Box Step: Output

R2: The traffic light should stay green for 57 seconds, stay yellow for 3 seconds, and stay red for 60 seconds.

slide-10
SLIDE 10

White-Box Step: State

R2: The traffic light should stay green for 57 seconds, stay yellow for 3 seconds, and stay red for 60 seconds.

slide-11
SLIDE 11

Implementation Step: Executor

R2: The traffic light should stay green for 57 seconds, stay yellow for 3 seconds, and stay red for 60 seconds.

slide-12
SLIDE 12

From Requirements to Implementation

slide-13
SLIDE 13

Applications

  • Tool Completeness
  • Hybrid Languages
  • Domain-Specific Languages
slide-14
SLIDE 14

Conclusion

  • Levels of Stepping:
  • Simulation, Black-Box, White-Box, Implementation
  • Based on System Execution
  • Requirement, Input/Output Trace, State Trace, Implementation Trace
  • Future Work:
  • Evaluation (+ iteration)
  • Map onto well-known formalisms
  • Language fragments