Skip to main content
Log in

Using a formal specification contractually

  • Published:
Formal Aspects of Computing

Abstract

A commonly made criticism of formal methods is that they increase costs. Selective use of formal methods to define critical requirements can, however, lead to a significant decrease in lifecycle costs. In particular the economic and technical benefits of outsourcing the development of software can be fully realized and the cost of outsourcing slightly reduced by use of a formal specification. In this paper we describe a development in which a formal specification prepared by the customer formed part of the contract with the supplier. We conclude that this use of a formal specification can reduce risks and costs for all concerned and can help foster fruitful and co-operative relations in situations which are often fraught with confrontation.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. Bramson, B. D.:Tools for the specification, design, analysis and verification of software, RSRE report 87005, 1987.

  2. Eds. Stephen Brien, John Nichols,Z base standard — version 1.0. ZIP DTI/IED project number 1639. Deliverable D1.3.3, November 1992.

  3. Carré, B. A., Jennings, T. J., Maclennan, F. J., Farrow, P. F. and Garnsworthy, P. F.:SPARK — The SPADE Ada Kernel (Edition 3.1). Program Validation Ltd.

  4. Granville, R. J. and O'Halloran, C.:Malpas IL (version 3.2), RSRE memorandum 3731, 1986.

  5. Hewitt, M. A.:Optimization of Prolog Generated from Z Specifications, M.Sc Project Report 1992, Department of Computing Science, University of Aberdeen.

  6. Hewitt, R. J., O'Halloran, C. and Sennett, C. T.:Experiences with PiZA, an animator for Z, in J. P. Bowen et al, editors, Proceedings ZUM'97, LNCS 1212, Springer April 1997.

  7. Knuth, D. E.:Literate Programming, Computer Journal, Vol. 27, No. 2, 1984

  8. Morgan, C.:Programming from Specifications, Prentice Hall 1990.

  9. O'Halloran, C. M., Sennett, C. T. and Smith, A.:Refinement of Z to SPARK (Volumes 1,2,3), DRA 1994, http://daedalus.dra.hmg.gb/hewitt/swi/swi.html.

  10. Program Validation Limited,The formal semantics of SPARK, March 1994, http://daedalus.dra.hmg.gb/hewitt/swi/swi.html

  11. Sennett, C. T.:Demonstrating the compliance of Ada programs with Z specifications Proceedings of the 5th Refinement Workshop, London, 8–10th January 1992. SpringerVerlag, 1992.

  12. Ward, N. J.:The static analysis of Safety-Critical Software using MALPAS in R. Genser et al, editors, Safety of Computer Control Systems 1989 (SAFECOMP'89), IFAC/IFIP Workshop, Pergamon Press Oxford.

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to C. O'Halloran.

Additional information

Published with the permission of the controller of Her Britannic Majesty's Stationery Office.

Rights and permissions

Reprints and permissions

About this article

Cite this article

O'Halloran, C., Arthan, R. & King, D. Using a formal specification contractually. Formal Aspects of Computing 9, 349–358 (1997). https://doi.org/10.1007/BF01211295

Download citation

  • Received:

  • Accepted:

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF01211295

Keywords

Navigation