Distinguishes a business requirement from a design solution
https://knobit.org/id/knobit/K-152
Also as Turtle · JSON-LD · RDF/XML · AI benchmark on Skilirium
| Context functions | Object understanding |
|---|---|
| Knobit creation methods | AI generated |
| Knobit types | Knowledge |
| LCG purposes | Assessing the learner's knowledge or skill state |
| LCG purposes | Opening up a learning outcome |
| action verb | Distinguishes en |
| assessment criterion | Classifies sample statements as requirement or solution and restates each solution as its requirement en |
| assessment method | Written question with sample data requirements en |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:identifier | K-152 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Data-management practice used by the stage 1 reference and review checklist en |
| expected result | A business requirement says what the business must know; a solution names a table, column, type or screen en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-modelling/01-requirements/K-152 |
| rdfs:label | Distinguishes a business requirement from a design solution en |
| schema:creativeWorkStatus | accepted |
| schema:isPartOf | Data modelling (DAMA-DMBOK2) |
| skos:definition | A business requirement says what the business must know; a solution names a table, column, type or screen. en |
| skos:prefLabel | Distinguishes a business requirement from a design solution en |
| target object | business requirement and design solution en |
Used by
| applies knowledge | Recognises a data requirement prescribing a design solution |
|---|---|
| includes knobit | Captures atomic, sourced and testable data requirements |
| requires knobit | Capture data requirements |