Advertisement

Specification Before Satisfaction: The Case for Research into Obtaining the Right Specification —Extended Abstract—

  • Cliff B. Jones
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3455)

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.

Keywords

Advisory System Batch Processor Psychological Type Normal Accident Mode Confusion 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [Abr96]
    Abrial, J.-R.: The B-Book: Assigning programs to meanings. Cambridge University Press, Cambridge (1996)MATHCrossRefGoogle Scholar
  2. [Bjø05]
    Bjørner, D.: Software Engineering, 3vols. Springer, Heidelberg (2005)Google Scholar
  3. [Hay92]
    Hayes, I.J.: VDM and Z: A comparative case study. Formal Aspects of Computing 4(1), 76–99 (1992)MATHCrossRefGoogle Scholar
  4. [Hay93]
    Hayes, I. (ed.): Specification Case Studies, 2nd edn. Prentice Hall International, Englewood Cliffs (1993)MATHGoogle Scholar
  5. [HJJ03]
    Hayes, I., Jackson, M., Jones, C.: Determining the specification of a control system from that of its environment. In: Araki, K., Gnesi, S., Mandrioli, D. (eds.) FME 2003. LNCS, vol. 2805, pp. 154–169. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  6. [HJN94]
    Hayes, I.J., Jones, C.B., Nicholls, J.E.: Understanding the differences between VDM and Z. ACM Software Engineering News 19(3), 75–81 (1994)CrossRefGoogle Scholar
  7. [Jon80]
    Jones, C.B.: Software Development: A Rigorous Approach. Prentice Hall International, Englewood Cliffs (1980) ISBN 0-13-821884-6MATHGoogle Scholar
  8. [Jon83]
    Jones, C.B.: Specification and design of (parallel) programs. In: Proceedings of IFIP 1983, pp. 321–332. North-Holland, Amsterdam (1983)Google Scholar
  9. [Jon90]
    Jones, C.B.: Systematic Software Development using VDM, 2nd edn. Prentice Hall International, Englewood Cliffs (1990) ISBN 0-13-880733-7MATHGoogle Scholar
  10. [Jon03]
    Jones., C.B.: A formal basis for some dependability notions. In: Aichernig, B.K., Maibaum, T. (eds.) Formal Methods at the Crossroads. From Panacea to Foundational Support. LNCS, vol. 2757, pp. 191–206. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  11. [Lap92]
    Laprie, J.-C.: Dependability: basic concepts and terminology—in English, French, German, Italian and Japanese. Springer, Heidelberg (1992)MATHGoogle Scholar
  12. [Mac94]
    MacKenzie, D.: Computer-related accidental death: an empirical exploration. Science and Public Policy 21, 233–248 (1994)Google Scholar
  13. [Mac01]
    MacKenzie, D.: Mechanizing Proof: Computing, Risk, and Trust. MIT Press, Cambridge (2001)MATHGoogle Scholar
  14. [Per99]
    Perrow, C.: Normal Accidents. Princeton University Press, Princeton (1999)Google Scholar
  15. [Ran00]
    Randell, B.: Facing up to faults. The Computer Journal 43(2), 95–106 (2000)CrossRefGoogle Scholar
  16. [Rea90]
    Reason, J.: Human Error. Cambridge University Press, Cambridge (1990)Google Scholar
  17. [Rea97]
    Reason, J.: Managing the Risks of Organisational Accidents. Ashgate Publishing Limited (1997)Google Scholar
  18. [Rus99]
    Rushby, J.: Using model checking to help discover mode confusions and other automation surprises. In: Proceedings of 3rd Workshop on Human Error, HESSD 1999, pp. 1–18 (1999)Google Scholar
  19. [SPA03]
    Strigini, L., Povyakalo, A., Alberdi, E.: Human machine diversity in the use of computerised advisory systems: A case study. In: DSN 2003-IEEE International Conference on Dependable Systems and Networks, San Francisco, USA, pp. 249–258 (2003)Google Scholar
  20. [Wei71]
    Weinberg, G.M.: The Psychology of Computer Programming, Van Norstrand (1971)Google Scholar
  21. [WWW04]

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Cliff B. Jones
    • 1
  1. 1.University of Newcastle upon TyneNewcastleUK

Personalised recommendations