4.1 Introduction
This section of the Handbook will introduce the managerial process and the technical methods and techniques inherent in the performance of software safety tasks within the context of a systems safety engineering and software development program. It will include detailed tasks and techniques for the performance of safety analysis, and for the traceability of SSRs from design to test. It will also provide the current “best practices” which may apply as one considers the necessary steps in establishing a credible and cost-effective SSS program (Figure 4-1).
Section 4 is applicable to all managerial and technical disciplines. It describes the processes, tools, and techniques to reduce the safety risk of software operating in safety-critical systems. Its primary purposes are as follows:
• Define a recommended software safety engineering process.
• Describe essential tasks to be accomplished by each professional discipline assigned to the SSS Team.
• Identify interface relationships between professional disciplines and the individual tasks assigned to the SSS Team.
• Identify “best practices” to complete the software safety process and describe each of its individual tasks.
• Recommend “tailoring” actions to the software safety process to identify specific user requirements.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Software System Safety Handbook.pdf | application/pdf | 2.15 MB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
All members of the system development team should read section 2 of the Software System Safety Handbook (SSSH). This section discusses the following major subjects:
• The major purpose for writing this Handbook
• The scope of the subject matter that this Handbook will present
• The authority by which a SSS program is conducted
• How this Handbook is organized and the best procedure for you to use, to gain its full
benefit.
As a member of the software development team, the safety engineer is critical in the design, and redesign, of modern systems. Whether a hardware engineer, software engineer, “safety specialist,” or safety manager, it is his/her responsibility to ensure that an acceptable level of safety is achieved and maintained throughout the life cycle of the system(s) being developed. This Handbook provides a rigorous and pragmatic application of SSS planning and analysis to be used by the safety engineer.