Proceedings ASE 2000. Fifteenth IEEE International Conference on Automated Software Engineering 2000
DOI: 10.1109/ase.2000.873645
|View full text |Cite
|
Sign up to set email alerts
|

Model checking programs

Abstract: Abstract. The majority of work carried out in the formal methods community throughout the last three decades has (for good reasons) been devoted to special languages designed to make it easier to experiment with mechanized formal methods such as theorem provers, proof checkers and model checkers. In this paper we will attempt to give convincing arguments for why we believe it is time for the formal methods community to shift some of its attention towards the analysis of programs written in modern programming l… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

1
743
0
6

Year Published

2006
2006
2013
2013

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 596 publications
(750 citation statements)
references
References 54 publications
1
743
0
6
Order By: Relevance
“…Model checking is a formal approach for systematically exploring all possible behaviors of a concurrent software system [9,17,25,3]. The state space explosion problem renders it intractable in verifying medium to large-sized programs.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Model checking is a formal approach for systematically exploring all possible behaviors of a concurrent software system [9,17,25,3]. The state space explosion problem renders it intractable in verifying medium to large-sized programs.…”
Section: Related Workmentioning
confidence: 99%
“…Explicit state model checking enumerates all possible thread schedules and input data values of a program in order to check for errors [9,25]. Whereas symbolic execution techniques substitute certain data values with symbolic values while all other values are concrete [11,24,16].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…To perform white box tests in the style of Pathfinder [11], SpecExplorer [8], or Korat [4], it is necessary to make the program paths explicit in the program representation and amenable to the rules of the operational semantics. Therefore, a pre-processing step is necessary that unfolds all WHILE -loops up to a certain limit, the unwind-factor k. This principle can also be applied in a language extension with procedure calls such as IMPP, also available in the Isabelle distribution.…”
Section: Unwinding Imp Programsmentioning
confidence: 99%
“…In Sec. 5, we will exploit the underlying generality of Isabelle for a different testing technique in the style of Pathfinder [11], SpecExplorer [8], and Korat [4]. The approach is based on a suitable semantic presentation of a programming language (a "logical embedding"), which can be used to both derive semantic constraints underlying a test as well as solving them in an integrated way.…”
Section: Introductionmentioning
confidence: 99%