Specification case studies
The Z notation: a reference manual
The Z notation: a reference manual
Using Z: specification, refinement, and proof
Using Z: specification, refinement, and proof
The way of Z: practical programming with formal methods
The way of Z: practical programming with formal methods
Applications of Formal Methods
Applications of Formal Methods
The CICS Application Programming Interface Definition
Proceedings of the Fifth Annual Z User Meeting on Z User Workshop
ZUM '97 Proceedings of the 10th International Conference of Z Users on The Z Formal Specification Notation
CICS Project Report: Experiences and Results from the use of Z in IBM
VDM '91 Proceedings of the 4th International Symposium of VDM Europe on Formal Software Development-Volume I: Conference Contributions - Volume I
Verified Software: A Grand Challenge
Computer
The verified software repository: a step towards the verifying compiler
Formal Aspects of Computing
Verifying the CICS File Control API with Z/Eves: An Experiment in the Verified Software Repository
ICECCS '07 Proceedings of the 12th IEEE International Conference on Engineering Complex Computer Systems
Z/Eves and the mondex electronic purse
ICTAC'06 Proceedings of the Third international conference on Theoretical Aspects of Computing
| Hi-index | 0.00 |
Parts of the CICS transaction processing system were modelled formally in the 1980s in a collaborative project between IBM UK Hursley Park and Oxford University Computing Laboratory. Z was used to capture a precise description of the behaviour of various modules as a means of communicating requirements and design intentions. These descriptions were not mechanically verified in any way: proof tools for Z were not considered mature, and no business case was made for effort in this area. We report a recent experiment in using the Z/Eves theorem prover to construct a machine-checked analysis of one of the CICS modules: the File Control API. This work was carried out as part of the international Grand Challenge in Verified Software, and our results are recorded in the Verified Software Repository. We give a brief description of the other modules, and propose them as challenge problems for the verification community.