Dbm (discuter | contributions) m |
Dbm (discuter | contributions) m |
||
| Ligne 5 : | Ligne 5 : | ||
| − | ::Cette section regroupe et intègre les différentes ressources du LIBD autour de thématiques spécifiques. | + | ::Cette section regroupe et intègre les différentes ressources de la faculté d'informatique et du LIBD en particulier autour de thématiques spécifiques. |
| − | ::This section collects and integrates the resources of the LIBD into specific themes. | + | ::This section collects and integrates the resources of the CS faculty and, more specifically of the LIBD into specific themes. |
| Ligne 15 : | Ligne 15 : | ||
==Introduction== | ==Introduction== | ||
| + | TBA | ||
==Modeling and Metamodeling== | ==Modeling and Metamodeling== | ||
| − | *''' | + | *'''Introduction''' |
| − | :This chapter describes the | + | :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 details 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'''). | ||
| + | :This chapter describes the contribution of the LIBD to the development of database models, database languages and API’s and metamodels. | ||
| + | |||
===Database Models=== | ===Database Models=== | ||
*'''Status''': ''Complete'' | *'''Status''': ''Complete'' | ||
| Ligne 52 : | Ligne 57 : | ||
==Database Methodologies== | ==Database Methodologies== | ||
| − | *''' | + | *'''Introduction''' |
===Method Modeling=== | ===Method Modeling=== | ||
| Ligne 111 : | Ligne 116 : | ||
==Database Reverse Engineering== | ==Database Reverse Engineering== | ||
| − | *''' | + | *'''Introduction''' |
===Methodology and Techniques=== | ===Methodology and Techniques=== | ||
| Ligne 135 : | Ligne 140 : | ||
==Transformational Engineering== | ==Transformational Engineering== | ||
| − | *''' | + | *'''Introduction''' |
===Principles and Methodology=== | ===Principles and Methodology=== | ||
| Ligne 159 : | Ligne 164 : | ||
==Database Evolution and Migration== | ==Database Evolution and Migration== | ||
| − | *''' | + | *'''Introduction''' |
===Database Evolution and Migration=== | ===Database Evolution and Migration=== | ||
| Ligne 176 : | Ligne 181 : | ||
==Data Interoperability== | ==Data Interoperability== | ||
| − | *''' | + | *'''Introduction''' |
===Heterogeneous Data Integration=== | ===Heterogeneous Data Integration=== | ||
| Ligne 193 : | Ligne 198 : | ||
==Special Databases== | ==Special Databases== | ||
| − | *''' | + | *'''Introduction''' |
:Some aspects of information systems require a special treatment, that translates in specific data models and specific design processes. | :Some aspects of information systems require a special treatment, that translates in specific data models and specific design processes. | ||
===Active Databases=== | ===Active Databases=== | ||
| Ligne 221 : | Ligne 226 : | ||
==XML and the web== | ==XML and the web== | ||
| − | *''' | + | *'''Introduction''' |
===XML Structures Modeling and Manipulation=== | ===XML Structures Modeling and Manipulation=== | ||
| Ligne 238 : | Ligne 243 : | ||
==Tools== | ==Tools== | ||
| − | *''' | + | *'''Introduction''' |
===DBMS=== | ===DBMS=== | ||
| Ligne 277 : | Ligne 282 : | ||
==Workflow modeling== | ==Workflow modeling== | ||
| − | *''' | + | *'''Introduction''' |
===Model-base for Clinical Pathways=== | ===Model-base for Clinical Pathways=== | ||
| Ligne 294 : | Ligne 299 : | ||
==Databases and Computing Models== | ==Databases and Computing Models== | ||
| − | *''' | + | *'''Introduction''' |
===Modeling and Methodology=== | ===Modeling and Methodology=== | ||
| Ligne 315 : | Ligne 320 : | ||
==Educational Resources== | ==Educational Resources== | ||
| − | *''' | + | *'''Introduction''' |
===SQL=== | ===SQL=== | ||
<Retour à la page d'accueil / Back>
TBA
<Retour à la page d'accueil / Back>