I3 (3 points)
https://knobit.org/id/task/dm-planning/I3
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dm-planning/I3 |
| rdfs:label | I3 (3 points) en |
| schema:hasPart | dm-planning I3: naming, definition and design standards set once |
| schema:identifier | I3 |
| schema:position | 9 |
| schema:text | Part B sets the standards once, 1 each: (a) one naming convention is chosen and the plan and model_config.conventions say the same - ISO 11179 names for the logical model, as the bank standard says, and snake case for physical names; adopting the BI developer's snake case for the logical model, or recording it in one file only, scores 0; (b) the abbreviation list and the definition rule (ISO/IEC 11179-4, as the glossary uses) are named; (c) the design principles the physical model must keep cover keys (surrogate keys, natural keys kept unique), nullability and history (an SCD type or effective dating), and the config agrees where it has a field for them (surrogate_keys, audit_columns). en |
Used by
| has question | Modelling plans and standards, reviewed and written (planning and standards skills) |
|---|---|
| schema:isPartOf | dm-planning I3: naming, definition and design standards set once |