| Index: > A B C D E F G H I J K L M N O P Q R S T U V W X Y Z |
|
|||||
This term is ambiguously defined to mean:
In general the first aspect (" database model ") describes the following:
For example in the relational model all data is represented by
mathematical relations (or, to be precise, a slightly generalized version thereof).There exists a general language for specifying constraints ( first-order logic), and for manipulations and querying the data the relational algebra, tuple calculus and domain calculus are introduced. Additional information about this topic can also be found in database management system.
For a specific application tables (objects, relations, ..., the naming conventions depend on the general model) are defined, for example "customer", "order", "item" as well as relations between them ("customer orders items").
If a relational model is used, sets of specific constraints ( candidate keys, foreign keys) have to be defined (using the appropriate language as defined for the general model, e.g. SQL).
While simple data models consisting of few tables or objects can be created "manually" large applications need a more systematic approach. The Entity-Relationship Model method is used to establish a domain specific data model. Other methods like the Functional Data Model and the Object Role Model also describe subsets/aspects of a data model and the application based on it. The Unified Modeling Language (UML) is another method more related to object-oriented data models. Especially the "Object Model" part has a number of parallel representations with the Entity-Relationship Model.
Data modeling