Specification before satisfaction: the case for research into obtaining the right specification

Authors:
Cliff B. Jones
Affiliations:
University of Newcastle upon Tyne, Newcastle, UK
Venue:
ZB'05 Proceedings of the 4th international conference on Formal Specification and Development in Z and B
Year:
2005

Citing 6
Cited 0

Systematic software development using VDM (2nd ed.)

Systematic software development using VDM (2nd ed.)
Understanding the differences between VDM and Z

ACM SIGSOFT Software Engineering Notes
The B-book: assigning programs to meanings

The B-book: assigning programs to meanings
Mechanizing proof: computing, risk, and trust

Mechanizing proof: computing, risk, and trust
Software Development: A Rigorous Approach

Software Development: A Rigorous Approach
Dependability: Basic Concepts and Terminology

Dependability: Basic Concepts and Terminology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Model-oriented specification techniques like VDM [Jon80,Jon90], Z [Hay93] and B [Abr96] have an enormous amount in common (cf. [Hay92,HJN94]). Among other things that this formal methods community shares is the view that one can start with a formal specification and show that a design/implementation satisfies that specification. It is however obvious that, if a specification does not actually reflect the real need, proving a program correct with respect to it is somewhat pointless.