Skilirium

Recognises a missing or wrong requirement type

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

No type, a value outside the seven in the schema, or a type that does not match the statement. The type decides where the requirement lands later.

Can AI do this?

People still lead Few or none of the tested AI models showed they master this. 0 of 10 models master it.

ModelTierProbability of masteryStatus
gemini-4-argonFlagship 20%Not shown
gemini-3.1-pro-previewFlagship 33%Not shown
gpt-6-astraFlagship 20%Not shown
claude-fable-5-1Flagship 21%Not shown
gemini-3.8-flashMid tier 21%Not shown
gpt-6.1-solMid tier 19%Not shown
claude-sonnet-5-5Mid tier 22%Not shown
gemini-3.5-flash-liteLow cost 36%Not shown
gpt-6-lunaLow cost 20%Not shown
claude-haiku-5-5Low cost 19%Not shown

Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.

What it looks like in practice

Expected result: The requirement and the type its statement implies

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DR-009 "Payment volumes reach ninety thousand rows a year." with type: reporting Acceptable: type: volume. A requirement for a report becomes one requirement per question the report answers (row 32), each typed by what it asks for.

Also known as: Type missing or wrong (data requirement)

Related knobits

Builds on

All 47 knobits of Capture data requirements.

Source: Review checklist 01-requirements, row 17; 29148 5.2.8 (type); REQ-013, REQ-014