Lecture Software engineering (7/e): Chapter 9 – Ian Sommerville

To explain how dependability requirements may be identified by analysing the risks faced by critical systems, to explain how safety requirements are generated from the system risk analysis, to explain the derivation of security requirements, to describe metrics used for reliability specification. | Critical Systems Specification Objectives To explain how dependability requirements may be identified by analysing the risks faced by critical systems To explain how safety requirements are generated from the system risk analysis To explain the derivation of security requirements To describe metrics used for reliability specification Topics covered Risk-driven specification Safety specification Security specification Software reliability specification Dependability requirements Functional requirements to define error checking and recovery facilities and protection against system failures. Non-functional requirements defining the required reliability and availability of the system. Excluding requirements that define states and conditions that must not arise. Risk-driven specification Critical systems specification should be risk-driven. This approach has been widely used in safety and security-critical systems. The aim of the specification process should be to understand the risks . | Critical Systems Specification Objectives To explain how dependability requirements may be identified by analysing the risks faced by critical systems To explain how safety requirements are generated from the system risk analysis To explain the derivation of security requirements To describe metrics used for reliability specification Topics covered Risk-driven specification Safety specification Security specification Software reliability specification Dependability requirements Functional requirements to define error checking and recovery facilities and protection against system failures. Non-functional requirements defining the required reliability and availability of the system. Excluding requirements that define states and conditions that must not arise. Risk-driven specification Critical systems specification should be risk-driven. This approach has been widely used in safety and security-critical systems. The aim of the specification process should be to understand the risks (safety, security, etc.) faced by the system and to define requirements that reduce these risks. Stages of risk-based analysis Risk identification Identify potential risks that may arise. Risk analysis and classification Assess the seriousness of each risk. Risk decomposition Decompose risks to discover their potential root causes. Risk reduction assessment Define how each risk must be taken into eliminated or reduced when the system is designed. Risk-driven specification Risk identification Identify the risks faced by the critical system. In safety-critical systems, the risks are the hazards that can lead to accidents. In security-critical systems, the risks are the potential attacks on the system. In risk identification, you should identify risk classes and position risks in these classes Service failure; Electrical risks; Insulin pump risks Insulin overdose (service failure). Insulin underdose (service failure). Power failure due to exhausted battery (electrical). Electrical .

Không thể tạo bản xem trước, hãy bấm tải xuống
TÀI LIỆU MỚI ĐĂNG
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.