source: papers/FDL2012/FDL2012.tex @ 74

Last change on this file since 74 was 66, checked in by cecile, 13 years ago

refinement with property first part

File size: 3.9 KB
RevLine 
[54]1 \documentclass{article}
2
3  \usepackage{spconf}
4\usepackage{cmap}
5\usepackage[utf8]{inputenc}
6\usepackage[T1]{fontenc}
7\usepackage{lmodern}
8\usepackage{textcomp}
9\usepackage{amsmath}
10\usepackage{amssymb}
11\usepackage{amsfonts}
12\usepackage{bbm}
13\usepackage{bbold}
14\usepackage{amsthm}
15\usepackage{array}
16\usepackage{verbatim}
17\usepackage{hyperref}
18\usepackage{booktabs}
19\usepackage{graphicx}
20\usepackage{tikz}
21\usepackage{pgf}
22\usetikzlibrary{arrows,automata}
23\usepackage[francais, american]{babel}
24\usepackage[babel=true,kerning=true]{microtype}
[65]25\usepackage[ruled]{algorithm2e}
[54]26
[66]27
28\graphicspath{{schema/}}
[54]29\newtheorem{definition}{Definition}
30\newtheorem{property}{Property}
31\newcommand{\TODO}[1] {\textcolor{red}{TODO : #1}}
32\newcommand{\remark}[2]{\textcolor{blue}{#1: #2}}
33
34
35 \title{ Compositional System Verification: Exploiting components' verified properties in the abstraction-refinement process}
36 \name{Syed Hussein S. ALWI, Emmanuelle ENCRENAZ and C\'{e}cile BRAUNSTEIN}
37% \thanks{This work was supported by...}}
38 \address{Universit\'{e} Pierre et Marie Curie Paris 6, \\
39                 LIP6-SOC (CNRS UMR 7606), \\
40                            4, place Jussieu, \\
41                75005 Paris, FRANCE. }
42
43\begin{document}
44 % OPTIONAL -->   \ninept            <-- OPTIONAL, for nine pt only
45
46\maketitle
47
48\begin{abstract}
49Embedded systems are usually composed of several components and in practice, these components generally have been independently verified to ensure that they respect their specifications before being integrated into a larger system. Therefore, we would like to exploit the specification (i.e. verified CTL properties) of the components in the objective of verifying a global property of the system. A complete concrete system may not be directly verifiable due to the state explosion problem, thus abstraction and eventually refinement process are required. In this paper, we propose a technique to select properties in order to generate a good abstraction and reduce refinement iterations. We have tested this technique on a set of benchmarks which shows that our approach is promising in comparison to other abstraction-refinement techniques.
50\end{abstract}
51
52\begin{keywords}
53Compositional verification, CTL properties, CEGAR, model-checking
54\end{keywords}
55
56
57%\def\abstract{\begin{center}
58%{\bf ABSTRACT\vspace{-.5em}\vspace{0pt}}
59%\end{center}}
60%\def\endabstract{\par}
61
62\section{Introduction}
63
64\input{introduction}
65
66
67\section{Our Framework}
68
69\input{framework}
[56]70\section{Refinement}
[54]71
72\input{abstraction_refinement}
73
74
75
76\section{Experimental results}
77
[64]78 \input{exp_results}
[54]79
80
81
82
83\section{Conclusion and Future Works}
84
85%\section*{Drawbacks}
86
87We have presented a new strategy in the abstraction generation and refinement which is well adapted for compositional embedded systems. This verification technique is compatible and suits well in the natural development process of complex systems. Our preliminary experimental results shows an interesting performance in terms duration of abstraction generation and the number of refinement iteration. Futhermore, this technique enables us to overcome repetitive counterexamples due to the presence of cycles in the system's graph.
88
[64]89Nevertheless, in order to function well, this refinement technique requires a complete specification of every components of the concrete model. Futhermore, it may be possible that none of the properties available is capable of eliminating the counterexample which probably due to the fact that the specification is not complete or counterexample given is provoqued by the composition of components. In this case, other refinement techniques such as the refinement by eliminating the counterexample only techniques should be considered. We are currently investigating other complementary techniques to overcome these particular cases.
[54]90
91
92
93%\begin{thebibliography}
94 \ninept
95%  <-- OPTIONAL, for nine pt only
96%\bibliographystyle{plain}
97\bibliographystyle{IEEEbib}
98\bibliography{myBib}
99
100%\end{thebibliography}
101
102
103
[64]104\end{document} 
Note: See TracBrowser for help on using the repository browser.