Definition: Accountability is an IT non-functional requirement that refers to the ability of a system to track and record the actions of users and processes. This requirement ensures that all activities within the system can be traced back to their source, allowing for transparency and responsibility. Accountability is essential for compliance with regulations and standards, as well as for detecting and preventing fraudulent or malicious activities. It also helps to build trust and confidence in the system by providing a clear audit trail of all actions taken.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Accountability is a non-functional requirement that refers to the ability to trace and audit the actions and decisions made by a system or its users. This requirement ensures that the system can be held responsible for its actions and that there is a clear record of who made what decision and when.
To meet this requirement, the system must have the ability to log and track all user actions and system events. This includes the ability to record user login and logout times, the actions taken by users while logged in, and any system events that occur during operation. The system must also be able to generate reports and audit trails that can be used to trace the actions and decisions made by the system and its users.
In addition, the system must provide mechanisms for controlling access to sensitive data and functionality. This includes the ability to restrict access to certain features or data based on user roles and permissions. The system must also provide mechanisms for enforcing data privacy and security policies to ensure that sensitive data is protected from unauthorized access or disclosure.
Overall, the Accountability non-functional requirement is critical for ensuring that the system is transparent and can be held responsible for its actions. By providing the ability to trace and audit user actions and system events, the system can be used with confidence and trust.
Example: One example of the IT non-functional requirement 'Accountability' could be ensuring that all actions taken by users on a system are logged and traceable to the individual user. This would allow for accountability in the event of any unauthorized or malicious activity on the system.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AccountabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AccountabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AccountabilityRequirement
dct:title: Accountability Non-Functional Requirement
|
|
dct:modified | 2024-01-28 |
dct:identifier | http://data.europa.eu/dr8/AccountabilityRequirement |
dct:title | Accountability Non-Functional Requirement |
skos:example | One example of the IT non-functional requirement 'Accountability' could be ensuring that all actions taken by users on a system are logged and traceable to the individual user. This would allow for accountability in the event of any unauthorized or malicious activity on the system. |
skos:definition | Accountability is an IT non-functional requirement that refers to the ability of a system to track and record the actions of users and processes. This requirement ensures that all activities within the system can be traced back to their source, allowing for transparency and responsibility. Accountability is essential for compliance with regulations and standards, as well as for detecting and preventing fraudulent or malicious activities. It also helps to build trust and confidence in the system by providing a clear audit trail of all actions taken. |
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, Accountability is a non-functional requirement that refers to the ability to trace and audit the actions and decisions made by a system or its users. This requirement ensures that the system can be held responsible for its actions and that there is a clear record of who made what decision and when.
To meet this requirement, the system must have the ability to log and track all user actions and system events. This includes the ability to record user login and logout times, the actions taken by users while logged in, and any system events that occur during operation. The system must also be able to generate reports and audit trails that can be used to trace the actions and decisions made by the system and its users.
In addition, the system must provide mechanisms for controlling access to sensitive data and functionality. This includes the ability to restrict access to certain features or data based on user roles and permissions. The system must also provide mechanisms for enforcing data privacy and security policies to ensure that sensitive data is protected from unauthorized access or disclosure.
Overall, the Accountability non-functional requirement is critical for ensuring that the system is transparent and can be held responsible for its actions. By providing the ability to trace and audit user actions and system events, the system can be used with confidence and trust. |
eira:PURI | http://data.europa.eu/dr8/AccountabilityRequirement |
dct:type | eira:AccountabilityRequirement |
eira:view | Digital Solution Non-Functional Requirements Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionNonFunctionalRequirementRequirement |