ACM Home Page
Please provide us with feedback. Feedback
Defining and translating a "safe" subset of simulink/stateflow into lustre
Full text PdfPdf (229 KB)
Source International Conference On Embedded Software archive
Proceedings of the 4th ACM international conference on Embedded software table of contents
Pisa, Italy
SESSION: Formal languages table of contents
Pages: 259 - 268  
Year of Publication: 2004
ISBN:1-58113-860-1
Authors
N. Scaife  VERIMAG, Gieres, France
C. Sofronis  VERIMAG, Gieres, France
P. Caspi  VERIMAG, Gieres, France
S. Tripakis  VERIMAG, Gieres, France
F. Maraninchi  VERIMAG, Gieres, France
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 48,   Citation Count: 6
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1017753.1017795
What is a DOI?

ABSTRACT

The Simulink/Stateflow toolset is an integrated suite enabling model-based design and has become popular in the automotive and aeronautics industries. We have previously developed a translator called Simtolus from Simulink to the synchronous language Lustre and we build upon that work by encompassing Stateflow as well. Stateflow is problematical for synchronous languages because of its unbounded behaviour so we propose analysis techniques to define a subset of Stateflow for which we can define a synchronous semantics. We go further and define a "safe" subset of Stateflow which elides features which are potential sources of errors in Stateflow designs. We give an informal presentation of the Stateflow to Lustre translation process and show how our model-checking tool Lesar can be used to verify some of the semantical checks we have proposed. Finally, we present a small case-study.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
C. Banphawatthanarak, B. H. Krogh, and K. Butts. Symbolic verification of executable control specifications. In Proc. of the Tenth IEEE International Symposium on Computer Aided Control System Design, pages 581--586, Hawaii, Aug 1999.
 
2
S. Bensalem, V. Ganesh, Y. Lakhnech, C. M. Noz, S. Owre, H. Rueß, J. Rushby, V. Rusu, H. Saïdi, N. Shankar, E. Singerman, and A. Tiwari. An overview of SAL. In C. M. Holloway, editor, LFM 2000: Fifth NASA Langley Formal Methods Workshop, pages 187--196, Hampton, VA, Jun 2000.
 
3
 
4
P. Caspi, A. Curic, A. Maignan, C. Sofronis, and S. Tripakis. Translating discrete-time Simulink to Lustre. In R. Alur and I. Lee, editors, EMSOFT'03, LNCS. Springer Verlag, 2003.
5
 
6
Ford. Structured Analysis Using Matlab/Simulink/Stateflow - Modeling Style Guidelines. Technical report, Ford Motor Company, 1999.
 
7
N. Halbwachs, P. Caspi, P. Raymond, and D. Pilaud. The synchronous data-flow programming language LUSTRE. Proc. of the IEEE, 79(9):1305--1320, September 1991.
 
8
 
9
G. Hamon and J. Rushby. An operational semantics for stateflow. In Proc. of Fundamental Approaches to Software Engineering, Barcelona, Spain, March 2004.
 
10
 
11
12
 
13
 
14
F. Maraninchi and Y. Rémond. Argos: an Automaton-Based Synchronous Language. Computer Languages, (27):61--92, 2001.
 
15
 
16
N. Scaife, C. Sofronis, P. Caspi, S. Tripakis, and F. Maraninchi. Defining and translating a ``safe'' subset of Simulink/Stateflow into Lustre. Technical Report TR-2004-16, http://www-verimag.imag.fr.
 
17
 
18
A. Tiwari. Formal semantics and analysis methods for Simulink Stateflow models. Technical report, http://www.csl.sri.com/~tiwari/stateflow.html.


Collaborative Colleagues:
N. Scaife: colleagues
C. Sofronis: colleagues
P. Caspi: colleagues
S. Tripakis: colleagues
F. Maraninchi: colleagues