LIBD:Themes - Historique des versions

Dbm le 4 décembre 2011 à 21:46

2011-12-04T21:46:41Z

Dbm le 30 octobre 2011 à 11:07

2011-10-30T11:07:52Z

Dbm le 5 juillet 2011 à 10:08

2011-07-05T10:08:17Z

Dbm : /* Tools */

2011-03-06T16:07:59Z

Tools

Dbm : /* Metamodeling */

2010-12-14T20:56:14Z

Metamodeling

Dbm : /* Database Models */

2010-12-14T20:50:46Z

Database Models

Dbm : /* Modeling and Metamodeling */

2010-12-14T20:39:25Z

Modeling and Metamodeling

Dbm le 14 décembre 2010 à 09:43

2010-12-14T09:43:03Z

Dbm le 12 décembre 2010 à 19:35

2010-12-12T19:35:20Z

Dbm le 12 décembre 2010 à 12:50

2010-12-12T12:50:15Z

@@ Ligne 17 : / Ligne 17 : @@
 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 (no starting year mentioned)
+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 5 : / Ligne 5 : @@
 ::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).
@@ Ligne 15 : / Ligne 15 : @@
 ==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 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 one or two years.
+This work is not a simple task, and I don't expect its completion before at least one or two years (no starting year mentioned)
 Jean-Luc Hainaut, June 2011

@@ Ligne 1 : / Ligne 1 : @@
-<center><big><b>Pages en cours de développement/ Pages in development</b></big></center>
+<center><big><b>Pages in development / Pages en cours de développement</b></big></center>
-<center><big><big><big><b>Thèmes et ressources/ Themes and resources</b></big></big></big></center>
+<center><big><big><big><b>Themes and resources/ Thèmes et ressources</b></big></big></big></center>
-::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 Computer science faculty and, more specifically of the DB research group, into themes related to Database Engineering (and some others).
-::This section collects and integrates the resources of the CS faculty and, more specifically of the LIBD into specific themes.
+::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 / Back''>]]
+[[Accueil|<''Back to Welcome page / Retour à la page d'accueil>]]
@@ Ligne 16 : / Ligne 25 : @@
 TBA
 ==Modeling and Metamodeling==
@@ Ligne 372 : / Ligne 382 : @@
-[[Accueil|<''Retour à la page d'accueil / Back''>]]
+[[Accueil|<''Back to Welcome page / Retour à la page d'accueil>]]
 <!--

@@ Ligne 313 : / Ligne 313 : @@
 *'''Status''': ''partial''
 *'''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 comptuting rules.
+: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'''
 :computing model, equational model, deductive database

@@ Ligne 48 : / Ligne 48 : @@
 *'''Status''': ''complete''
 *'''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 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 32 : / Ligne 32 : @@
 *'''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>]]''

@@ Ligne 20 : / Ligne 20 : @@
 *'''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''').
-: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''').
+: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''').
 :This chapter describes the contribution of the LIBD to the development of database models, database languages and API’s and metamodels.

@@ 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==
 ==Modeling and Metamodeling==
-*'''Description'''
+*'''Introduction'''
-:This chapter describes the contributions of the LIBD to the development of database models, database languages and metamodels.
+: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 Models===
 *'''Status''': ''Complete''
@@ Ligne 52 : / Ligne 57 : @@
 ==Database Methodologies==
-*'''Description'''
+*'''Introduction'''
 ===Method Modeling===
@@ Ligne 111 : / Ligne 116 : @@
 ==Database Reverse Engineering==
-*'''Description'''
+*'''Introduction'''
 ===Methodology and Techniques===
@@ Ligne 135 : / Ligne 140 : @@
 ==Transformational Engineering==
-*'''Description'''
+*'''Introduction'''
 ===Principles and Methodology===
@@ Ligne 159 : / Ligne 164 : @@
 ==Database Evolution and Migration==
-*'''Description'''
+*'''Introduction'''
 ===Database Evolution and Migration===
@@ Ligne 176 : / Ligne 181 : @@
 ==Data Interoperability==
-*'''Description'''
+*'''Introduction'''
 ===Heterogeneous Data Integration===
@@ Ligne 193 : / Ligne 198 : @@
 ==Special Databases==
-*'''Description'''
+*'''Introduction'''
 :Some aspects of information systems require a special treatment, that translates in specific data models and specific design processes.
 ===Active Databases===
@@ Ligne 221 : / Ligne 226 : @@
 ==XML and the web==
-*'''Description'''
+*'''Introduction'''
 ===XML Structures Modeling and Manipulation===
@@ Ligne 238 : / Ligne 243 : @@
 ==Tools==
-*'''Description'''
+*'''Introduction'''
 ===DBMS===
@@ Ligne 277 : / Ligne 282 : @@
 ==Workflow modeling==
-*'''Description'''
+*'''Introduction'''
 ===Model-base for Clinical Pathways===
@@ Ligne 294 : / Ligne 299 : @@
 ==Databases and Computing Models==
-*'''Description'''
+*'''Introduction'''
 ===Modeling and Methodology===
@@ Ligne 315 : / Ligne 320 : @@
 ==Educational Resources==
-*'''Description'''
+*'''Introduction'''
 ===SQL===

@@ Ligne 27 : / Ligne 27 : @@
 *'''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, 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>]]''
@@ Ligne 33 : / Ligne 33 : @@
 ===Database Languages and API===
 *'''Status''': ''Partial''
-*'''Description''':
+*'''Description'''
 *'''Keywords'''
-:new database languages, CASE programming, SQL script, dynamic SQL, temporal API, wrappers
+:database languages, CASE programming, Voyager 2, DB-MAIN, SQL script, dynamic SQL, temporal API, wrapper, wrapper generator
 :''[[LIBD:Themes:Database-Languages-and-API|<Go to the <b>Database Languages and API</b> page for more detail>]]''