Definition: Resiliency is an IT non-functional requirement that refers to the ability of a system to recover quickly and efficiently from unexpected events or failures. This includes the ability to maintain availability, performance, and data integrity in the face of disruptions such as hardware failures, network outages, or cyber attacks. A resilient system is designed to minimize downtime, prevent data loss, and ensure business continuity, even in the face of adverse conditions. This requirement is critical for any system that needs to operate reliably and consistently, particularly in mission-critical applications such as financial services, healthcare, or emergency response. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Resiliency is a non-functional requirement that refers to the ability of an IT system to recover from failures or disruptions and continue to function as intended. This requirement is essential for ensuring that the system can withstand unexpected events such as hardware failures, power outages, or cyber-attacks. To meet the Resiliency requirement, IT systems must be designed with redundancy and fault-tolerant mechanisms that enable them to continue operating even when one or more components fail. This may involve the use of backup systems, redundant hardware, or failover mechanisms that automatically switch to a backup system when the primary system fails. In addition to technical measures, Resiliency also requires the implementation of robust disaster recovery and business continuity plans that outline procedures for responding to disruptions and restoring normal operations as quickly as possible. These plans should be regularly tested and updated to ensure that they remain effective in the face of changing threats and circumstances. Overall, Resiliency is a critical non-functional requirement for IT systems that must be carefully considered and addressed throughout the entire system development lifecycle. By ensuring that systems are designed with Resiliency in mind, organizations can minimize the risk of downtime and data loss, and maintain the continuity of their operations even in the face of unexpected events. Example: One example of the IT non-functional requirement 'Resiliency' could be that the system should be able to recover from hardware or software failures within a specified time frame, without losing any data or causing significant downtime. This could involve implementing redundancy measures such as backup servers, failover mechanisms, and data replication to ensure that the system can continue to operate even in the event of a failure. Additionally, the system should be able to handle high levels of traffic or usage without becoming overwhelmed or crashing, and should be able to scale up or down as needed to accommodate changing demands. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:ResiliencyRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirement dct:title: Resiliency Non-Functional Requirement