How the design of JML accommodates both runtime assertion checking and formal verification (Q1776585): Difference between revisions
From MaRDI portal
Changed an Item |
Set OpenAlex properties. |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Property / describes a project that uses | |||
| Property / describes a project that uses: Korat / rank | |||
Normal rank | |||
| Property / describes a project that uses | |||
| Property / describes a project that uses: LARCH / rank | |||
Normal rank | |||
| Property / MaRDI profile type | |||
| Property / MaRDI profile type: MaRDI publication profile / rank | |||
Normal rank | |||
| Property / OpenAlex ID | |||
| Property / OpenAlex ID: W2035529004 / rank | |||
Normal rank | |||
Latest revision as of 22:36, 19 March 2024
scientific article
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | How the design of JML accommodates both runtime assertion checking and formal verification |
scientific article |
Statements
How the design of JML accommodates both runtime assertion checking and formal verification (English)
0 references
12 May 2005
0 references
Specification languages
0 references
Runtime assertion checking
0 references
Formal methods
0 references
Program verification
0 references
Programming by contract
0 references
Java language
0 references
JML language
0 references
