NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.

Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.

U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

PUBLICATIONS

Is 'Implementation Implies Specification' Enough?

Published

Author(s)

Paul E. Black

Abstract

An implementation is typically checked against a specification by proving that the implementation implies the specification. This ensures that the implementation only has behaviors allowed by the specification. However, this does not require the implementation to have any behavior to all!We propose that correctness statements have two parts, corresponding to liveness and safety. Safety is that the implementation implies an allowed behavior specification, as now. Livenenss is that a
Citation
Design Automation Conference
Pub Type
Journals

Download Paper

Local Download

Keywords

correctness, formal specification, verification

Citation

Black, P. (2000), Is 'Implementation Implies Specification' Enough?, Design Automation Conference, [online], https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=151671 (Accessed October 2, 2025)

Issues

If you have any questions about this publication or are having problems accessing it, please contact [email protected].

Created June 1, 2000, Updated February 17, 2017
Was this page helpful?