TAILIEUCHUNG - Lecture Software engineering: Chapter 14 – Resilience Engineering

Chapter 14 – Resilience Engineering. This lecture presents brief overview of project quality management and key concepts related to project communication management. ISO defines the quality as “the totality of characteristics of an entity that bear on its ability to satisfy stated or implied needs” or “the degree to which a set of inherent characteristics fulfill requirements”. | Chapter 14 – Resilience Engineering 1 Chapter 15 Resilience engineering 13/11/2014 Topics covered Cybersecurity Sociotechnical resilience Resilient systems design 13/11/2014 Chapter 15 Resilience engineering 2 Resilience The resilience of a system is a judgment of how well that system can maintain the continuity of its critical services in the presence of disruptive events, such as equipment failure and cyberattacks. Cyberattacks by malicious outsiders are perhaps the most serious threat faced by networked systems but resilience is also intended to cope with system failures and other disruptive events. 13/11/2014 Chapter 15 Resilience engineering 3 Essential resilience ideas The idea that some of the services offered by a system are critical services whose failure could have serious human, social or economic effects. The idea that some events are disruptive and can affect the ability of a system to deliver its critical services. The idea that resilience is a judgment – there are no resilience metrics and resilience cannot be measured. The resilience of a system can only be assessed by experts, who can examine the system and its operational processes. 13/11/2014 Chapter 15 Resilience engineering 4 Resilience engineering assumptions Resilience engineering assumes that it is impossible to avoid system failures and so is concerned with limiting the costs of these failures and recovering from them. Resilience engineering assumes that good reliability engineering practices have been used to minimize the number of technical faults in a system. It therefore places more emphasis on limiting the number of system failures that arise from external events such as operator errors or cyberattacks. 13/11/2014 Chapter 15 Resilience engineering 5 Resilience activities Recognition The system or its operators should recognise early indications of system failure. Resistance If the symptoms of a problem or cyberattack are detected early, then resistance strategies may be used to reduce

• Kỹ thuật lập trình
• Software engineering
• Công nghệ phần mềm
• Lecture Software engineering
• Software design
• Software project management
• Quality management
• Object oriented software engineering
• Practical software development
• Object orientation
• Software quality
• Software engineering projects
• Introduction to software engineering
• Lecture Introduction to software engineering
• Software process
• Software engineering ethics
• Professional software development
• Software process activities
• Software engineering diversity
• Introduction Software Engineering
• Software products
• FAQs about software engineering
• Essential attributes of good software
• Importance of software engineering
• Software processes
• Aspect oriented software engineering
• The separation of concerns
• Software engineering with aspects
• Quality concepts
• Detail Design
• Design Software Engineering
• Implementation Software Engineering
• Build Software Engineering
• Buy Software Engineering
• Requirement engineering
• Requirement engineering process
• Software requirements engineering
• Lecture Software requirements engineering
• Requirements engineering
• Software requirements engineering
• Lecture Software requirements engineering
• System engineering
• Software requirements document
• Requirements engineering process tasks