Proceedings of the 8th Computer Science Education Research Conference 2019
DOI: 10.1145/3375258.3375265
|View full text |Cite
|
Sign up to set email alerts
|

Is Deductive Program Verification Mature Enough to be Taught to Software Engineers?

Abstract: Article 25fa pilot End User AgreementThis publication is distributed under the terms of Article 25fa of the Dutch Copyright Act (Auteurswet) with explicit consent by the author. Dutch law entitles the maker of a short scientific work funded either wholly or partially by Dutch public funds to make that work publicly available for no consideration following a reasonable period of time after the work was first published, provided that clear reference is made to the source of the first publication of the work.This… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
1
1

Relationship

2
0

Authors

Journals

citations
Cited by 2 publications
(4 citation statements)
references
References 22 publications
0
4
0
Order By: Relevance
“…Like [31], only general purpose, well-understood verification methods were used. Why3 in particular has an easy learning curve [30]. Our method for translating C and assembly code into WhyML is straight-forward, and the AVR model of Section 4.1 can be validated, so trust in our results mainly resides with trusting the verification condition generation of Why3, the soundness of the automated provers, and the compilation-toolchain (C compiler, assembler and linker) used for producing AVR binaries.…”
Section: Discussionmentioning
confidence: 90%
See 1 more Smart Citation
“…Like [31], only general purpose, well-understood verification methods were used. Why3 in particular has an easy learning curve [30]. Our method for translating C and assembly code into WhyML is straight-forward, and the AVR model of Section 4.1 can be validated, so trust in our results mainly resides with trusting the verification condition generation of Why3, the soundness of the automated provers, and the compilation-toolchain (C compiler, assembler and linker) used for producing AVR binaries.…”
Section: Discussionmentioning
confidence: 90%
“…We describe our approach in using Why3 for this verification task; this is an extension of earlier work [29], and has been demonstrated to be have low barrier to understanding [30]. This approach would work similarly well for other architectures such as ARM or RISC-V.…”
Section: Contributionsmentioning
confidence: 89%
“…Like [32], only general purpose, well-understood verification methods were used. Why3 in particular has an easy learning curve [31]. Our method for translating C and assembly code into WhyML is straight-forward, and the AVR model of Sect.…”
Section: Discussionmentioning
confidence: 99%
“…We describe our approach in using Why3 for this verification task; this is an extension of earlier work [30], and has been demonstrated to have a low barrier to understanding [31]. This approach should work similarly well for other architectures such as ARM or RISC-V.…”
Section: Contributionsmentioning
confidence: 92%