Formal system specifications: A case study of three diverse representations
1990
Abstract
The only effective way to raise the confidence level of a program significantly is to give a convincing proof of its correctness. But one should not first make the program and then prove its correctness, because then the requirement of providing the proof would only increase the poor programmer's burden. On the contrary: the programmer should let correctness proof and program grow hand in hand. 21 refs., 15 figs.
Related Papers
- → An uncaught exception analysis for Java(2003)48 cited
- Formal Proof for the Correctness of RSA-PSS.(2006)
- → Semantical Correctness of Simulation-to-Animation Model and Rule Transformation(2024)4 cited
- An uncaught exception analysis for Java q,qq(2004)
- C++ Programmer's Companion: Designing, Testing, and Debugging(1992)