Scenario-based modeling and synthesis for reactive systems with dynamic system structure in scenario tools

Joel Greenyer, Daniel Gritzner, Guy Katz, Assaf Marron

Research output: Contribution to journalConference articlepeer-review

23 Scopus citations

Abstract

Software-intensive systems such as communicating cars or collaborating robots consist of multiple interacting components, where physical or virtual relationships between components change at run-time. This dynamic system structure influences the components' behavior, which again affects the system's structure. With the often distributed and concurrent nature of the software, this causes substantial complexity that must be mastered during system design. For this purpose, we propose a specification method that combines scenario-based modeling and graph transformations. The specifications are executable and can be analyzed via simulation. We furthermore developed a formal synthesis procedure that can find inconsistencies or prove the specification's realizability. This method is implemented in Scenario Tools, an Eclipse-based tool suite that combines the Scenario Modeling Language, an extended variant of LS Cs, and graph transformations modeled with Henshin. The particular novelty is the synthesis support for systems with dynamic structure.

Original languageEnglish
Pages (from-to)16-23
Number of pages8
JournalCEUR Workshop Proceedings
Volume1725
StatePublished - 2016
Externally publishedYes
Event2016 MoDELS Demo and Poster Sessions, MoDELS-D and P 2016 - Saint-Malo, France
Duration: 2 Oct 20167 Oct 2016

Keywords

  • Analysis
  • Controller synthesis
  • Dynamic system structure
  • Graph transformation
  • Live sequence charts
  • Reactive systems
  • Realizability
  • Scenario Modeling Language
  • Scenario-based specification
  • Specification inconsistency

Fingerprint

Dive into the research topics of 'Scenario-based modeling and synthesis for reactive systems with dynamic system structure in scenario tools'. Together they form a unique fingerprint.

Cite this