Definition: Integrity is an IT non-functional requirement that ensures the accuracy, consistency, and reliability of data throughout its lifecycle. It involves maintaining the correctness and completeness of data, preventing unauthorized access or modification, and ensuring that data is not lost or corrupted due to system failures or errors. Integrity is critical for ensuring the trustworthiness of data and maintaining the credibility of the system that uses it. It is often achieved through the use of data validation, error checking, access controls, and backup and recovery mechanisms. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Integrity is a non-functional requirement that refers to the accuracy, consistency, and reliability of data and information within a system. It ensures that the data is protected from unauthorized access, modification, or deletion, and that it remains consistent and reliable throughout its lifecycle. Integrity is an essential requirement for any system that deals with sensitive or critical data, such as financial transactions, personal information, or medical records. It ensures that the data is not compromised or corrupted, and that it can be trusted by the users and stakeholders. To achieve integrity, the system must have appropriate security measures in place, such as access controls, authentication, encryption, and auditing. It must also have mechanisms to detect and prevent data tampering, such as checksums, digital signatures, or version control. Integrity is closely related to other non-functional requirements, such as availability, reliability, and performance. A system that lacks integrity may also suffer from data loss, downtime, or poor performance, which can have severe consequences for the users and the organization. Overall, integrity is a critical non-functional requirement that ensures the trustworthiness and reliability of data and information within a system. It must be carefully considered and implemented to ensure the security and effectiveness of the system. Example: One example of the IT non-functional requirement 'Integrity' is ensuring that data is not altered or modified during transmission or storage. This can be achieved through the use of encryption, checksums, and other security measures to prevent unauthorized access or tampering. Additionally, data backups and disaster recovery plans can help ensure that data remains intact and accessible in the event of a system failure or other disruption. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/IntegrityRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:IntegrityRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/IntegrityRequirement dct:title: Integrity Non-Functional Requirement