Requirements · Concepts · European Finance Observatory

Roles that need it

User storyA user story is a short requirement written from the user's point of view, usually in the form "As a [role], I want [capability] so that [benefit]". It is small enough to deliver in one sprint and comes with acceptance criteria.
Acceptance criteriaAcceptance criteria are the specific, testable conditions a feature or user story must meet to be accepted, often written as "Given [context], when [action], then [result]". They guide development and form the basis of test cases and UAT.
Non-functional requirementA non-functional requirement defines how well a system must work, as opposed to what it does: response time, availability, capacity, security, auditability, recoverability. In finance, many come from regulation, such as DORA resilience rules or record-keeping duties.
Gap analysisGap analysis compares the current state with a required or desired state, such as a new regulation or a target operating model, and lists each difference with its impact, owner and remediation action. It is a standard first step in regulatory change projects.

Updated 31 Oct 2026.