Recognises a requirements register with unbounded scope

K-125 · Skill knobit · Activity: Capture data requirements · Competence: Data modelling

Nothing says what the data is for, what is out of scope, or which existing systems hold overlapping data. Requirements keep arriving and none can be declined.

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 missing purpose, exclusions and overlapping systems

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: A payments mart register with no statement of whether card transactions or payments from the correspondent-banking channel are in scope Acceptable: A scope note in the project (purpose, in, out, overlapping systems) and out-of-scope requests recorded as status: rejected with a reason.

Also known as: Scope not bounded (data requirement)

Related knobits

Builds on

• K-158 Explains the scope, events and questions a data register must state

All 47 knobits of Capture data requirements.

Source: Review checklist 01-requirements, row 25; 29148 5.2.6 (complete); Stage 1 (scope and purpose)