knobit.org

Derive the logical data model

edu:Activity

https://knobit.org/id/activity/LO-5

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/activity/data-modelling/05-logical
rdfs:commentStage 3 (Logical) of the data-modelling skill: produces 03-logical/logical-model.yaml and passes the stage's validation gate. en
rdfs:labelDerive the logical data model en
rdfs:labelLoogilise andmemudeli tuletamine et
requires knobitRecognises an insertion anomaly in a logical data model
requires knobitRecognises an update anomaly in a logical data model
requires knobitRecognises a deletion anomaly in a logical data model
requires knobitRecognises a repeating group in an entity
requires knobitRecognises an attribute holding several facts
requires knobitRecognises an attribute with several meanings
requires knobitRecognises attributes held as name-value rows
requires knobitRecognises a partial dependency on a composite key
requires knobitRecognises a transitive dependency between non-key attributes
requires knobitRecognises a stored derivable attribute
requires knobitRecognises a non-superkey determinant in a 3NF entity
requires knobitRecognises independent multi-valued facts in one entity
requires knobitRecognises a join dependency kept in one entity
requires knobitRecognises a lossy decomposition
requires knobitRecognises a functional dependency lost in a decomposition
requires knobitRecognises attributes inapplicable to some instances
requires knobitRecognises an unstable or meaningful primary key
requires knobitRecognises an entity identified only by a system-assigned key
requires knobitRecognises undeclared subtype constraints
requires knobitRecognises independently changing histories in one entity
requires knobitRecognises an unresolved many-to-many relationship
requires knobitRecognises a polymorphic association
requires knobitRecognises a connection trap
requires knobitRecognises a fan trap
requires knobitRecognises a chasm trap
requires knobitRecognises a redundant relationship
requires knobitRecognises overlapping entities
requires knobitRecognises one entity split by value into several
requires knobitRecognises a relationship contradicting its data rule
requires knobitRecognises a constraint implied by neither keys nor domains
requires knobitTraces a logical-model anomaly to its structural cause
requires knobitRecords the functional dependencies of an entity
requires knobitDecomposes an entity along a functional dependency without loss
requires knobitResolves a many-to-many relationship into an associative entity
requires knobitReplaces a repeating group with a dependent entity
requires knobitIntroduces subtypes for attributes applying to only some instances
requires knobitExplains functional dependency
requires knobitExplains candidate key and prime attribute
requires knobitExplains the insertion, update and deletion anomalies
requires knobitExplains first normal form
requires knobitExplains second normal form
requires knobitExplains third normal form
requires knobitExplains Boyce-Codd normal form
requires knobitExplains multivalued dependency and fourth normal form
requires knobitExplains join dependency and fifth normal form
requires knobitExplains sixth normal form for temporal data
requires knobitExplains domain-key normal form
requires knobitExplains attribute domains
requires knobitExplains lossless-join decomposition
requires knobitExplains dependency preservation
requires knobitExplains derived data and point-in-time snapshots
requires knobitExplains supertype and subtype constraints
requires knobitExplains relationship cardinality and optionality
requires knobitExplains natural keys, surrogate keys and key stability
requires knobitExplains the connection, fan and chasm traps
requires knobitExplains an entity type as the realisation of one business concept
requires knobitExpresses a logical model as a UML class diagram
requires knobitModels data as fact types in a fact-based scheme
requires knobitMaps an application model onto a canonical model
schema:position3

Used by

consists ofData modelling