Advertisement

Select Z Bibliography

  • Jonathan Bowen
Conference paper
Part of the Workshops in Computing book series (WORKSHOPS COMP.)

Abstract

This bibliography contains a list of Z references that are either available as published papers, books or technical reports from institutions, or from the librarian or via electronic mail at the Programming Research Group (PRG). The bibliography is in alphabetical order by author name(s).

Keywords

Formal Specification Software Engineer Formal Method Cache Coherence Protocol IEEE Software 
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. [1]
    Gregory D. Abowd. Agents: Communicating interactive processes. In Dan Diaper, David Gilmore, Gilbert Cockton, and Brian Shackel, editors, Human-Computer Interaction: INTERACT’90, pages 143–148. Elsevier Science Publishers B.V. (North-Holland), 1990.Google Scholar
  2. [2]
    Gregory D. Abowd. Formal Aspects of Human-Computer Interaction. DPhil thesis, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, 1991.Google Scholar
  3. [3]
    Gregory D. Abowd, Jonathan P. Bowen, Alan Dix, Michael D. Harrison, and Roger Took. User interface languages: a survey of existing methods. Technical Report PRG-TR-5-89, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, October 1989. Alan Dix, Michael Harrison and Roger Took are members of the Human Computer Interaction Group, Department of Computer Science, University of York. This report was originally produced as part of ESPRIT II project no. 2487: ‘REDO: Maintenance, Validation and Documentation of Software Systems.’ It covers a number of methods, including a chapter on modelling using Z.Google Scholar
  4. [4]
    Jean-Raymond Abrial. The B tool. In G. Goos and J. Hartmanis, editors, VDM-The Way Ahead. Proc. 2nd VDM-Europe Symposium, volume 328 of Lecture Notes in Computer Science, pages 86–87. VDM-Europe, Springer-Verlag, 1988.Google Scholar
  5. [5]
    Jean-Raymond Abrial. The B method for large software, specification, design and coding (abstract). In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 552 of Lecture Notes in Computer Science, pages 398–405. Springer-Verlag, 1991.Google Scholar
  6. [6]
    Jean-Raymond Abrial, S.A. Schuman, and B. Meyer. Specification language. In R.M. McKeag and A.M. Macnaghten, editors, On the Construction of Programs: An Advanced Course, pages 343–410. Cambridge University Press, UK, 1980.Google Scholar
  7. [7]
    Jean-Raymond Abrial and Ib H. Sørensen. KWIC-index generation. In J. Staunstrup, editor, Program Specification: Proceedings of a Workshop, volume 134 of Lecture Notes in Computer Science, pages 88–95. Springer-Verlag, 1981.Google Scholar
  8. [8]
    Antonio J. Alencar and Joseph A. Goguen. OOZE: An object-oriented Z environment. In Pierre America, editor, Proc. ECOOP’91 European Conference on Object-Oriented Programming, volume 512 of Lecture Notes in Computer Science, pages 180–199. Springer-Verlag, 1991.Google Scholar
  9. [9]
    Antonio J. Alencar and Joseph A. Goguen. Two examples in OOZE. Technical Report PRG-TR-25-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, 1991.Google Scholar
  10. [10]
    David B. Arnold, David A. Duce, and Graham J. Reynolds. An approach to the formal specification of configurable models of graphs systems. In Guy Maréchal, editor, Proc. European Computer Graphics Conference and Exhibition, pages 439–463. EUROGRAPHICS’87, Elsevier Science Publishers B.V. (North-Holland), 1987. The paper describes a general framework for the formal specification of modular graphics systems. The approach is illustrated by an example taken from the Graphical Kernel System (GKS) and uses the Z specification notation.Google Scholar
  11. [11]
    David B. Arnold and Graham J. Reynolds. Configuring graphics systems components. Software Engineering Journal, 3(6): 248–256, November 1988.CrossRefGoogle Scholar
  12. [12]
    R.D. Arthan. Formal specification of a proof tool. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 356–370. Springer-Verlag, 1991.Google Scholar
  13. [13]
    R.D. Arthan. On free type definitions in Z. Technical Report DS/FMU/IED/-WRK016, ICL Defence Systems, UK, April 1991.Google Scholar
  14. [14]
    P.B. Austin, K.A. Murray, and A.J. Wellings. File system caching in large point-to-point networks. Software Engineering Journal, 7(1): 65–80, January 1992.CrossRefGoogle Scholar
  15. [15]
    Cecily Bailes and Roger Duke. The ecology of class refinement. In Joseph M. Morris and Roger C. Shaw, editors, Proc. 4th Refinement Workshop, Workshops in Computing, pages 185–196. Springer-Verlag, 1991.Google Scholar
  16. [16]
    M. Bailey. Formal specification using Z. In Proc. Software Engineering anniversary meeting (SEAS), page 99. SEA, 1987.Google Scholar
  17. [17]
    J. Bainbridge, Robin W. Whitty, and John B. Wordsworth. Obtaining structural metrics of Z specifications for systems development. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 269–281. Springer-Verlag, 1991.Google Scholar
  18. [18]
    Jean-Pierre Banâtre. About programming environments. In J-P. Banâtre, S.B. Jones, and D. de Métayer, editors, Prospects for Functional Programming in Software Engineering, volume 1 of Research Reports, chapter 1, pages 1–22. Springer-Verlag, 1991. ESPRIT Project 302.Google Scholar
  19. [19]
    Geoff Barrett. Formal methods applied to a floating-point number system. IEEE Transactions on Software Engineering, 15(5): 611–621, May 1989. This paper presents a formalisation of the IEEE standard for binary floatingpoint arithmetic in Z. The formal specification is refined into four components. The procedures presented form the basis for the floating-point unit of the In-mos IMS T800 transputer. This work resulted in a joint Queen’s Award for technological achievement for Inmos Ltd and the Oxford University Computing Laboratory in 1990. It was estimated that the approach saved a year in development time compared to traditional methods.CrossRefGoogle Scholar
  20. [20]
    S. Baxter. Executing Z specifications. Research and Technology memorandum RT31/009/88, British Telecom Research Laboratories, Martlesham Heath, Ipswich, Suffolk, UK, 1988.Google Scholar
  21. [21]
    Mike Benjamin. A message passing system: An example of combining CSP and Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 221–228. Springer-Verlag, 1990.Google Scholar
  22. [22]
    Marc Benveniste. Operational semantics of a distributed object-oriented language and its Z formal specification. Rapport de recherche 1230, INRIA, France, May 1990.Google Scholar
  23. [23]
    Marc Benveniste. Writing operational semantics in Z: A structural approach. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 164–188. Springer-Verlag, 1991.Google Scholar
  24. [24]
    S. Bera. Structuring for the VDM specification language. In G. Goos and J. Hartmanis, editors, VDM-The Way Ahead. Proc. 2nd VDM-Europe Symposium, volume 328 of Lecture Notes in Computer Science, pages 2–25. VDM-Europe, Springer-Verlag, 1988.Google Scholar
  25. [25]
    M.A. Best. Specification of a Z cross-reference facility. IBM Technical Report TR12.253, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, September 1986.Google Scholar
  26. [26]
    Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors. VDM and Z-Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science. VDM-Europe, Springer-Verlag, 1990. Proc. Third International Symposium of VDM-Europe, 17–21 April 1990, Kiel, Germany. A number of papers concerned with Z were presented [52, 76, 92, 99, 100, 105, 150, 220, 247, 268, 289].Google Scholar
  27. [27]
    David Blyth. The CICS application programming interface: Temporary storage. IBM Technical Report TR12.301, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, December 1990. One of a number of reports on the CICS application programming interface. See also [124, 149, 186].Google Scholar
  28. [28]
    Jonathan P. Bowen. Formal specification and documentation of microprocessor instruction sets. In Harald Schumny and John Molgaard, editors, Proc. EUROMICRO’ 87, Microcomputers: Usage, Methods and Structures, volume 21, pages 223–230. EUROMICRO, Elsevier Science Publishers B.V. (North-Holland), August 1987.Google Scholar
  29. [29]
    Jonathan P. Bowen. The formal specification of a microprocessor instruction set. Technical Monograph PRG-60, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, January 1987. The Z notation is used to define the Motorola M6800 8-bit microprocessor instruction set.Google Scholar
  30. [30]
    Jonathan P. Bowen, editor. Proc. Z Users Meeting, 1 Wellington Square, Oxford, 11 Keble Road, Oxford, UK, December 1987. Oxford University Computing Laboratory. The 1987 Z Users Meeting was held on Friday 8 December at the Department of External Studies, Rewley House, 1 Wellington Square, Oxford, UK. The LATEX [154] source of the Proceedings is available by sending the command “send z proc87.tex” to <archive-server@comlab.ox.ac.uk> via e-mail [299].Google Scholar
  31. [31]
    Jonathan P. Bowen. Formal specification in Z as a design and documentation tool. In Proc. Second IEE/BCS Conference on Software Engineering, volume 290, pages 164–168. IEE/BCS, July 1988.Google Scholar
  32. [32]
    Jonathan P. Bowen, editor. Proc. Third Annual Z Users Meeting, 11 Keble Road, Oxford, UK, December 1988. Oxford University Computing Laboratory. The 1988 Z Users Meeting was held on Friday 16 December at the Department of External Studies, Rewley House, 1 Wellington Square, Oxford, UK. Issued with A Miscellany of Handy Techniques by Ruaridh Macdonald, RSRE, Practical Experience of Formal Specification: a programming interface for communications by John B. Wordsworth, IBM, and a number of posters. This is available from the Librarian at the Oxford University Computing Laboratory. The iATgX [154] source file for the main part of the document is available by sending the command “send z proc88.tex” via e-mail to the PRG archive server on <archive-serverQcomlab.ox.ac.uk> [299].Google Scholar
  33. [33]
    Jonathan P. Bowen. Formal specification of window systems. Technical Monograph PRG-74, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, June 1989. Three existing window systems, X from MIT, WM from Carnegie-Mellon University and the Blit from AT&T Bell Laboratories are covered.Google Scholar
  34. [34]
    Jonathan P. Bowen. POS: Formal specification of a UNIX tool. Software Engineering Journal, 4(1): 67–72, January 1989.MathSciNetCrossRefGoogle Scholar
  35. [35]
    Jonathan P. Bowen. Formal specification of the ProCoS/safemos instruction set. Microprocessors and Microsystems, 14(10): 631–643, December 1990. This article gives a preview of the work of two European government-sponsored projects investigating design methods for ‘provable’ computer systems. As a common interface both projects use subsets of Occam and the transputer instruction set. A number of transputer instructions are presented using Z. The article is part of a special issue on Formal aspects of microprocessor design, edited by Hussein Zedan. See also [231].CrossRefGoogle Scholar
  36. [36]
    Jonathan P. Bowen. Selected Z bibliography. Oxford University Computing Laboratory, 1990–1992. This bibliography is maintained in BIBTEX database format. It is available via e-mail, together with a LATEX [154] file for printing the bibliography, by sending a message containing the command “send z z91.bib z91.tex” to the PRG archive server on <archive-server@comlab.ox.ac.uk> [299]. Note that the source of the bibliography is about 120 Kbytes in size. If your mailer has a limit of 100 Kbytes (and many do), and you have access to the UNIX utilities uncompress and uudecode, please access the compressed uuencoded version instead using the command “send z z91.uu” Ruaridh Macdonald, RSRE, Malvern, initiated the Z bibliography and helped maintain it for a while. Joan Arnold, the industrial liaison secretary at the PRG, Oxford, is now helping to maintain it. To add entries, please send as complete information as possible to <Joan.Arnold@comlab.ox.ac.uk>.Google Scholar
  37. [37]
    Jonathan P. Bowen. X: Why Z? Computer Graphics Forum, 11, June 1992.Google Scholar
  38. [38]
    Jonathan P. Bowen, Roger B. Gimson, and Stig Topp-Jørgensen. The specification of network services. Technical Monograph PRG-61, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, August 1987.Google Scholar
  39. [39]
    Jonathan P. Bowen, Roger B. Gimson, and Stig Topp-jørgensen. Specifying system implementations in Z. Technical Monograph PRG-63, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, February 1988.Google Scholar
  40. [40]
    Peter T. Breuer. Z! in progress: Maintaining Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 295–318. Springer-Verlag, 1991.Google Scholar
  41. [41]
    David J. Brown and Jonathan P. Bowen. The Event Queue: An extensible input system for UNIX workstations. In Proc. European Unix Users Group Conference, pages 29–52. EUUG, May 1987.Google Scholar
  42. [42]
    D. Brownbridge. Using Z to develop a CASE toolset. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 142–149. Springer-Verlag, 1990.Google Scholar
  43. [43]
    T. Bryant. Structured methodologies and formal notations: Developing a framework for synthesis and investigation. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 229–241. Springer-Verlag, 1990.Google Scholar
  44. [44]
    Alan Burns and I.W. Morrison. A formal description of the structure attribute model for tool interfacing. Software Engineering Journal, 4(2): 74–78, March 1989.CrossRefGoogle Scholar
  45. [45]
    Alan Burns and A.J. Wellings. Occam’s priority model and deadline scheduling. In Proc. 7th Occam User Group Meeting, Grenoble, 1987.Google Scholar
  46. [46]
    Alan Burns and A.J. Wellings. A formal description of Ada tasking in Z. Computer Science Report YCS122, University of York, Heslington, York YO1 5DD, UK, 1989.Google Scholar
  47. [47]
    Alan Burns and A.J. Wellings. Priority inheritance and message passing communication: A formal treatment. Computer Science Report YCS116, University of York, Heslington, York YO1 5DD, UK, 1989.Google Scholar
  48. [48]
    Paul Butcher. A behavioural semantics for Linda-2. Software Engineering Journal, 6(4): 196–204, July 1991.MathSciNetCrossRefGoogle Scholar
  49. [49]
    M.J. Butler. Service extension at the specification level. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 319–336. Springer-Verlag, 1991.Google Scholar
  50. [50]
    David Carrington, David Duke, Roger Duke, Paul King, Gordon A. Rose, and Graeme Smith. Object-Z: An object-oriented extension to Z. In S. Vuong, editor, Formal Description Techniques, II (FORTE’89), pages 281–296. North-Holland, 1990.Google Scholar
  51. [51]
    David Carrington and Graeme Smith. Extending Z for object-oriented specifications. In Proc. 5th Australian Software Engineering Conference (ASWEC’90), pages 9–14, 1990.Google Scholar
  52. [52]
    Patrice Chalin and Peter Grogono. Z specification of an object manager. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z-Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 41–71. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  53. [53]
    S.J. Clarke, Andy C. Combes, and John A. McDermid. The analysis of safety arguments in the specification of a motor speed control loop. Computer Science Report YCS136, University of York, Heslington, York YO1 5DD, UK, 1990. This report describes some timing extensions to Z.Google Scholar
  54. [54]
    Bernie Cohen. Justification of formal methods for system specifications & A rejustification of formal notations. Software Engineering Journal, 4(1): 26–38, January 1989.CrossRefGoogle Scholar
  55. [55]
    B.P. Collins, John E. Nicholls, and Ib H. Sørensen. Introducing formal methods: the CICS experience with Z. In B. Neumann et al., editors, Mathematical Structures for Software Engineering. Oxford University Press, UK, 1991.Google Scholar
  56. [56]
    Andrew Coombes and John A. McDermid. A tool for defining the architecture of Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 77–92. Springer-Verlag, 1991.Google Scholar
  57. [57]
    David Cooper. Educating management in Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 192–194. Springer-Verlag, 1990.Google Scholar
  58. [58]
    Iain Craig. The Formal Specification of Advanced AI Architectures. AI Series. Ellis Horwood, September 1991. This book contains two rather large (and relatively complete) specifications of AI systems using Z. The architectures are the blackboard and Cassandra architectures. As well as showing that formal specification can be used in AI at the architecture level, the book is intended as a case-studies book, and also contains introductory material on Z (for AI people). The book assumes a knowledge of Z, so for non-AI people its primary use is for the presentation of the large specifications (The blackboard specification, with explanatory text, is around 100 pages.)Google Scholar
  59. [59]
    Iain D. Craig. The formal specification of a blackboard framework. Research Report 181, Department of Computer Science, University of Warwick, Department of Computer Science, University of Warwick, Coventry CV4 7AL, UKoventry CV4 7AL, UK, March 1991.Google Scholar
  60. [60]
    Ian D. Craig. Formal specification of AI systems: Four case studies. Research Report 182, Department of Computer Science, University of Warwick, Department of Computer Science, University of Warwick, Coventry CV4 7AL, UKoventry CV4 7AL, UK, March 1991.Google Scholar
  61. [61]
    Dan Craigen, Sentot Kromodimoeljo, Irwin Meisels, Bill Pase, and Mark Saaltink. EVES: An overview. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 389–405. Springer-Verlag, 1991.Google Scholar
  62. [62]
    S. Croxall, Peter Lupton, and John B. Wordsworth. A formal specification of the CPI communications. IBM Technical Report TR12.277, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, 1990.Google Scholar
  63. [63]
    Elspeth Cusack. Inheritance in object oriented Z. In Pierre America, editor, Proc. ECOOP’91 European Conference on Object-Oriented Programming, volume 512 of Lecture Notes in Computer Science, pages 167–179. Springer-Verlag, 1991.Google Scholar
  64. [64]
    Elspeth Cusack. Object oriented modelling in Z for open distributed systems. In J. de Meer, editor, Proc. International Workshop on ODP. North Holland, 1992.Google Scholar
  65. [65]
    Elspeth Cusack and Michael Lai. Object oriented specification in LOTOS and Z (or my cat really is object oriented!). In J.W. de Bakker, W.P. de Roever, and G. Rozenberg, editors, REX/FOOL School/Workshop on Foundations of Object-Oriented Languages, volume 489 of Lecture Notes in Computer Science, pages 179–202. Springer-Verlag, 1990.Google Scholar
  66. [66]
    Norman Delisle and David Garlan. Formally specifying electronic instruments. In Proc. Fifth International Workshop on Software Specification and Design. IEEE Computer Society, May 1989. Also published in ACM SIGSOFT Software Engineering Notes 14(3).Google Scholar
  67. [67]
    Norman Delisle and David Garlan. A formal specification of an oscilloscope. IEEE Software, pages 29–36, September 1990. Unlike most work on the application of formal methods, this research uses formal methods to gain insight into system architecture. The context for this case study is electronic instrument design.Google Scholar
  68. [68]
    A.J.J. Dick, P.J. Krause, and J. Cozens. Computer aided transformation of Z into Prolog. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 71–85. Springer-Verlag, 1990.Google Scholar
  69. [69]
    Antoni Diller. Specifying interactive programs in Z. Research Report CSRP-90-13, School of Computer Science, University of Birmingham, UK, August 1990.Google Scholar
  70. [70]
    Antoni Diller. Z: An Introduction to Formal Methods. Wiley, Chichester, UK, June 1990. This book offers a comprehensive tutorial to Z from the practical viewpoint. Many natural deduction style proofs are presented and exercises are included.MATHGoogle Scholar
  71. [71]
    Antoni Diller. Relating to Z specifications and programs through Hoare logics. Research Report CSR-91-3, School of Computer Science, University of Birmingham, UK, April 1991. Copies available from: Mary Cooper, School of Computer Science, Aston Webb Building, University of Birmingham, Edgbaston, Birmingham, B15 2TT, UK.Google Scholar
  72. [72]
    Veronika Doma and Robin Nicholl. EZ: A system for automatic prototyping of Z specifications. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 189–203. Springer-Verlag, 1991.Google Scholar
  73. [73]
    David A. Duce. A simple example from GKS in Z. Technical Report RAL-86-082, Informatics Division, Rutherford Appleton Laboratories, Chilton, Didcot, Oxon OX11 0QX, UK, 1986.Google Scholar
  74. [74]
    David Duke. Structuring Z specifications. In Proc. 14th Australian Computer Science Conference, 1991.Google Scholar
  75. [75]
    David Duke and Roger Duke. A history model for classes in Object-Z. Technical Report 120, Department of Computer Science, University of Queensland, Australia 4072, 1989.Google Scholar
  76. [76]
    David Duke and Roger Duke. Towards a semantics for Object-Z. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 244–261. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  77. [77]
    Roger Duke and David Duke. Aspects of object-oriented formal specification. In Proc. 5th Australian Software Engineering Conference (ASWEC’90), pages 21–26, 1990.Google Scholar
  78. [78]
    Roger Duke, Ian J. Hayes, Paul King, and Gordon A. Rose. Protocol specification and verification using Z. In S. Aggarwal and K. Sabnani, editors, Protocol Specification, Testing, and Verification VIII, pages 33–46. North-Holland, 1988.Google Scholar
  79. [79]
    Roger Duke, Paul King, Gordon A. Rose, and Graeme Smith. The Object-Z specification language. Technical Report 91-1, Version 1, Software Verification Research Centre, University of Queensland, Australia 4072, May 1991.Google Scholar
  80. [80]
    Roger Duke, Paul King, Gordon A. Rose, and Graeme Smith. The Object-Z specification language. In T. Korson, V. Vaishnavi, and B. Meyer, editors, Technology of Object-Oriented Languages and Systems: TOOLS 5, pages 465–483. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1991.Google Scholar
  81. [81]
    Roger Duke and Gordon A. Rose. A complete Z specification of an interactive program editor. Technical Report 71, Department of Computer Science, University of Queensland, Australia, 4072, 1986.Google Scholar
  82. [82]
    Roger Duke, Gordon A. Rose, and A. Lee. Object-oriented protocol specification. In L. Logrippo, R.L. Probert, and H. Ural, editors, Protocol Specification, Testing, and Verification X, pages 325–338. North-Holland, 1990.Google Scholar
  83. [83]
    Roger Duke and Graeme Smith. Temporal logic and Z specifications. Australian Computer Journal, 21(2): 62–69, May 1989.Google Scholar
  84. [84]
    N.E. Fenton and D. Mole. A note on the use of Z for flowgraph transformation. Journal of Information & Software Technology, 30(7): 432–437, 1988.CrossRefGoogle Scholar
  85. [85]
    E. Fergus and Darrell C. Ince. Z specifications and modal logic. In Patrick A.V. Hall, editor, Proc. Software Engineering 90, volume 1 of British Computer Society Conference Series. Cambridge University Press, July 1990.Google Scholar
  86. [86]
    C.J. Fidge. Specification and verification of real-time behaviour using Z and RTL. In School and Symposium on Formal Techniques in Real-Time and Fault-Tolerant Systems, 1992.Google Scholar
  87. [87]
    L. William Flinn and Ib H. Sørensen. CAVIAR: A case study in specification. Technical Monograph PRG-48, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, July 1985.Google Scholar
  88. [88]
    Mike Flynn, Tim Hoverd, and David Brazier. Formaliser — an interactive support tool for Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 128–141. Springer-Verlag, 1990.Google Scholar
  89. [89]
    I. Fogg, B. Hicks, Andrew Lister, T. Mansfield, and Kerry Raymond. A comparison of LOTOS and Z for specifying distributed systems. Australian Computer Science Communications, 12(1): 88–96, February 1990.Google Scholar
  90. [90]
    Paul H.B. Gardiner, Peter J. Lupton, and Jim C.P. Woodcock. A simpler semantics for Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 3–11. Springer-Verlag, 1991.Google Scholar
  91. [91]
    David Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4): 42–44, September 1990.CrossRefGoogle Scholar
  92. [92]
    David Garlan and Norman Delisle. Formal specifications as reusable frameworks. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 150–163. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  93. [93]
    David Garlan and David Notkin. Formalizing design spaces: Implicit invocation mechanisms. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 31–45. Springer-Verlag, 1991.Google Scholar
  94. [94]
    Susan L. Gerhart. Applications of formal methods: Developing virtuoso software. IEEE Software, pages 6–10, September 1990. This is an introduction to a special issue on Formal Methods with an emphasis on Z in particular. It was published in conjunction with special Formal Methods issues of IEEE Transactions on Software Engineering and IEEE Computer. See also [67, 104, 187, 245, 273].Google Scholar
  95. [95]
    Stephen Gilmore. Correctness-oriented approaches to software development. Technical Report CST-76-91 (also ECS-LFCS-91-147), University of Edinburgh, UK, 1991. A PhD thesis providing a critical evaluation of Z, VDM and algebraic specifications. It is centered around the rigorous development of a specification translator with the specifications given in Z, VDM and ASL. Several refinement techniques are used: these range from classical VDM development to an original transformational approach to implementing from a Z specification. Advantages and disadvantages of the approaches are discussed. Also, the correctness and efficiency of the completed implementation are assessed. The implementation is in an imperative programming language and is approximately 10,000 lines long. Copies available from: Dorothy McKie, Laboratory for Foundations of Computer Science, Department of Computer Science, The James Clerk Maxwell Building, The King’s Buildings, University of Edinburgh, Edinburgh EH9 3JZ, UK.Google Scholar
  96. [96]
    Roger B. Gimson. The formal documentation of a Block Storage Service. Technical Monograph PRG-62, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, August 1987.Google Scholar
  97. [97]
    Roger B. Gimson and C. Carroll Morgan. Ease of use through proper specification. In David A. Duce, editor, Distributed Computing Systems Programme. Peter Peregrinus, London, UK, 1984.Google Scholar
  98. [98]
    Roger B. Gimson and C. Carroll Morgan. The Distributed Computing Software project. Technical Monograph PRG-50, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, July 1985.Google Scholar
  99. [99]
    R. Di Giovanni and P.L. Iachini. HOOD and Z for the development of complex systems. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 262–289. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  100. [100]
    Reinhard Gotzhein. Specifying open distributed systems with Z. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 319–339. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  101. [101]
    Andy M. Gravell. Minimisation in formal specification and design. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 32–45. Springer-Verlag, 1990.Google Scholar
  102. [102]
    Andy M. Gravell. What is a good formal specification? In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 137–150. Springer-Verlag, 1991.Google Scholar
  103. [103]
    Frank Halasz and Mayer Schwartz. The Dexter hypertext reference model. In NIST Hypertext Standardization Workshop, January 1990.Google Scholar
  104. [104]
    Anthony Hall. Seven myths of formal methods. IEEE Software, pages 11–19, September 1990. Formal methods are difficult, expensive, and not widely useful, detractors say. Using a case study and other real-world examples, this article challenges such common myths.Google Scholar
  105. [105]
    Anthony Hall. Using Z as a specification calculus for object-oriented systems. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z-Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 290–318. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  106. [106]
    Patrick A.V. Hall. Towards testing with respect to formal specification. In Proc. Second IEE/BCS Conference on Software Engineering, volume 290, pages 159–163, Liverpool, UK, July 1988, July 1988. IEE/BCS.Google Scholar
  107. [107]
    Clare L. Harrold. Formal specification of a secure document control system for SMITE. Report no. 88002, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, February 1988.Google Scholar
  108. [108]
    W.T. Harwood. Proof rules for Balzac. Technical Report WTH/P7/001, Imperial Software Technology, Cambridge, UK, 1991.Google Scholar
  109. [109]
    Howard Haughton and Kevin C. Lano. Three dimensional maintenance. In Malcolm Munro and Peter Carroll, editors, Fourth Software Maintenance Workshop Notes, 18–20 September 1990. Centre for Software Maintenance, Durham, UK, 1990. This paper presents an object-oriented extension to Z with the aim to aid software maintenance.Google Scholar
  110. [110]
    Ian J. Hayes. Applying formal specification to software development in industry. IEEE Transactions on Software Engineering, 11(2): 169–178, February 1985.CrossRefGoogle Scholar
  111. [111]
    Ian J. Hayes. Specification directed module testing. IEEE Transactions on Software Engineering, 12(1): 124–133, January 1986.Google Scholar
  112. [112]
    Ian J. Hayes. Using mathematics to specify software. In Proc. First Australian Software Engineering Conference. Institution of Engineers, Australia, May 1986.Google Scholar
  113. [113]
    Ian J. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1987. This book, the first published on Z, contains material from PRG Technical Monographs 46–50, edited by Ian Hayes and written mainly by members of the PRG. The contributors are Ian J. Hayes, L. William Flinn, Roger B. Gimson, C. Carroll Morgan, Ib H. Sørensen and Bernard A. Sufrin. The book forms a varied collection of case studies using Z. See also [118] for the second edition of this book.Google Scholar
  114. [114]
    Ian J. Hayes. A generalisation of bags in Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 113–127. Springer-Verlag, 1990.Google Scholar
  115. [115]
    Ian J. Hayes. Specifying physical limitations: A case study of an oscilloscope. Technical Report 167, Department of Computer Science, University of Queensland, Australia, 4072, July 1990.Google Scholar
  116. [116]
    Ian J. Hayes. Interpretations of Z schema operators. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 12–26. Springer-Verlag, 1991.Google Scholar
  117. [117]
    Ian J. Hayes. Multi-relations in Z: A cross between multi-sets and binary relations. Acta Informatica, 29(1): 33–62, February 1992.MATHCrossRefGoogle Scholar
  118. [118]
    Ian J. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 2nd edition, 1992. This is the 2nd edition of the first ever published book on Z [113]; it contains substantial revisions to every chapter. The notation has been revised to be consistent with The Z Notation: A Reference Manual by Mike Spivey [243, 246]. The CAVIAR chapter has been extensively changed to make use of a form of modularization. Divided into four sections, the first provides examples of specifications, the second is devoted to the area of software engineering, the third covers distributed computing, analyzing the role of mathematical specification, and lastly, the fourth part covers transaction processing. The book will be of interest to the professional software engineer involved in designing and specifying large software projects.Google Scholar
  119. [119]
    Ian J. Hayes. VDM and Z: a comparative case study. Formal Aspects of Computing, 4(1), 1992.Google Scholar
  120. [120]
    He Jifeng, C.A.R. Hoare, and Jeff W. Sanders. Data refinement refined. In B. Robinet and R. Wilhelm, editors, Proc. ESOP 86, volume 213 of Lecture Notes in Computer Science, pages 187–196. Springer-Verlag, 1986.Google Scholar
  121. [121]
    Brian Hepworth. ZIP: a unification initiative for Z standards, methods and tools. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 253–259. Springer-Verlag, 1990.Google Scholar
  122. [122]
    Brian Hepworth. ZIP project overview. DTI IED Project No. 1639 Report ZIP/BAe/90/017, Software Technology Department, British Aerospace, Warton PR4 1AX, UK, December 1990.Google Scholar
  123. [123]
    Brian Hepworth and D. Simpson. The ZIP project. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 129–133. Springer-Verlag, 1991.Google Scholar
  124. [124]
    Iain S.C. Houston. The CICS application programming interface: Automatic transaction initiation. IBM Technical Report TR12.300, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, December 1990. One of a number of reports on the CICS application programming interface. See also [27, 149, 186].Google Scholar
  125. [125]
    Iain S.C. Houston and Steve King. CICS project report: Experiences and results from the use of Z in IBM. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 588–596. Springer-Verlag, 1991.Google Scholar
  126. [126]
    Iain S.C. Houston and John B. Wordsworth. A Z specification of part of the CICS file control API. IBM Technical Report TR12.272, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, 1990.Google Scholar
  127. [127]
    A.D. Hutcheon and A.J. Wellings. Specifying restrictions on imperative programming languages for use in a distributed embedded environment. Software Engineering Journal, 5(2): 93–104, March 1990.CrossRefGoogle Scholar
  128. [128]
    P.L. Iachini. Operation schema iterations. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 50–57. Springer-Verlag, 1991.Google Scholar
  129. [129]
    M. Imperato. An Introduction to Z. Chartwell-Bratt, 1991.Google Scholar
  130. [130]
    Darrell C. Ince. An Introduction to Discrete Mathematics and Formal System Specification. Oxford Applied Mathematics and Computing Science Series. Oxford University Press, UK, 1988.MATHGoogle Scholar
  131. [131]
    Darrell C. Ince. Z and system specification. In Darrell C. Ince and Derek Andrews, editors, The Software Life Cycle, chapter 12, pages 260–277. But-terworths, UK, 1990.Google Scholar
  132. [132]
    Inmos Ltd. Specification of instruction set & Specification of floating point unit instructions. In Transputer Instruction Set — tA compiler writer’s guide, pages 127–161. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1988. Appendices F and G use a Z-like notation to give a specification of the instruction set of the IMS T212 and T414 transputers, and the T800 floating-point transputer.Google Scholar
  133. [133]
    Jonathan Jacky. Formal specifications for a clinical cyclotron control system. ACM SIGSOFT Software Engineering Notes, 15(4): 45–54, September 1990.CrossRefGoogle Scholar
  134. [134]
    Jeremy Jacob. The varieties of refinements. In Joseph M. Morris and Roger C. Shaw, editors, Proc. 4th Refinement Workshop, Workshops in Computing, pages 441–455. Springer-Verlag, 1991.Google Scholar
  135. [135]
    M. Johnson and P. Sanders. From Z specifications to functional implementations. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 86–112. Springer-Verlag, 1990.Google Scholar
  136. [136]
    P. Johnson. Using Z to specify CICS. In Proc. Software Engineering anniversary meeting (SEAS), page 303. SEA, 1987.Google Scholar
  137. [137]
    Cliff B. Jones. Interference revisited. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 58–73. Springer-Verlag, 1991.Google Scholar
  138. [138]
    David Jordan, John A. McDermid, and Ian Toyn. CADiZ — computer aided design in Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 93–104. Springer-Verlag, 1991. See also [267].Google Scholar
  139. [139]
    L.E. Jordan. The kernel Z type checking rules. Technical Report LEJ/TC3/-001, Imperial Software Technology, Cambridge, UK, 1991.Google Scholar
  140. [140]
    L.E. Jordan. The Z syntax supported by Balzac-II/1. Technical Report LEJ/-S1/001, Imperial Software Technology, Cambridge, UK, 1991.Google Scholar
  141. [141]
    Mark B. Josephs. The data refinement calculator for Z specifications. Information Processing Letters, 27(1): 29–33, 1988.MathSciNetCrossRefGoogle Scholar
  142. [142]
    Mark B. Josephs. A state-based approach to communicating processes. Distributed Computing, 3: 9–18, 1988. A theoretical paper on combining features of CSP and Z.MATHCrossRefGoogle Scholar
  143. [143]
    Mark B. Josephs. Specifying reactive systems in Z. Technical Report PRG-TR-19-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, July 1991.Google Scholar
  144. [144]
    Mark B. Josephs and David Redmond-Pyle. Entity-relationship models expressed in Z: A synthesis of structured and formal methods. Technical Report PRG-TR-20-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, July 1991.Google Scholar
  145. [145]
    Mark B. Josephs and David Redmond-Pyle. A library of Z schemas for use in entity-relationship modelling. Technical Report PRG-TR-21-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, August 1991.Google Scholar
  146. [146]
    D.H. Kemp. Specification of Viperl in Z. Memorandum no. 4195, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, October 1988.Google Scholar
  147. [147]
    D.H. Kemp. Specification of Viper2 in Z. Memorandum no. 4217, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, October 1988.Google Scholar
  148. [148]
    Paul King. Printing Z and Object-Z LATEX documents. Department of Computer Science, University of Queensland, May 1990. A description of a Z style option “oz.sty”, an extended version of Mike Spivey’s “zed.sty” [244], for use with the LATEX document preparation system [154]. It is particularly useful for printing Object-Z documents [50, 76]. The style file and the guide are available electronically by sending an e-mail message containing the command “send z oz.sty oz.tex” to <archive-server@comlab.ox.ac.uk> [299].Google Scholar
  149. [149]
    Steve King. The CICS application programming interface: Program control. IBM Technical Report TR12.302, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, December 1990. One of a number of reports on the CICS application programming interface. See also [27, 124, 186].Google Scholar
  150. [150]
    Steve King. Z and the refinement calculus. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 164–188. VDM-Europe, Springer-Verlag, 1990. Also published as Technical Monograph PRG-79, Oxford University Computing Laboratory, February 1990.Google Scholar
  151. [151]
    Steve King and Ib H. Sørensen. Specification and design of a library system. In The Theory and Practice of Refinement: Approaches to the Formal Development of Large-Scale Software Systems. Butterworths, London, UK, 1989.Google Scholar
  152. [152]
    Steve King, Ib H. Sørensen, and Jim C.P. Woodcock. Z: Grammar and concrete and abstract syntaxes. Technical Monograph PRG-68, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, 1988.Google Scholar
  153. [153]
    Peter Knaggs. Formal descriptive languages (student reports), MSc Software Engineering 1990/91. Technical report, School of Computing and Mathematics, Teesside Polytechnic, Middlesbrough, Cleveland TS1 3BA, UK, 1991. This is a collection of reports, written by the students on the MSc in Software Engineering course. These reports were written after a 20 hour introduction to Z and were collected and produced by Peter Knaggs.Google Scholar
  154. [154]
    Leslie Lamport. LATEX User’s Guide & Reference Manual. Addison-Wesley Publishing Company, Reading, Massachusetts, USA, 1986. Z specifications may be produced using the document preparation system LATEX together with a special LATEX style option. The most widely used style files are fuzz.sty [240], zed.sty [244] and oz.sty [148].Google Scholar
  155. [155]
    Kevin C. Lano. Z++: An object-orientated extension to Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 151–172. Springer-Verlag, 1991.Google Scholar
  156. [156]
    Kevin C. Lano and Peter T. Breuer. From programs to Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 46–70. Springer-Verlag, 1990.Google Scholar
  157. [157]
    Kevin C. Lano and Howard Haughton. An algebraic semantics for the specification language Z++. In Proc. AMAST’ 91, Workshops in Computing. Springer-Verlag, 1991.Google Scholar
  158. [158]
    Kevin C. Lano, Howard Haughton, and Peter T. Breuer. Using object-oriented extensions of Z for maintenance and reverse-engineering. Technical Report PRG-TR-22-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, 1991.Google Scholar
  159. [159]
    David Lightfoot. Formal Specification using Z. Macmillan, 1991.Google Scholar
  160. [160]
    Ralph L. London. Specifying reusable components using Z: Sets implemented by bit vectors. Technical Report CR-88-14, Tektronix Laboratories, P.O. Box 500, MS 50-662, Beaverton, Oregon 97077, USA, November 1988.Google Scholar
  161. [161]
    Ralph L. London and Kathleen R. Milsted. Specifying reusable components using Z: Realistic sets and dictionaries. ACM SIGSOFT Software Engineering Notes, 14(3): 120–127, May 1989. Presented at the 5th International Workshop on Software Specification and Design, Pittsburgh, Pennsylvania, 19–20 May 1989. A longer version entitled Specifying and Verifying Reusable Components Using Z: Sets and Dictionaries appeared as Technical Report CR-88-10, Tektronix Laboratories, P.O. Box 500, MS 50-662, Beaverton, Oregon 97077, USA, October, 1988.CrossRefGoogle Scholar
  162. [162]
    Peter J. Lupton. Promoting forward simulation. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 27–49. Springer-Verlag, 1991.Google Scholar
  163. [163]
    Ruaridh Macdonald. Z usage and abusage. Report no. 91003, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, February 1991. Training courses for Z teach the notation and a number of commonly used techniques for manipulating it. Experience of writing Z specifications and reading those of others leads to the development of other techniques, many of which are passed around informally between Z practitioners, but which are less likely to be written down. This paper presents a miscellany of observations drawn from experience of using Z, shows a variety of techniques for expressing certain class of idea concisely and clearly, and alerts the reader to certain pitfalls which may trap the unwary. The paper assumes a familiarity with the Z notation and the modelling of operations using the state-machine style, including error-handling.Google Scholar
  164. [164]
    David May. Use of formal methods by a silicon manufacturer. In C.A.R. Hoare, editor, Developments in Concurrency and Communication, University of Texas at Austin Year of Programming Series, chapter 4, pages 107–129. Addison-Wesley Publishing Company, 1990.Google Scholar
  165. [165]
    David May and David Shepherd. Verification of the IMS T800 microprocessor. In Proc. Electronic Design Automation, pages 605–615, London, UK, September 1987.Google Scholar
  166. [166]
    John A. McDermid. Special section on Z. Software Engineering Journal, 4(1): 25–72, January 1989. A special issue on Z, introduced and edited by Prof. John McDermid. See also [34, 242, 283].CrossRefGoogle Scholar
  167. [167]
    John A. McDermid, editor. The Theory and Practice of Refinement: Approaches to the Formal Development of Large-Scale Software Systems. Butterworths, London, UK, 1989. Papers from the Refinement Workshop at the University of York, held on 7–8 January 1988, including several on Z.Google Scholar
  168. [168]
    John A. McDermid. Formal methods: Use and relevance for the development of safety critical systems. In P.A. Bennett, editor, Safety Aspects of Computer Control. Butterworth-Heinemann, Oxford, UK, 1991. This paper discusses a number of formal methods and summarizes strengths arid weaknesses in safety critical applications; a major safety-related example is presented in Z.Google Scholar
  169. [169]
    John A. McDermid and Peter Whysall. Formal System Specification and Implementation using Z. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1992. A comprehensive introduction to the use of Z specifications. The emphasis on the application of Z enables the reader to appreciate how to use it in specifying and developing software systems. Written in a tutorial style, the book: • discussed an approach to large-scale modular specifications using object-oriented techniques; • includes the development of code from specifications; • provides a practical engineering treatment of formal specifications; • deals with the problems of scale and modular specifications; • embodies up-to-date research results.Google Scholar
  170. [170]
    Mike A. McMorran and John E. Nicholls. Z user manual. Technical Report TR12.274, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, July 1989. Version 1.0.Google Scholar
  171. [171]
    Silvio L. Meira and A.L.C. Cavalcanti. Modular object-oriented Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 173–192. Springer-Verlag, 1991.Google Scholar
  172. [172]
    B. Meyer. On formalism in specifications. IEEE Software, 2(1): 6–26, January 1985.CrossRefGoogle Scholar
  173. [173]
    Jonathan D. Moffett and Morris S. Sloman. A case study representing a model: to Z or not to Z? In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 254–268. Springer-Verlag, 1991.Google Scholar
  174. [174]
    Brian Q. Monahan. Book review. Formal Aspects of Computing, 1(1): 137–142, January–March 1989. A review of Understanding Z: A Specification Language and Its Formal Semantics by Mike Spivey [241].CrossRefGoogle Scholar
  175. [175]
    Brian Q. Monahan and Roger C. Shaw. Model-based specifications. In John A. McDermid, editor, Software Engineer’s Reference Book, chapter 21. Butterworth-Heinemann, Oxford, UK, 1991. Contains a case study in Z, followed by a discussion of the respective trade-offs in specification between Z and VDM.Google Scholar
  176. [176]
    C. Carroll Morgan. Data refinement using miracles. Information Processing Letters, 26(5): 243–246, January 1988. Also reprinted in [182].MathSciNetCrossRefGoogle Scholar
  177. [177]
    C. Carroll Morgan. Procedures, parameters, and abstraction: Separate concerns. Science of Computer Programming, 11(1), October 1988. Also reprinted in [182].Google Scholar
  178. [178]
    C. Carroll Morgan. The specification statement. ACM Transactions on Programming Languages and Systems (TOPLAS), 10(3), July 1988. Also reprinted in [182].Google Scholar
  179. [179]
    C. Carroll Morgan. Types and invariants in the refinement calculus. In Proc. Mathematics of Program Construction Conference, June 1989.Google Scholar
  180. [180]
    C. Carroll Morgan. Programming from Specifications. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1990.MATHGoogle Scholar
  181. [181]
    C. Carroll Morgan and Ken A. Robinson. Specification statements and refinement. IBM Journal of Research and Development, 31(5), September 1987. Also reprinted in [182].Google Scholar
  182. [182]
    C. Carroll Morgan, Ken A. Robinson, and Paul H.B. Gardiner. On the refinement calculus. Technical Monograph PRG-70, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, October 1988. A collection of papers including [176, 178, 177, 181].Google Scholar
  183. [183]
    C. Carroll Morgan and Jeff W. Sanders. Laws of the logical calculi. Technical Monograph PRG-78, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, September 1989. This document records some important laws of classical predicate logic. It is designed as a reservoir to be tapped by users of logic, in system development.Google Scholar
  184. [184]
    C. Carroll Morgan and Bernard A. Sufrin. Specification of the Unix filing system. IEEE Transactions on Software Engineering, 10(2): 128–142, March 1984.CrossRefGoogle Scholar
  185. [185]
    C. Carroll Morgan and Jim C.P. Woodcock. What is a specification? In Dan Craigen and Karen Summerskill, editors, Formal Methods for Trustworthy Computer Systems (FM89), Workshops in Computing, pages 38–43. Springer-Verlag, 1990.Google Scholar
  186. [186]
    P. Mundy and John B. Wordsworth. The CICS application programming interface: Transient data and storage control. IBM Technical Report TR12.299, IBM United Kingdom Laboratories Ltd., Hursley Park, Winchester, Hampshire SO21 2JN, UK, October 1990. One of a number of reports on the CICS application programming interface. See also [27, 124, 149].Google Scholar
  187. [187]
    K.T. Narayana and Sanjeev Dharap. Formal specification of a look manager. IEEE Transactions on Software Engineering, 16(9): 1089–1103, September 1990.CrossRefGoogle Scholar
  188. [188]
    K.T. Narayana and Sanjeev Dharap. Invariant properties in a dialog system. ACM SIGSOFT Software Engineering Notes, 15(4): 67–79, September 1990.CrossRefGoogle Scholar
  189. [189]
    T.C. Nash. Using Z to describe large systems. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 150–178. Springer-Verlag, 1990.Google Scholar
  190. [190]
    David Neilson. Hierarchical refinement of a Z specification. In Proc. Foundations of Software Technology and Theoretical Computer Science, December 1987.Google Scholar
  191. [191]
    David Neilson. Hierarchical refinement of a Z specification. In John A. Mc-Dermid, editor, Theory and Practice of Refinement. Butterworth Scientific, 1989.Google Scholar
  192. [192]
    David Neilson. Machine support for Z: the zedB tool. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 105–128. Springer-Verlag, 1991.Google Scholar
  193. [193]
    John E. Nicholls. Working with formal methods. Journal of Information Technology, 2(2): 67–71, June 1987.MathSciNetCrossRefGoogle Scholar
  194. [194]
    John E. Nicholls, editor. Z User Workshop, Oxford 1989, Workshops in Computing. Springer-Verlag, 1990. Proceedings of the Fourth Annual Z User Meeting, Wolfson College & Rewley House, Oxford, UK, 14–15 December 1989. Published in collaboration with the British Computer Society. For the opening address see [202]. For individual papers, see [21, 42, 43, 57, 68, 88, 101, 114, 121, 135, 156, 189, 205, 234, 248, 270].Google Scholar
  195. [195]
    John E. Nicholls. A survey of Z courses in the UK. Technical Report PRG-TR-4-91, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, March 1991.Google Scholar
  196. [196]
    John E. Nicholls, editor. Z User Workshop, Oxford 1990, Workshops in Computing. Springer-Verlag, 1991. Proceedings of the Fifth Annual Z User Meeting, Lady Margaret Hall, Oxford, UK, 17–18 December 1990. Published in collaboration with the British Computer Society. For individual papers, see [17, 40, 49, 56, 90, 102, 116, 123, 128, 137, 138, 155, 171, 173, 192, 200, 212, 225, 271, 294]. The proceedings also includes an Introduction and Opening Remarks, A Survey of Z Courses in the UK, a Selected Z Bibliography, a selection of posters and information on Z tools.Google Scholar
  197. [197]
    John E. Nicholls et al. Z in the development process. Technical Report PRG-TR-1-89, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, June 1989. Proceedings of a discussion workshop held on 15 December 1988 in Oxford, UK, with contributions by Peter Collins, David Cooper, Anthony Hall, Patrick Hall, Brian Hepworth, Ben Potter and Andrew Ricketts.Google Scholar
  198. [198]
    C.J. Nix and B.P. Collins. The use of software engineering, including the Z notation, in the development of CICS. Quality Assurance, 14(3): 103–110, September 1988.Google Scholar
  199. [199]
    Allan Norcliffe and Gill Slater. Mathematics for Software Construction. Series in Mathematics and its Applications. Ellis Horwood, 1991.Google Scholar
  200. [200]
    Allan Norcliffe and Sam Valentine. A video-based training course in reading Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 319–336. Springer-Verlag, 1991.Google Scholar
  201. [201]
    M. Norris. Z — a rigorous system specification technique. STARTS debrief report, The National Computing Centre Ltd., Oxford Road, Manchester M1 7ED, UK, 1986. Other reports in the series include: SLIM, PRICE S, ARTEMIS, VDM, SOFCHIP, JSD, SDL, SAFRA and CORE.Google Scholar
  202. [202]
    Brian Oakley. The state of use of formal methods. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 1–5. Springer-Verlag, 1990. A record of the opening address at the meeting.Google Scholar
  203. [203]
    C. O’Halloran. The software repeater (an exercise in Z specification). Report no. 4090, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, 1987.Google Scholar
  204. [204]
    Colin E. Parker. Z tools catalogue. Technical Report ZIP/BAe/90/020, British Aerospace, Warton,UK, May 1991.Google Scholar
  205. [205]
    M. Phillips. CICS/ESA 3.1 experiences. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 179–185. Springer-Verlag, 1990.Google Scholar
  206. [206]
    Michael Pilling, Alan Burns, and Kerry Raymond. Formal specifications and proofs of inheritance protocols for real-time scheduling. Software Engineering Journal, 5(5): 263–279, September 1990.CrossRefGoogle Scholar
  207. [207]
    P.R.H. Place et al. Formal development of Ada programs using Z and Anna: a case study. CMU Technical Report CMU/SEI-91-TR-1, Carnegie-Mellon University, Software Engineering Institute, Pittsburgh, Pennsylvania, USA, February 1991.Google Scholar
  208. [208]
    Ben F. Potter, Jane E. Sinclair, and David Till. An Introduction to Formal Specification and Z. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1990.Google Scholar
  209. [209]
    S. Prehn and W.J. Toetenel, editors. VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science. Springer-Verlag, 1991. Volume 1: Conference Contributions. Papers with relevance to Z include [12, 23, 61, 72, 93, 125, 269, 274, 297].Google Scholar
  210. [210]
    S. Prehn and W.J. Toetenel, editors. VDM’91: Formal Software Development Methods, volume 552 of Lecture Notes in Computer Science. Springer-Verlag, 1991. Volume 2: Tutorials. Papers with relevance to Z include [5, 286].Google Scholar
  211. [211]
    Gill P. Randell. Translating data flow diagrams into Z (and vice versa). Report no. 90019, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, 1990.Google Scholar
  212. [212]
    Gill P. Randell. Data flow diagrams and Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 216–227. Springer-Verlag, 1991.Google Scholar
  213. [213]
    Kerry Raymond, Phil Stocks, and David Carrington. Using Z to specify distributed systems. Technical Report 181, Key Centre for Software Technology, University of Queensland, Australia 4072, 1990.Google Scholar
  214. [214]
    Joy N. Reed. Semantics-based tools for a specification support environment. In Mathematical Foundations of Programming Language Semantics, volume 298 of Lecture Notes in Computer Science. Springer-Verlag, 1988.Google Scholar
  215. [215]
    Joy N. Reed and Jane E. Sinclair. An algorithm for type-checking Z: A Z specification. Technical Monograph PRG-81, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, March 1990.Google Scholar
  216. [216]
    Ken A. Robinson. Refining Z specifications to programs. In Proc. Australian Software Engineering Conference, pages 87–97, 1987.Google Scholar
  217. [217]
    Gordon A. Rose and Peter Robinson. A case study in formal specifications. In Proc. First Australian Software Engineering Conference, May 1986.Google Scholar
  218. [218]
    P. Rudkin. Modelling information objects in Z. In J. de Meer, editor, Proc. International Workshop on ODP. North Holland, 1992.Google Scholar
  219. [219]
    Mark Saaltink. Z and EVES. Technical Report TR-91-5449-02, Odyssey Research Associates, 265 Carling Avenue, Suite 506, Ottawa, Ontario K1S 2E1, Canada, October 1991. An account of the mechanisation of the Z toolkit using the EVES proof system [61].Google Scholar
  220. [220]
    Augusto C.A. Sampaio and Silvio L. Meira. Modular extensions to Z. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 211–232. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  221. [221]
    S.A. Schuman and D.H. Pitt. Object-oriented subsystem specification. In L.G.L.T. Meertens, editor, Program Specification and Transformation, pages 313–341. North Holland, 1987.Google Scholar
  222. [222]
    S.A. Schuman, D.H. Pitt, and P.J. Byers. Object-oriented process specification. In Specification and Verification of Concurrent Systems, Workshops in Computing, pages 21–70. Springer-Verlag, 1990.Google Scholar
  223. [223]
    Lesley T. Semmens and Pat M. Allen. Using entity relationship models as a basis for Z specifications. Technical Report IES1/90, Leeds Polytechnic, Faculty of Information and Engineering Systems, Leeds, UK, 1990.Google Scholar
  224. [224]
    Lesley T. Semmens and Pat M. Allen. Using Yourdon and Z to specify computer security: A case study. Technical Report IES4/90, Leeds Polytechnic, Faculty of Information and Engineering Systems, Leeds, UK, 1990.Google Scholar
  225. [225]
    Lesley T. Semmens and Pat M. Allen. Using Yourdon and Z: An approach to formal specification. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 228–253. Springer-Verlag, 1991.Google Scholar
  226. [226]
    Chris T. Sennett. A combined security and integrity policy model appendix to development environment for secure software. Report no. 87015, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, November 1987.Google Scholar
  227. [227]
    Chris T. Sennett. Review of type checking and scope rules of the specification language Z. Report no. 87017, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, November 1987.Google Scholar
  228. [228]
    Chris T. Sennett. Formal specification and implementation. In Chris T. Sennett, editor, High-Integrity Software. Pitman, 1989.Google Scholar
  229. [229]
    Chris T. Sennett. Demonstrating the compliance of Ada programs with Z specifications. In BCS/FACS Refinement Workshop, January 1992.Google Scholar
  230. [230]
    Chris T. Sennett and Ruaridh Macdonald. Separability and security models. Report no. 87020, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, November 1987.Google Scholar
  231. [231]
    David E. Shepherd. Verified microcode design. Microprocessors and Microsystems, 14(10): 623–630, December 1990. This article shows how a high-level program in Occam was transformed to a low level implementation that matched the micromachine functions of the T800 transputer in order to verify its microcode. The high-level specification is first given in Z. The article is part of a special issue on Formal aspects of microprocessor design, edited by Hussein Zedan. See also [35].CrossRefGoogle Scholar
  232. [232]
    David E. Shepherd and Greg Wilson. Making chips that work. New Scientist, 1664: 61–64, May 1989. A general article containing information on the formal development of the T800 floating-point unit for the transputer including the use of Z.Google Scholar
  233. [233]
    Lewis N. Simcox. The application of Z to the specification of air traffic control systems: 1. Memorandum no. 4280, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, April 1989.Google Scholar
  234. [234]
    Alf Smith. The Knuth-Bendix completion algorithm and its specification in Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 195–220. Springer-Verlag, 1990.Google Scholar
  235. [235]
    Alf Smith. On recursive free types in Z. Memorandum no. 91028, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, 1991.Google Scholar
  236. [236]
    Graeme Smith and Roger Duke. Specification and verification of a cache coherence protocol. Technical Report 126, Department of Computer Science, University of Queensland, Australia 4072, 1989.Google Scholar
  237. [237]
    Graeme Smith and Roger Duke. Modelling a cache coherence protocol using Object-Z. In Proc. 13th Australian Computer Science Conference (ACSC-13), pages 352–361, 1990.Google Scholar
  238. [238]
    Ian Sommerville. Software Engineering, chapter 9, pages 157–173. Addison-Wesley, 1989. A chapter entitled Model-Based Specification including examples using Z.Google Scholar
  239. [239]
    Ib H. Sørensen. A specification language. In J. Staunstrup, editor, Program Specification: Proceedings of a Workshop, volume 134 of Lecture Notes in Computer Science, pages 381–401. Springer-Verlag, 1981.Google Scholar
  240. [240]
    J. Michael Spivey. The fuzz Manual. Computing Science Consultancy, 2 Willow Close, Garsington, Oxford 0X9 9AN, UK, 1988. A Z type-checker and “fuzz.sty” style option for LATEX documents [154]. The package is compatible with the book, The Z Notation: A Reference Manual by the same author [243]. A new version compatible with the 2nd edition of this book [246] will be available soon. Send orders to Mrs. A. Spivey, 34 Westlands Grove, Stockton Lane, York YO3 0EF, UK. Technical enquiries can be sent to Mike Spivey at 2 Willow Close, Garsington, Oxford OX9 9AN, UK, or by e-mail at <Mike.Spivey@comlab.ox.ac.uk>. Cost: SUN 3 on cartridge tape, SUN 4 version on 3.5in disk, or VAX/VMS version on TK-50 tape, £300, and IBM PC version on 5.25in or 3.5in disk, £200. Cheques should be made payable to Dr. J.M. Spivey. An order form is available via electronic mail by sending a message containing the command “send z fuzz” to the PRG archive server [299] on <archive-server@comlab.ox.ac.uk>.Google Scholar
  241. [241]
    J. Michael Spivey. Understanding Z: A Specification Language and its Formal Semantics, volume 3 of Cambridge Tracts in Theoretical Computer Science. Cambridge University Press, UK, January 1988. Published version of 1985 DPhil thesis.Google Scholar
  242. [242]
    J. Michael Spivey. An introduction to Z and formal specifications. Software Engineering Journal, 4(1), January 1989.Google Scholar
  243. [243]
    J. Michael Spivey. The Z Notation: A Reference Manual. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1989. This book is the first widely available reference manual for the Z notation. See also [296] for the draft proposed standard and [246] for the 2nd edition of this book.Google Scholar
  244. [244]
    J. Michael Spivey. A guide to the zed style option. Oxford University Computing Laboratory, December 1990. A description of the Z style option “zed.sty” for use with the LATEX document preparation system [154]. The style file and the guide are available electronically by sending an e-mail message containing the command “send z zed.sty zguide.tex” to <archive-server@comlab.ox.ac.uk>.Google Scholar
  245. [245]
    J. Michael Spivey. Specifying a real-time kernel. IEEE Software, pages 21–28, September 1990. This case study of an embedded real-time kernel shows that mathematical techniques have an important role to play in documenting systems and avoiding design flaws.Google Scholar
  246. [246]
    J. Michael Spivey. The Z Notation: A Reference Manual. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 2nd edition, 1992. This is the 2nd edition of the first widely available reference manual on Z [243]. The Reference Manual provides a complete and definitive guide to the use of Z in specifying information systems, writing specifications and designing implementations.Google Scholar
  247. [247]
    J. Michael Spivey and Bernard A. Sufrin. Type inference in Z. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 426–438. VDM-Europe, Springer-Verlag, 1990. See also [248].Google Scholar
  248. [248]
    J. Michael Spivey and Bernard A. Sufrin. Type inference in Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 6–31. Springer-Verlag, 1990.Google Scholar
  249. [249]
    Susan Stepney. Comparative study of object orientation in Z. Technical Report ZIP/Logica/90/046, Issue 3.0, Logica Cambridge Ltd, Betjeman House, 104 Hills Road, Cambridge CB2 1LQ, UK, November 1990.Google Scholar
  250. [250]
    Susan Stepney, Rosalind Barden, and David Cooper. A survey of object orieb-tation in Z. Software Engineering Journal, 7, March 1992.Google Scholar
  251. [251]
    Susan Stepney and Stephen P. Lord. Formal specification of an access control system. Software-Practice and Experience, 17(9): 575–593, September 1987.CrossRefGoogle Scholar
  252. [252]
    Phil Stocks, Kerry Raymond, and David Carrington. Representing distributed system concepts in Z. Technical Report 180, Key Centre for Software Technology, University of Queensland, Australia 4072, 1990.Google Scholar
  253. [253]
    Phil Stocks, Kerry Raymond, David Carrington, and Andrew Lister. Modelling open distributed systems in Z. Computer Communications, 15(2): 103–113, March 1992. In a special issue on the practical use of FDTs (Formal Description Techniques) in communications and distributed systems, edited by Dr. Gordon S. Blair.CrossRefGoogle Scholar
  254. [254]
    Bernard A. Sufrin. Formal system specification: Notation and examples. In D. Neel, editor, Tools and Notations for Program Construction. Cambridge University Press, UK, 1982. An example of a filing system specification. First published use of the schema notation to put together states.Google Scholar
  255. [255]
    Bernard A. Sufrin. Towards formal specification of the ICL data dictionary. ICL Technical Journal, August 1984.Google Scholar
  256. [256]
    Bernard A. Sufrin. Formal methods and the design of effective user interfaces. In Michael D. Harrison and A.F. Monk, editors, People and Computers: Designing for Usability. Cambridge University Press, UK, 1986.Google Scholar
  257. [257]
    Bernard A. Sufrin. Formal specification of a display-oriented editor. In Narain Gehani and Andrew D. McGettrick, editors, Software Specification Techniques, International computer science series, pages 223–267. Addison-Wesley Publishing Company, 1986.Google Scholar
  258. [258]
    Bernard A. Sufrin. A formal framework for classifying interactive information systems. In IEE Colloquium on Formal Methods and Human-Computer Interaction, number 09 in IEE Digest, pages 4/1-14. IEE, 1987.Google Scholar
  259. [259]
    Bernard A. Sufrin. Effective industrial application of formal methods. In Proc. 11th IFIP Computer Congress. North-Holland, 1989.Google Scholar
  260. [260]
    Bernard A. Sufrin and He Jifeng. Specification, analysis and refinement of interactive processes. In Michael Harrison and Harold Thimbleby, editors, Formal Methods in Human-Computer Interaction, volume 2 of Cambridge Series on Human-Computer Interaction, chapter 6, pages 153–200. Cambridge University Press, UK, 1990. A case study on using Z for process modelling.Google Scholar
  261. [261]
    Bernard A. Sufrin and Jim C.P. Woodcock. Towards the formal specification of a simple programming support environment. Software Engineering Journal, 2(4): 86–94, July 1987.CrossRefGoogle Scholar
  262. [262]
    Paul A. Swatman, P.M.C. Swatman, and Roger Duke. Electronic data interchange: A high-level formal specification in Object-Z. In Proc. 6th Australian Software Engineering Conference (ASWEC’91), 1991.Google Scholar
  263. [263]
    Phil F. Terry and Simon R. Wiseman. On the design and implementation of a secure computer system. Memorandum no. 4188, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, June 1988.Google Scholar
  264. [264]
    Simon Thompson.Specification techniques [9004-0316]. A CM Computing Reviews, 31(4): 213, April 1990. A review of Formal methods applied to a floating-point number system by Geoff Barrett [19].Google Scholar
  265. [265]
    David Till and Ben F. Potter. The specification in Z of gateway functions within a communications network. In Proc. IFIP WG10.3 Conference on Distributed Processing, Amsterdam, The Netherlands, October 1987. Elsevier Science Publishers B.V. (North-Holland).Google Scholar
  266. [266]
    Brian S. Todd. A model-based diagnostic program. Software Engineering Journal, 2(3): 54–63, May 1987.MathSciNetCrossRefGoogle Scholar
  267. [267]
    Ian Toyn. CADiZ Quick Reference Guide. York Software Engineering Ltd., University of York, York YO1 5DD, UK, 1990. A guide to the CADiZ (Computer Aided Design in Z) toolkit. This makes use of the UNIX troff family of text formatting tools. Contact David Jordan at the address above or on <yse@minster.york.ac.uk> via e-mail for further information on CADiZ. See also [138] for a paper introducing CADiZ. Support for LATEX [154] is planned.Google Scholar
  268. [268]
    M.J. van Diepen and K.M. van Hee. A formal semantics for Z and the link between Z and the relational algebra. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 526–551. VDM-Europe, Springer-Verlag, 1990.Google Scholar
  269. [269]
    K.M. van Hee, L.J. Somers, and M. Voorhoeve. Z and high level Petri nets. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 204–219. Springer-Verlag, 1991.Google Scholar
  270. [270]
    Robin W. Whitty. Structural metrics for Z specifications. In John E. Nicholls, editor, Z User Workshop, Oxford 1989, Workshops in Computing, pages 186–191. Springer-Verlag, 1990.Google Scholar
  271. [271]
    Peter J. Whysall and John A. McDermid. An approach to object-oriented specification using Z. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 193–215. Springer-Verlag, 1991.Google Scholar
  272. [272]
    Peter J. Whysall and John A. McDermid. Object-oriented specification and refinement. In Joseph M. Morris and Roger C. Shaw, editors, Proc. 4th Refinement Workshop, Workshops in Computing, pages 151–184. Springer-Verlag, 1991.Google Scholar
  273. [273]
    Jeannette M. Wing. A specifier’s introduction to formal methods. IEEE Computer, 23(9): 8–24, September 1990.CrossRefGoogle Scholar
  274. [274]
    Jeannette M. Wing and Amy M. Zaremski. Unintrusive ways to integrate formal specifications in practice. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 545–570. Springer-Verlag, 1991.Google Scholar
  275. [275]
    Simon R. Wiseman and Clare L. Harrold. A security model and its implementation. Memorandum no. 4222, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, September 1988.Google Scholar
  276. [276]
    Andrew W. Wood. A Z specification of the MaCHO interface editor. Memorandum no. 4247, RSRE, Ministry of Defence, Malvern, Worcestershire, UK, November 1988.Google Scholar
  277. [277]
    Kenneth R. Wood. The elusive software refinery: a case study in program development. In Joseph M. Morris and Roger C. Shaw, editors, Proc. 4th Refinement Workshop, Workshops in Computing, pages 281–325. Springer-Verlag, 1991.Google Scholar
  278. [278]
    William G. Wood. Application of formal methods to system and software specification. ACM SIGSOFT Software Engineering Notes, 15(4): 144–146, September 1990.CrossRefGoogle Scholar
  279. [279]
    Jim C.P. Woodcock. Teaching how to use mathematics for large-scale software development. Bull. BCS-FACS, July 1988.Google Scholar
  280. [280]
    Jim C.P. Woodcock. Calculating properties of Z specifications. ACM SIGSOFT Software Engineering Notes, 14(4): 43–54, 1989.CrossRefGoogle Scholar
  281. [281]
    Jim C.P. Woodcock. Mathematics as a management tool: Proof rules for promotion. In Proc. 6th Annual CSR Conference on Large Software Systems, September 1989.Google Scholar
  282. [282]
    Jim C.P. Woodcock. Parallel refinement in Z. In Proc. Workshop on Refinement. Butterworths, 1989.Google Scholar
  283. [283]
    Jim C.P. Woodcock. Structuring specifications in Z. Software Engineering Journal, 4(1): 51–66, January 1989.MathSciNetCrossRefGoogle Scholar
  284. [284]
    Jim C.P. Woodcock. Transaction refinement in Z. In Proc. Workshop on Refinement Butterworths, 1989.Google Scholar
  285. [285]
    Jim C.P. Woodcock. Z. In Dan Craigen and Karen Summerskill, editors, Formal Methods for Trustworthy Computer Systems (FM89), Workshops in Computing, pages 57–62. Springer-Verlag, 1990.Google Scholar
  286. [286]
    Jim C.P. Woodcock. A tutorial on the refinement calculus. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 552 of Lecture Notes in Computer Science, pages 79–140. Springer-Verlag, 1991.Google Scholar
  287. [287]
    Jim C.P. Woodcock. Using Standard Z. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1992-93. To appear. This book covers requirements, specifications and proofs using standard Z. It contains a sound proof system for the entire Z language, and describes in detail the process of finding programs from specifications. The text is supported by many examples and case studies, and has been extensively class tested.Google Scholar
  288. [288]
    Jim C.P. Woodcock and Martin Loomes. Software Engineering Mathematics: Formal Methods Demystified. Pitman Publishing Ltd., London, UK, 1988.CrossRefGoogle Scholar
  289. [289]
    Jim C.P. Woodcock and C. Carroll Morgan. Refinement of state-based concurrent systems. In Dines Bjørner, C.A.R. Hoare, and Hans Langmaack, editors, VDM and Z — Formal Methods in Software Development, volume 428 of Lecture Notes in Computer Science, pages 340–351. VDM-Europe, Springer-Verlag, 1990. Work on combining Z and CSP.Google Scholar
  290. [290]
    John B. Wordsworth. Teaching formal specification methods in an industrial environment. In Proc. Software Engineering’ 86, London, UK, 1986. IEE/BCS, Peter Peregrinus.Google Scholar
  291. [291]
    John B. Wordsworth. Specifying and refining programs with Z. In Proc. Second IEE/BCS Conference on Software Engineering, volume 290, pages 8–16. IEE/BCS, July 1988. A tutorial summary.Google Scholar
  292. [292]
    John B. Wordsworth. Refinement tutorial: A storage manager. In Proc. Workshop on Refinement. Butterworths, January 1989.Google Scholar
  293. [293]
    John B. Wordsworth. A Z development method. In Proc. Workshop on Refinement. Butterworths, January 1989.Google Scholar
  294. [294]
    John B. Wordsworth. The CICS application programming interface definition. In John E. Nicholls, editor, Z User Workshop, Oxford 1990, Workshops in Computing, pages 285–294. Springer-Verlag, 1991.Google Scholar
  295. [295]
    William D. Young. Comparing specifications paradigms: Gypsy and Z. Technical Report 45, Computational Logic Inc., 1717 W. 6th St., Suite 290, Austin, Texas 78703, USA, 1989. Presented at the 12th National Computer Security Conference, Baltimore, Maryland, USA, 10–13 October 1989.Google Scholar
  296. [296]
    Z standards change group. Z base standard. ZIP Project Technical Report ZIP/PRG/91/074, Version 0.4, Oxford University Computing Laboratory, 11 Keble Road, Oxford, UK, December 1991. The draft version of the proposed BSI Z Standard. See also [243, 246] for the current most widely available Z reference manual.Google Scholar
  297. [297]
    Pamela Zave and Michael Jackson. Techniques for partial specification and specification of switching systems. In S. Prehn and W.J. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of Lecture Notes in Computer Science, pages 511–525. Springer-Verlag, 1991.Google Scholar
  298. [298]
    Z FORUM. Oxford University Computing Laboratory, 1986–1992. Electronic mailing list: vol. 1.1–9 (1986), vol. 2.1-4 (1987), vol. 3.1-7 (1988), vol. 4.1-4 (1989), vol. 5.1-3 (1990). Z FORUM is an electronic mailing list. It was initiated as an edited newsletter by Ruaridh Macdonald of RSRE, Malvern, Worcestershire, UK, and is now maintained by Jonathan Bowen at the PRG. Contributions should be sent to <zforum@comlab.ox.ac.uk>. Requests to join or leave the list should be sent to <zforum-request@comlab.ox.ac.uk>. Messages are now forwarded to the list directly to ensure timeliness. The list is also gatewayed to the USENET newsgroup comp.specification.z and messages posted on either will automatically appear on both. A message answering some frequently asked questions is maintained and sent to the list once a month. A list of back issues of newsletters and other Z-related material is available via e-mail by sending a message of “index z” to the PRG archive server [299] on <archive-server@comlab.ox.ac.uk>. For a particular issue, send a message such as “send z 5.3”; for the latest messages, send the command “send z zforum92”.Google Scholar
  299. [299]
    PRG archive server. Oxford University Computing Laboratory, 1992.Google Scholar

Copyright information

© British Computer Society 1992

Authors and Affiliations

  • Jonathan Bowen
    • 1
  1. 1.Oxford University Computing Laboratory Programming Research GroupOxfordUK

Personalised recommendations