Definition: Latency is a non-functional requirement that refers to the time delay between the initiation of a request and the response received. It is a critical factor in determining the overall performance of a system, particularly in real-time applications such as online gaming, video conferencing, and financial trading. Low latency is desirable as it ensures that the system responds quickly to user requests, providing a seamless and efficient user experience. High latency, on the other hand, can lead to frustration and decreased productivity, making it essential to ensure that latency is kept to a minimum in any IT system. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Latency is a non-functional requirement that refers to the time delay between the initiation of a request and the response received. It is a measure of the time taken for data to travel from one point to another, and is typically measured in milliseconds (ms). Latency is an important consideration for IT systems that require real-time or near-real-time responses, such as financial trading systems, online gaming platforms, and video conferencing applications. High latency can result in delays, lag, and poor user experience, which can negatively impact the performance and usability of the system. To ensure that latency requirements are met, IT architects must consider a range of factors, including network bandwidth, server processing power, and data storage capacity. They must also design systems that are optimized for low latency, using techniques such as caching, load balancing, and content delivery networks (CDNs). In addition, IT architects must work closely with stakeholders to define latency requirements and establish appropriate performance metrics. This may involve conducting performance testing and benchmarking to identify areas for improvement and ensure that the system meets the required latency targets. Overall, latency is a critical non-functional requirement that must be carefully considered and managed throughout the IT system development lifecycle to ensure optimal performance and user experience. Example: An example of the IT non-functional requirement 'Latency' could be for a video conferencing application to have a maximum latency of 100 milliseconds to ensure smooth and real-time communication between participants. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/LatencyRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:LatencyRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/LatencyRequirement dct:title: Latency Non-Functional Requirement