Definition: Recoverability is an important non-functional requirement in IT that refers to the ability of a system to solve failures or errors and come-back to its normal functioning. This includes the ability to recover data, configurations, and settings after a system crash or other disruptions. Recoverability is critical for ensuring system availability and minimizing downtime, as well as for protecting against data loss and corruption. It involves implementing backup and recovery mechanisms, such as data replication, redundancy, and failover, to ensure that the system can quickly and reliably recover from any failures or errors. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Recoverability is a non-functional requirement that refers to the ability of a system to recover from failures or disasters. It is a critical aspect of system design and architecture, as it ensures that the system can continue to operate even in the event of unexpected events. Recoverability includes a range of features and capabilities that enable a system to recover from failures, including backup and restore capabilities, fault tolerance, and disaster recovery planning. These features are designed to ensure that the system can quickly and efficiently recover from any type of failure, whether it is a hardware failure, software failure, or a natural disaster. To achieve recoverability, system architects and designers must consider a range of factors, including the system's overall architecture, the types of failures that are most likely to occur, and the impact of those failures on the system's operations. They must also consider the cost and complexity of implementing recoverability features, as well as the potential impact on system performance and availability. Overall, recoverability is a critical non-functional requirement that must be carefully considered and designed into any system architecture. By ensuring that a system can recover quickly and efficiently from failures, organizations can minimize downtime, reduce costs, and ensure that critical business operations can continue uninterrupted. Example: In a banking application, the recoverability non-functional requirement would ensure that in case of a system failure or crash, the system can recover all the data and transactions that were in progress before the failure occurred. This would ensure that no data is lost and the system can resume normal operations without any major disruptions. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/RecoverabilityRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:RecoverabilityRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/RecoverabilityRequirement dct:title: Recoverability Non-Functional Requirement