Definition: Legality is an IT non-functional requirement that ensures that the software or system complies with all applicable laws, regulations, and standards. It is important to ensure that the system does not violate any legal or regulatory requirements, such as data privacy laws, copyright laws, or industry-specific regulations. Failure to comply with these requirements can result in legal and financial consequences for the organization. Therefore, it is crucial to ensure that the system is designed and developed in accordance with all applicable legal and regulatory requirements.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Legality' refers to the compliance of the IT system with legal and regulatory requirements. This requirement ensures that the system adheres to all applicable laws, regulations, and standards, including data protection laws, intellectual property laws, and industry-specific regulations.
The Legality requirement also includes the need for the system to be auditable and transparent, allowing for regulatory compliance checks and audits. The system must also provide appropriate documentation and reporting capabilities to demonstrate compliance with legal and regulatory requirements.
In addition, the Legality requirement also encompasses the need for the system to be secure and protect sensitive data from unauthorized access or disclosure. This includes the implementation of appropriate security measures, such as encryption, access controls, and monitoring, to ensure that the system meets legal and regulatory requirements for data protection.
Overall, the Legality requirement is critical for ensuring that the IT system operates within the boundaries of the law and meets all applicable legal and regulatory requirements. Failure to meet this requirement can result in legal and financial penalties, reputational damage, and loss of customer trust.
Example: One example of an IT non-functional requirement related to legality could be ensuring compliance with data privacy laws such as GDPR or CCPA. This could include requirements for data encryption, user consent for data collection and processing, and data retention policies.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LegalityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:LegalityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/LegalityRequirement
dct:title: Legality Non-Functional Requirement
|
|
dct:modified | 2024-01-28 |
dct:identifier | http://data.europa.eu/dr8/LegalityRequirement |
dct:title | Legality Non-Functional Requirement |
skos:example | One example of an IT non-functional requirement related to legality could be ensuring compliance with data privacy laws such as GDPR or CCPA. This could include requirements for data encryption, user consent for data collection and processing, and data retention policies. |
skos:definition | Legality is an IT non-functional requirement that ensures that the software or system complies with all applicable laws, regulations, and standards. It is important to ensure that the system does not violate any legal or regulatory requirements, such as data privacy laws, copyright laws, or industry-specific regulations. Failure to comply with these requirements can result in legal and financial consequences for the organization. Therefore, it is crucial to ensure that the system is designed and developed in accordance with all applicable legal and regulatory requirements. |
eira:concept | eira:ArchitectureBuildingBlock |
eira:definitionSource | TOGAF |
eira:definitionSourceReference | https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html |
skos:note | According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Legality' refers to the compliance of the IT system with legal and regulatory requirements. This requirement ensures that the system adheres to all applicable laws, regulations, and standards, including data protection laws, intellectual property laws, and industry-specific regulations.
The Legality requirement also includes the need for the system to be auditable and transparent, allowing for regulatory compliance checks and audits. The system must also provide appropriate documentation and reporting capabilities to demonstrate compliance with legal and regulatory requirements.
In addition, the Legality requirement also encompasses the need for the system to be secure and protect sensitive data from unauthorized access or disclosure. This includes the implementation of appropriate security measures, such as encryption, access controls, and monitoring, to ensure that the system meets legal and regulatory requirements for data protection.
Overall, the Legality requirement is critical for ensuring that the IT system operates within the boundaries of the law and meets all applicable legal and regulatory requirements. Failure to meet this requirement can result in legal and financial penalties, reputational damage, and loss of customer trust. |
eira:PURI | http://data.europa.eu/dr8/LegalityRequirement |
dct:type | eira:LegalityRequirement |
eira:view | Digital Solution Non-Functional Requirements Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionNonFunctionalRequirementRequirement |