Recognises a requirements register describing no events
Requirements describe nouns and their attributes, and nothing about what happens to them: status changes, reopenings, payments, corrections, cancellations. Events carry most volume, history and temporal rules.
Can AI do this?
Not tested yet
No AI benchmark covers this knobit yet. New results are announced in the Can AI Do the Job? newsletter.
What it looks like in practice
Expected result: The things whose events, changes and corrections are missing
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Twelve requirements about account attributes, none about how an account becomes dormant or blocked, or what a status change must record Acceptable: "Every change of account status must record the date, the new status and the reason." "Every payment reversal must record …"
Also known as: Only things, no events (data requirement)
Related knobits
Builds on
- K-158 Explains the scope, events and questions a data register must state
- K-902 Explains the types of modelled data
All 47 knobits of Capture data requirements.
Source: Review checklist 01-requirements, row 26; Stage 1 (the events)