Abstract: Chapter 5 Developing System Safety Requirements Louis J. Gullo, Louis J. GulloSearch for more papers by this author Louis J. Gullo, Louis J. GulloSearch for more papers by this author Book Editor(s):Louis J. Gullo, Louis J. Gullo Raytheon Missile Systems, Arizona, USASearch for more papers by this authorJack Dixon, Jack Dixon JAMAR International, Inc., Florida, USASearch for more papers by this author First published: 08 December 2017 https://doi.org/10.1002/9781118974339.ch5 AboutPDFPDF ToolsRequest permissionExport citationAdd to favoritesTrack citation ShareShareShare a linkShare onFacebookTwitterLinked InRedditWechat Summary Safety requirements ensure a safe design. System/product requirements must address the expectations of the customer in terms of safe system/product operation. Systems requirements analysis (SRA) is a significant task that deserves sufficient time and energy to make sure system requirements are good. The primary focus of any system safety plan, hazard analysis, and safety assessment is to identify operational behaviors, anomalous conditions, faults, or human errors that could lead to a safety-critical failure, hazard, or potential mishap. When hazard controls are planned, the need for hazard controls is transformed into a set of design or process requirements forming a safety standard. This chapter explains on how to identify good and bad requirements and why requirements are bad and recommends changes to fix bad requirements. It provides an example of certification and validation of requirements for a system safety device called a presence sensing device initiation (PSDI) used in mechanical power presses. Design for Safety RelatedInformation
Publication Year: 2017
Publication Date: 2017-12-08
Language: en
Type: other
Indexed In: ['crossref']
Access and Citation
Cited By Count: 1
AI Researcher Chatbot
Get quick answers to your questions about the article from our AI researcher chatbot