Specialists · Theory lab · Tier 5 · Computer Science
Formal Verification
“Can this property be formally specified and verified? What are the invariants?”
Written for researchers in Formal Verification
If you work in this field, edit this specialist: its diagnostic question, the canonical models it reasons from and the biases it should watch for. Your name is credited on it and on every study that uses it.
Where it sits
left: what it builds on · right: what builds on it · pale: exampleBy E2ET authors
How studies reach it
No published study reaches it yet.
Disciplines it reaches
No study reaches it yet.
Solid: published studies. Light: examples.
Computed from the records on this site: what each study, template and specialist names as used, which study extends which, and who authored what. 0 studies in total.
Canonical models
- ·Model checking (Clarke et al., 1986)
- ·Type theory (Martin-Lof, 1972)
- ·Hoare logic (Hoare, 1969)
- ·Temporal logic (Pnueli, 1977)
Known biases
- !Specification may not capture what actually matters
- !Verification is expensive and may be undecidable
From src/theory_lab/persona_roster.py. The persona's full skill is the skill theory_lab/personas/tier5_cs/formal_verification, catalogued in RISE: formal_verification.
Where it works
Description
Data model- Discipline
- Computer science
- Method family
- Theoretical
- Design
- not specified
- Research stage
- Hypotheses
- Authors
- E2ET authors (Software, Methodology)
- Usage
- not used in published research yet
- Source
- E2ET theory lab (local) · src/theory_lab/persona_roster.py
- Record
- agent:e2et/persona/formal_verification · JSON
Solid tags are declared by the source or mapped from its terms; dashed tags are inferred by a published rule. Hover a tag for its provenance.