Dbm (discuter | contributions) m |
Dbm (discuter | contributions) m |
||
| (6 révisions intermédiaires par un utilisateur sont masquées) | |||
| Ligne 1 : | Ligne 1 : | ||
| − | <center><big><b>Pages en cours de développement | + | <center><big><b>Pages in development / Pages en cours de développement</b></big></center> |
| − | <center><big><big><big><b> | + | <center><big><big><big><b>Themes and resources/ Thèmes et ressources</b></big></big></big></center> |
| − | :: | + | ::This section collects and integrates the resources of the Computer science faculty and, more specifically of the DB research group, into themes related to Database Engineering (and some others). |
| − | :: | + | ::Cette section regroupe et intègre les différentes ressources de la faculté d'informatique et du LIBD en particulier, autour de thématiques liées à l'Ingénierie des bases de données (et quelques autres). |
| − | [[Accueil|<''Retour à la page d'accueil | + | [[Accueil|<''Back to Welcome page / Retour à la page d'accueil>]] |
| + | |||
| + | |||
| + | ==Foreword== | ||
| + | |||
| + | This section of the site will present the contribution of the Computer science faculty of the University of Namur to the Database discipline since 1971. In short, an overview of the first 40 years of research in DB engineering! I will leave the development of the next 40 years to my young colleagues. | ||
| + | |||
| + | This work is not a simple task, and I don't expect its completion before at least one or two years | ||
| + | |||
| + | Jean-Luc Hainaut, June 2011 | ||
| Ligne 16 : | Ligne 25 : | ||
TBA | TBA | ||
| + | |||
==Modeling and Metamodeling== | ==Modeling and Metamodeling== | ||
*'''Introduction''' | *'''Introduction''' | ||
:Database engineeering addresses domains such as database exploitation, database design, database reverse engineering or database evolution. A database is described through a hierarchy of ''schemas'', each of them expressed in a '''data''' (or information) '''model'''. A large part of database engineering resort to schema manipulation, where data structures are built, analyzed, evaluated, transformed and used to produced various artefacts such as other schemas, DML and DDL code. The quality and the effectiveness of these schema manipulation processes depend on the availability of appropriate data models. Hence the importance of model development activities ('''Database Models'''). | :Database engineeering addresses domains such as database exploitation, database design, database reverse engineering or database evolution. A database is described through a hierarchy of ''schemas'', each of them expressed in a '''data''' (or information) '''model'''. A large part of database engineering resort to schema manipulation, where data structures are built, analyzed, evaluated, transformed and used to produced various artefacts such as other schemas, DML and DDL code. The quality and the effectiveness of these schema manipulation processes depend on the availability of appropriate data models. Hence the importance of model development activities ('''Database Models'''). | ||
| − | :A data model states a definite way to view data but, to be complete, it must be accompanied by '''languages''' that tell how to interact with the contents of database, that is, how to manipulate these data. Sometimes, such language takes the form of an '''API''' (application program interface) that also defines the technical | + | :A data model states a definite way to view data but, to be complete, it must be accompanied by '''languages''' that tell how to interact with the contents of database, that is, how to manipulate these data. Sometimes, such language takes the form of an '''API''' (application program interface) that also defines the technical detail of these interactions ('''Database languages'''). |
:The design and evaluation of models require a means to describe them in a general way and to reason about them (for example, ''how the Entity-relationship model compares with UML class diagrams?'') This is the concern of '''metamodeling''', that proposes models to reason about models, and that are, for that, metamodels ('''Metamodeling'''). | :The design and evaluation of models require a means to describe them in a general way and to reason about them (for example, ''how the Entity-relationship model compares with UML class diagrams?'') This is the concern of '''metamodeling''', that proposes models to reason about models, and that are, for that, metamodels ('''Metamodeling'''). | ||
:This chapter describes the contribution of the LIBD to the development of database models, database languages and API’s and metamodels. | :This chapter describes the contribution of the LIBD to the development of database models, database languages and API’s and metamodels. | ||
| Ligne 32 : | Ligne 42 : | ||
*'''Keywords''' | *'''Keywords''' | ||
| − | :ER model, Individual model, Merise model, UML class diagrams, wide-spectrum model, GER model, DB-MAIN model, logical data model, temporal model, legacy data model, relational model, network model, hierarchical model, OO model, OR model, XML model, large schema layout, semantic and statistical aspects of models, IS-A relation, wrappers | + | :ER model, Individual model, Merise model, UML class diagrams, wide-spectrum model, GER model, DB-MAIN model, logical data model, temporal model, legacy data model, relational model, network model, hierarchical model, OO model, OR model, XML model, decision support, large schema layout, semantic and statistical aspects of models, IS-A relation, wrappers |
:''[[LIBD:Themes:Database-Models|<Go to the <b>Database Models</b> page for more detail>]]'' | :''[[LIBD:Themes:Database-Models|<Go to the <b>Database Models</b> page for more detail>]]'' | ||
| Ligne 48 : | Ligne 58 : | ||
*'''Status''': ''complete'' | *'''Status''': ''complete'' | ||
*'''Description''' | *'''Description''' | ||
| − | :Meta-''something'' is ''something'' about ''something'' (replace ''something'' by any name pertaining to philosophy or computer science). For instance, metadata are data that describe the structure and other properties of data (generally user data). For instance, the ''table of tables'' (generically named SYS_TABLE) in the ''catalog'' of any relational database is a metatable that contains metadata. Being said in passing, it includes a row that describes this table itself. | + | :Meta-''something'' is ''something'' about ''something'' (replace ''something'' by any name pertaining to philosophy, mathematics or computer science). For instance, metadata are data that describe the structure and other properties of data (generally user data). For instance, the ''table of tables'' (generically named SYS_TABLE) in the ''catalog'' of any relational database is a metatable that contains metadata. Being said in passing, it includes a row that describes this table itself. |
:The domain of database engineering makes much use of ''meta''-level concepts. For instance any CASE tool includes some sort of database in which it stores its data. This database contains descriptions of schemas, among others. These descriptions are metadata. This database bears several names according to the community that uses it, namely ''metadatabase'', ''metabase'', ''(metadata) repository'', ''model base'' or ''encyclopedia'' (this one a bit outdated). | :The domain of database engineering makes much use of ''meta''-level concepts. For instance any CASE tool includes some sort of database in which it stores its data. This database contains descriptions of schemas, among others. These descriptions are metadata. This database bears several names according to the community that uses it, namely ''metadatabase'', ''metabase'', ''(metadata) repository'', ''model base'' or ''encyclopedia'' (this one a bit outdated). | ||
:The term ''meta-model'' designates a model that is used to describe other models. Since the database community prefers the term ''schema'' instead of ''model'' (the latter having another interpretation, as in ''relational model''), this proposition translate as follows: the term ''meta-schema'' designates a schema that is used to describe other schemas. | :The term ''meta-model'' designates a model that is used to describe other models. Since the database community prefers the term ''schema'' instead of ''model'' (the latter having another interpretation, as in ''relational model''), this proposition translate as follows: the term ''meta-schema'' designates a schema that is used to describe other schemas. | ||
| Ligne 313 : | Ligne 323 : | ||
*'''Status''': ''partial'' | *'''Status''': ''partial'' | ||
*'''Description''' | *'''Description''' | ||
| − | :An environment to design and generate hybrid databases including an equational model has been implemented in the DB-MAIN CASE tool. Such a database includes derived attributes according to complex | + | :An environment to design and generate hybrid databases including an equational model has been implemented in the DB-MAIN CASE tool. Such a database includes derived attributes according to complex computing rules. |
*'''Keywords''' | *'''Keywords''' | ||
:computing model, equational model, deductive database | :computing model, equational model, deductive database | ||
| Ligne 372 : | Ligne 382 : | ||
| − | [[Accueil|<''Retour à la page d'accueil | + | [[Accueil|<''Back to Welcome page / Retour à la page d'accueil>]] |
<!-- | <!-- | ||
<Back to Welcome page / Retour à la page d'accueil>
This section of the site will present the contribution of the Computer science faculty of the University of Namur to the Database discipline since 1971. In short, an overview of the first 40 years of research in DB engineering! I will leave the development of the next 40 years to my young colleagues.
This work is not a simple task, and I don't expect its completion before at least one or two years
Jean-Luc Hainaut, June 2011
TBA
<Back to Welcome page / Retour à la page d'accueil>