Mechanical software verification: high level control aspects from a user's perspective

DOI10.1016/S1571-0661(04)00282-8zbMATH Open1268.68111OpenAlexW2026989220MaRDI QIDQ2841237FDOQ2841237

Authors: Wolfgang Goerigk 

Publication date: 24 July 2013

Published in: Electronic Notes in Theoretical Computer Science (Search for Journal in Brave)

Full work available at URL: https://doi.org/10.1016/s1571-0661(04)00282-8

Recommendations

• Mechanized result verification: An industrial application
• Overview on mechanized theorem proving
• scientific article; zbMATH DE number 2177632
• Software verification with ITPs should use binary code extraction to reduce the TCB (short paper)
• scientific article; zbMATH DE number 1746646

Mathematics Subject Classification ID

Specification and verification (program logics, model checking, etc.) (68Q60)

Cites Work

• Title not available (Why is that?)
• An axiomatic basis for computer programming
• SPECIFICATION AND VERIFICATION OF CONURRENT SYSTEMS IN CESAR
• Title not available (Why is that?)
• Compiler specification and verification
• Title not available (Why is that?)
• Title not available (Why is that?)
• Title not available (Why is that?)
• Weakest relative precondition semantics. Balancing approved theory and realistic translation verification
• Title not available (Why is that?)

Cited In (3)

• Mechanized result verification: An industrial application
• An integrated approach to high integrity software verification
• Software verification with ITPs should use binary code extraction to reduce the TCB (short paper)

Uses Software

• ACL2
• PVS
• CESAR
• Piton
• ComLisp

This page was built for publication: Mechanical software verification: high level control aspects from a user's perspective

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q2841237)