<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors></contributors><titles><title><style face="normal" font="default" size="100%">Formal Verification of Nuclear Systems: Past, Present, and Future</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Security: An International Journal</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2012</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">18</style></number><volume><style face="normal" font="default" size="100%">28</style></volume><pages><style face="normal" font="default" size="100%">223-235</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we review the Systematic Design Verification Process used on the computer controlled shutdown systems of the Darlington Nuclear Generating Station Shutdown Systems. The Software Requirements Specification (SRS) made extensive use of tabular expressions to document the requirements as did the Software Design Description (SDD). Systematic Design Verification was then performed based upon the 4-Variable Model to verify that the design was correct with respect to its requirements. Custom tools were developed to process the SRS and SDD documents to produce “block theorems” for the PVS theorem prover that were used to verify the majority of the functional requirements. We discuss how the formal methods were integrated into the forward going software development process and techniques that were used to manage the complexity of the verification task. We offer some lessons learned in the process and discuss the future of formal verification for nuclear systems.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alan Wassyng</style></author><author><style face="normal" font="default" size="100%">Mark Lawford</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Lessons Learned from a Successful Implementation of Formal Methods in an Industrial Project</style></title><secondary-title><style face="normal" font="default" size="100%"> FME 2003: International Symposium of Formal Methods Europe Proceedings</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2003</style></year></dates><pub-location><style face="normal" font="default" size="100%">Pisa, Italy</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mark Lawford</style></author><author><style face="normal" font="default" size="100%">Jeff McDougall</style></author><author><style face="normal" font="default" size="100%">Peter Froebel</style></author><author><style face="normal" font="default" size="100%">Greg Moum</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Practical Application of Functional and Relational Methods for the Specification and Verification of Safety Critical Software</style></title><secondary-title><style face="normal" font="default" size="100%"> Algebraic Methodology and Software Technology</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2000</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record></records></xml>