Abstract
The paper describes one approach to providing safety in software systems, recognizing that safety is more often relative than absolute, and that safety is a transient condition unless safeguards are provided. It is also shown that safety in a software system is achievable and is a function of analyst qualification, cohesion with management, and adherence to a clearly definable process.