Looking at code with your safety goggles on.

This paper presents a process for the refinement of safety-critical source code into a more tractable representation. For large software-intensive information systems, the safety engineering view of the system reveals a "long thin slice" of hazard-related software involving a number of different software components. The hazard-related software is documented in the system "safety verification case" which provides a rigorous argument for the safety of the source code. The refinement process creates a representation of the source code which isolates the relevant source code details. A hypothetical chemical factory information system is examined to illustrate aspects of this process and its significance. [ABSTRACT FROM AUTHOR]