2018
DOI: 10.1007/978-3-319-70578-1_4
|View full text |Cite
|
Sign up to set email alerts
|

Initial Steps Towards Assessing the Usability of a Verification Tool

Abstract: In this paper we report the experience of using AutoProof for static verification of a small object oriented program. We identify the problems that emerge by this activity and classify them according to their nature. In particular, we distinguish between tool-related and methodology-related issues, and propose necessary changes to simplify both the tool and the method.1 A cipher for an integrated set of tools checking correctness in a broad sense [1,2]

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
1
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 12 publications
0
3
0
Order By: Relevance
“…All methods in classes are specified with pre-/postconditions and invariants for verification purposes. The tool AutoProof [29,49] is used to verify the correctness of implemented methods. It translates methods to logic formulas, and an SMT solver proves the correctness.…”
Section: Related Workmentioning
confidence: 99%
“…All methods in classes are specified with pre-/postconditions and invariants for verification purposes. The tool AutoProof [29,49] is used to verify the correctness of implemented methods. It translates methods to logic formulas, and an SMT solver proves the correctness.…”
Section: Related Workmentioning
confidence: 99%
“…Classes and methods are annotated with pre-/postconditions and invariants. Programs written in Eiffel can be verified using AutoProof [18,28]. The verification tool translates the program with assertions to a logic formula.…”
Section: Related Workmentioning
confidence: 99%
“…Despite major conceptual and technological advances, game designers still use the same instruments, and this is not on par with comparable entertainment industries [1], [23], or other well-established fields where the discussion spans over tools and methodologies [10], [22]. Part of the explanation comes from the scarce usability of modern software verification tools that often still requires help from the experts or good mathematical background from the developers, or possibly both [14]. For testing purposes, Test Driven Development (TDD) [20] is usually used in practice but, since tests cover just a subset of the set of all possible executions of a program, TDD helps only to find bugs, but not to prove their absence.…”
Section: Introductionmentioning
confidence: 99%