Name
Abstract | ||
|---|---|---|
Programming errors found early are the cheapest. Tools applying to the early stage of code development exist but either they suffer from false positives ("noise") or they require strong user interaction. We propose to avoid this deficiency by defining a new class of errors. A program fragment is doomed if its execution will inevitably fail, in whatever state it is started. We use a formal verification method to identify such errors fully automatically and, most significantly, without producing noise. We report on preliminary experiments with a prototype tool. |
Year | DOI | Venue |
|---|---|---|
2009 | 10.1007/978-3-642-05089-3_22 | FM |
Keywords | DocType | Volume |
code development,false positive,strong user interaction,program fragment,early stage,preliminary experiment,new class,programming error,formal verification method,prototype tool,formal verification | Conference | 5850 |
ISSN | Citations | PageRank |
0302-9743 | 16 | 0.80 |
References | Authors | |
17 | 5 | |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Jochen Hoenicke | 1 | 292 | 20.43 |
| Rustan, K. | 2 | 3995 | 301.64 |
| Andreas Podelski | 3 | 2760 | 197.87 |
| Martin Schäf | 4 | 135 | 14.71 |
| Thomas Wies | 5 | 515 | 28.26 |