English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

It is a common belief that the rise of standardized software certication schemes like the Common Criteria (CC) would give a boost to formal verication, and that software certication may be a killer application for program verication. However, while formal models are indeed used throughout high-assurance certication, verication of the actual implementation is not required by the CC and largely neglected in certication practice { despite the great advances in program verication over the last decade. In this paper we discuss the gap between program verication and CC software certication, and we point out possible uses of code-level program verication in the CC certication process.

Mind the Gap: Formal Verification and the Common Criteria (Discussion Paper)