Recognises a business rule left inside another statement

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

A rule stated in the source or by a stakeholder survives only inside a data-item statement, a spreadsheet column or a meeting note, instead of as its own type: data-rule requirement. Stage 3 formalises requirements, so it will never see it. An empty rules list is expected at stage 1 and is not this defect.

Can AI do this?

AI does this well Most of the tested AI models master this. 9 of 10 models master it.

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 buried rule as its own data-rule requirement

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Spreadsheet row IBAN, Business rules column: "Every account has an IBAN. No two accounts share an IBAN.", captured as one data-item requirement "Every account has an IBAN." Acceptable: data-item "Every account must be identified by its IBAN." plus two data-rule requirements in the source's words: "Each account has exactly one IBAN." and "An IBAN is never assigned to more than one account." Stage 3 formalises both and fills rules.

Also known as: Candidate rule not captured (data requirement)

Related knobits

Builds on

• K-355 Explains Witt's classification of business rules

All 47 knobits of Capture data requirements.

Source: Review checklist 01-requirements, row 13; Stage 1 (candidate rules); 03-data-rules.md row 18