Recognises a business rule left inside another statement
https://knobit.org/id/knobit/K-113
Also as Turtle · JSON-LD · RDF/XML · AI benchmark on Skilirium
| Context functions | Result evaluation |
|---|---|
| Knobit creation methods | AI generated, human edited |
| Knobit types | Skill |
| LCG purposes | Assessing the learner's knowledge or skill state |
| LCG purposes | Selecting an assessment task or learning activity |
| action verb | Recognises en |
| applies knowledge | Explains Witt's classification of business rules |
| assessment criterion | 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`. en |
| assessment method | skill-tests task: Loan application data requirements (data requirement capture skills) en |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:identifier | K-113 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Review checklist 01-requirements, row 13; Stage 1 (candidate rules); `03-data-rules.md` row 18 en |
| expected result | The buried rule as its own data-rule requirement en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-modelling/01-requirements/13 |
| rdfs:label | Recognises a business rule left inside another statement en |
| schema:creativeWorkStatus | accepted |
| schema:isPartOf | Data modelling (DAMA-DMBOK2) |
| skos:altLabel | Candidate rule not captured (data requirement) en |
| skos:definition | 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. en |
| skos:prefLabel | Recognises a business rule left inside another statement en |
| target object | rule buried in a data-item statement, cell or note en |
Used by
| includes knobit | Captures atomic, sourced and testable data requirements |
|---|---|
| requires knobit | Capture data requirements |