Data model: Difference between revisions

Revision as of 10:19, 15 January 2006

Revision as of 17:23, 24 January 2006

Line 7:

#or how data of a specific business function is organized logically (e.g. the data model of some business)

== General Organizationorganization of Datadata ==

In general the first aspect ("[[database model]]") describes the following :

Line 20:

Additional information about this topic can also be found in [[Database management system|database management system]].

== Organization of Datadata in a Specificspecific Applicationapplication (Domain___domain) ==

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").

Line 26:

If a relational model is used, sets of specific constraints ([[candidate key]]s, [[foreign key]]s) have to be defined (using the appropriate language as defined for the general model, e.g. [[SQL]]).

== Tools for Creatingcreating a Datadata model for an Applicationapplication ==

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 [[Object Role Modeling]] (ORM) 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.