Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21d4a780fb2a151

Jump to content

// Workers AI · dad joke modeWhat did model-based specification say to its date? You're a perfect match.

From Wikipedia, the free encyclopedia

Model-based specification is an approach to formal specification where the system specification is expressed as a system state model. This state model is constructed using well-understood mathematical entities such as sets and functions. System operations are specified by defining how they affect the state of the system model.

The most widely used notations for developing model-based specifications are VDM[1][2] and Z[3][4] (pronounced Zed, not Zee). These notations are based on typed set theory. Systems are therefore modelled using sets and relations between sets.

Another well-known approach to formal specification is algebraic specification.

See also

[edit]

References

[edit]
  1. Cliff B. Jones (1980). Software Development: A Rigorous Approach. Prentice Hall International. ISBN 0-13-821884-6.
  2. Cliff B. Jones (1986). Systematic Software Development using VDM. Prentice Hall International. ISBN 0-13-880717-5.
  3. Ian J. Hayes (May 1986). "Using mathematics to specify software" (PDF). Proceedings of the 1st Australian Software Engineering Conference. ASWEC-86. pp. 67–71.
  4. J. Michael Spivey (1992). The Z Notation: A reference manual (2nd ed.). Prentice Hall International Series in Computer Science. ISBN 0-13-978529-9. Archived from the original on 2008-10-09. Retrieved 2010-10-24.