G. J. K. Asmis’s scientific contributions

What is this page?


This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.

Publications (3)


Assessment of safety-critical software in nuclear power plants
  • Article
  • Full-text available

April 1991

·

5,298 Reads

·

201 Citations

·

·

G. J. K. Asmis

This article outlines an approach in the design, documentation, and evaluation of computer systems. This allows the use of software in many safety-critical applications because it enables the systematic comparison of the program behavior with the engineering specifications of the computer system. Many of the ideas in this article have been used by the Atomic Energy Control Board of Canada in its safety assessment of the software for the shutdown systems of the Darlington Station. The four main elements of this approach follow: (1) Formal Documentation of Software Requirements: Most of the details of a complex environment can be ignored by system implementers and reviewers if they are given a complete and precise statement of the behavioral requirements for the computer system. We describe five mathematical relations that specify the requirements for the software in a computerized control system. (2) Design and Documentation of the Module Structure: Complexity caused by interactions between separately written components can be reduced by applying Data Abstraction, Abstract Data Types, and Object-Oriented Programming if the interfaces are precisely and completely documented. (3) Program Function Documentation: Software executions are lengthy sequences of state changes described by algorithms. The effects of these executive sequences can be precisely specified documented with tabular presentations of the program functions. Also, large programs can be decomposed and presented at a collection of well-documented smaller programs. (4) Tripod Approach to Assessment: There are three basic approaches to the assessment of complex software products: (i) testing, (ii) systematic inspection, and (iii) certification of people and processes. Assessment of a complex system cannot depend on any one of these alone. The approach used on the Darlington shutdown software, which included systematic inspection as well as planned and statistically designed random testing, is outlined.

Download

Managing Complexity in Safety-Critical Software

November 1990

·

68 Reads

·

1 Citation

This paper outlines an approach to the design, documentation, and evaluation of computer systems. We believe that this approach makes it possible to control the complexity that is present in software products and allows the use of software in many safety-critical applications. Our approach to dealing with complex systems has been described by E.W. Dijkstra as “separation of concerns” and is supported by the use of rigidly organized mathematical documentation. Many of the ideas presented in this paper have been used by the Atomic Energy Control Board of Canada (AECB) in their safety assessment of the software for the shutdown systems of the Darlington Nuclear Power Station.


Citations (2)


... However, many project requirements documents are non-formal, semi-formal, there are many problems such as inaccurate, inconsistent, incomplete, and poor readability and so on, all of these brought great difficult to verify whether the software is consistent with requirements. Document-driven development methods software proposed by Professor David L. Parnas emphasizes the role of document in the software development process, describes each important element and performance of the software system requirements as a precise math relation set, and provides a series verification [1][2][3] of the integrity and consistency of the formal requirements document. In this method professor Parnas gives a generic model of requirement document named 4-variable model [4], which uses the environment variables and the relationship between environment variables to characterize the requirement of computer system. ...

Reference:

A Verification Method of Software Acceptability
Reviewable development of safety critical software
  • Citing Article
  • January 1990

... Statistical testing [4,10,8] provides a direct estimate of the software probability of failure on demand (pfd) of a demand-based system to some confidence bound, and it is recommended in functional safety standards such as IEC 61508 [6]. The standard approach to deriving a confidence bound on the pfd of a software-based system is to perform statistical testing on the whole system as a "black-box". ...

Assessment of safety-critical software in nuclear power plants