Recognises a data requirement prescribing a design solution

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

The statement names a table, column, index, datatype, system field or screen. The design is frozen before modelling and the need behind it is lost.

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 design element named and the business requirement behind it

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DR-008 "Create a payment table with an index on the payment number column." Acceptable: "Payments staff must be able to find a payment by its payment reference." The proposed table and index go in rationale.

Also known as: Solution instead of need (data requirement)

Related knobits

Builds on

• K-152 Distinguishes a business requirement from a design solution

All 47 knobits of Capture data requirements.

Source: Review checklist 01-requirements, row 2; 29148 5.2.5 (appropriate: implementation-free); REQ-012