Dbm (discuter | contributions) m |
Dbm (discuter | contributions) m |
||
Ligne 1 : | Ligne 1 : | ||
==Modeling and Meta-modeling== | ==Modeling and Meta-modeling== | ||
− | ===Database Models=== | + | ===<big>Database Models</big>=== |
*'''Description''' | *'''Description''' | ||
− | :The development and the exploitation of data models are | + | :The development and the exploitation of data models are the baseline of the database engineeering domain. They allow database structures to be described at the appropriate level of abstraction, so that schemas can be evaluated, transformed and reasoned about them rigourously. They are at the core of design methodologies and CASE tools. The <b>conceptual models</b>, such as the Entity-relationship model and some interpretation of UML class diagrams are aimed at describing data/information structures at the conceptual, technology-independent level, while the many <b>logical models</b> currently available are intended to represent data structures as they are implemented by data managers (or by families thereof). |
− | :*<b>The | + | :*<b>The SPHINX data models</b>. |
:*<b>The Individual model</b>. Reference [P74-04] reports on the first version on the Individual model (a variant of the ER model), which was the main component of the MERISE methodology. Hubert Tardieu, the architect of the Merise methodology was a member of the team. | :*<b>The Individual model</b>. Reference [P74-04] reports on the first version on the Individual model (a variant of the ER model), which was the main component of the MERISE methodology. Hubert Tardieu, the architect of the Merise methodology was a member of the team. | ||
:*<b>The GAM</b>. | :*<b>The GAM</b>. |