2006
DOI: 10.1007/11730637_37
|View full text |Cite
|
Sign up to set email alerts
|

Interchange Format for Hybrid Systems: Abstract Semantics

Abstract: In [1] we advocated the need for an interchange format for hybrid systems that enables the integration of design tools coming from many different research communities. In deriving such interchange format the main challenge is to define a language that, while presenting a particular formal semantics, remains general enough to accommodate the translation across the various modeling approaches used in the existing tools. In this paper we give a formal definition of the syntax and semantics for the proposed interc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
16
0

Year Published

2006
2006
2017
2017

Publication Types

Select...
3
3
2

Relationship

1
7

Authors

Journals

citations
Cited by 26 publications
(16 citation statements)
references
References 12 publications
0
16
0
Order By: Relevance
“…However, we also believe that combining and leveraging HSIF, Modelica, and the Metropolis metamodel, we can push for the foundations of a standard interchange format as well as a standard design capture language where semantics is favored over syntax. Consequently, we have made a first step in this direction by proposing a new interchange format and by presenting some examples of its application to the definition of a design flow that includes HyVisual, Modelica and CheckMate to enter the design, simulate it and formally verify its properties [145,144]. The new interchange format is at this point a proposal, since work still needs to be done to support it with the appropriate debugging and analysis tools and with translators to and from existing tools.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…However, we also believe that combining and leveraging HSIF, Modelica, and the Metropolis metamodel, we can push for the foundations of a standard interchange format as well as a standard design capture language where semantics is favored over syntax. Consequently, we have made a first step in this direction by proposing a new interchange format and by presenting some examples of its application to the definition of a design flow that includes HyVisual, Modelica and CheckMate to enter the design, simulate it and formally verify its properties [145,144]. The new interchange format is at this point a proposal, since work still needs to be done to support it with the appropriate debugging and analysis tools and with translators to and from existing tools.…”
Section: Discussionmentioning
confidence: 99%
“…The abstract semantics of the interchange format proposed in [145] is reported in [144]. To facilitate the customization to a specific semantics, the model designer uses generic schedulers and refines their implementation by defining the behavior of certain abstract functions that are invoked during a scheduling cycle.…”
Section: Metropolis-based Abstract Semantics For Hybrid Systemsmentioning
confidence: 99%
See 1 more Smart Citation
“…This evolution can be seen in the hybrid systems [83], embedded systems [34], and security [55] communities. However, the immediacy of behavioral issues has dominated the spotlight, leaving issues in the structural regime behind.…”
Section: Introductionmentioning
confidence: 99%
“…UPPAAL is primarily a model-checker for timed automata (Alur and Dill, 1994), however, it also supports statistical model-checking of hybrid systems (David et al, 2011(David et al, ). 2013Beohar et al, 2010) and HSIF (Pinto et al, 2006) solve the complexity problem of one format translation to another by performing at most two translations, the approach still suffers from the fact that UPPAAL features like committed locations and C-like function code are not supported in SPACEEX and UPPAAL has limited support for ODEs. Moreover, by using co-simulation, we are able to take advantage not just of the specific strengths of the language of each tool, but also of their native simulation engines, since each FMU is internally running essentially a "copy" of the simulation algorithm of the original tool.…”
Section: Introductionmentioning
confidence: 99%