Definition: Detail-Level Requirement Leftover is a Requirement formulating specific low-level capabilities of a software system that remain unaddressed after the primary decomposition and allocation of requirements to solutions. It captures residual functional or non-functional needs that emerge when major requirements are assigned to specific solutions, ensuring comprehensive coverage of the problem domain without gaps in the implementation. Source: EIRA Team Last modification: 2026-01-03 Identifier: http://data.europa.eu/dr8/Detail-LevelRequirementLeftoverRequirement LOST view: EIRA Ontology view EIRA concept: eira:ArchitectureBuildingBlock ABB name: eira:Detail-LevelRequirementLeftoverRequirement Synonym: Residual Requirement Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): When implementing a digital public service platform, three primary requirements address authentication (Requirement A), data storage (Requirement B), and workflow management (Requirement C). However, audit logging capabilities, session timeout handling, and error notification mechanisms remain unaddressed. These constitute Detail-Level Requirement Leftovers that must be captured and implemented to ensure complete system functionality and compliance with digital public service standards. Interoperability Saliency: Detail-Level Requirement Leftover ABB is salient for semantic and technical interoperability because it ensures (i) completeness in requirements coverage, preventing functional gaps in interoperable systems; (ii) traceability of all system capabilities back to identified needs; and (iii) systematic identification of cross-cutting concerns that may impact integration points between different digital public services or components. Additional information: This ABB addresses the practical reality that requirement decomposition rarely results in perfect partitioning. Leftover requirements typically include cross-cutting concerns, edge cases, non-functional requirements, or integration aspects that don't fit neatly into primary requirement categories but are essential for complete solution delivery. Interoperability Dimension: Governance IoP EIF Layer: N/A