LIBD - Contributions de l’utilisateur [fr]

LIBD:THESES

2010-10-19T12:55:21Z

Rra : /* Reverse Engineering User-Drawn Form-based Interfaces for Interactive Database Conceptual Analysis */

<center><big>Page en développement</big></center>

<center><big><big>Theses / Thèses</big></big></center>

[[LIBD:Publications|<''Retour à la page des publications / Back''>]]

===''Reverse Engineering User-Drawn Form-based Interfaces for Interactive Database Conceptual Analysis''===

:'''Author''': Ravi Ramdoyal

:'''Date''': 2010

:'''Abstract'''

:The first step of most database design methodologies consists in eliciting part of the user requirements from various sources such as user interviews and corporate documents. These requirements are formalised into a conceptual schema of the application domain, that has proved difficult to validate, especially since the graphical representations of data models have shown understandability limitations from the end-users standpoint. On the other hand, electronic forms seem to be more natural and intuitive to express data requirements for laymen. Besides, the necessity to associate end-users of a future system with its specification and development steps has long been advocated.
:In this doctoral research, we consequently explore the possible reverse engineering of user-drawn form-based interfaces to perform an interactive database conceptual analysis, and subsequently present the tool-supported RAINBOW approach resulting from this investigation. This user-oriented approach relies on the adaptation and integration of principles and techniques coming from various fields of study, ranging from Database Forward and Reverse Engineering to Prototyping and Participatory Design.

:[ [full text]]

===''Program Analysis and Transformation for Data-Intensive System Evolution''===

:'''Author''': Anthony Cleve

:'''Date''': 2009

:'''Abstract'''
:Data-intensive software systems are generally made of a database (sometimes in the form of a set of files) and a collection of application programs in strong interaction with the former. They constitute critical assets in most enterprises, since they support business activities in all production and management domains. Data-intensive systems form most of the so-called legacy systems: they typically are one or more decade old, they are very large, heterogeneous and highly complex. Many of them significantly resist modifications and change due to the lack of documentation, to the use of aging technologies and to inflexible architectures. Therefore, the evolution of data-intensive systems clearly calls for automated support. This thesis particularly explores the use of automated program analysis and transformation techniques in support to the evolution of the database component of the system. The program analysis techniques aim to ease the database evolution process, by helping the developers to understand the data structures that are to be changed, despite the lack of precise and up-to-date documentation. The objective of the program transformation techniques is to support the adaptation of the application programs to the new database. This adaptation process is studied in the context of two realistic database evolution scenarios, namely database platform migration and database schema refactoring.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Anthony-Cleve-Thesis.pdf [full text]]

===''Legacy database federation. A combined forward-Reverse approach''===

:'''Author''': Philippe Thiran

:'''Date''': 2003

:'''Abstract'''
:Most large organizations maintain their data in many distinct independent databases that have been developed at different times on different platforms and DMS (Data Management Systems). The new economic challenges force enterprises to integrate their functions and therefore their information systems including the databases they are based on. In most cases, these databases cannot be replaced with a unique system, nor even reengineered due to the high financial and organizational costs of such restructuring. Hence the need for interoperation frameworks that allow the databases to be accessed by users and application programs as if they were a unique homogeneous and consistent database, through an architecture called federated databases. We refer to software services allowing such so-called legacy database systems to cooperate, as providing interoperability. Such services provide users and application programs with an integrated view of data dispersed over various component databases. In this thesis, we focus on the interoperability of legacy and heterogeneous databases. We introduce the thesis by first giving the main issues about interoperability. Next, a short overview of the interoperability research is presented. We then develop a small example that illustrates some of the problems we intend to address. Finally, we present the purpose and the topic of the thesis.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Philippe-Thiran-Thesis.pdf [full text]]

===''Program comprehension in database reverse engineering''===

:'''Author''': Jean Henrard

:'''Date''': 2003

:'''Abstract'''
:For many years software engineering has primarily focused on the development of new systems and neglected maintenance and reengineering of legacy applications. Maintenance typically represents 70% of the cost during the life cycle of a system. In order to allow an efficient and safe maintenance of a legacy system, we need to reverse engineer it in order to reconstruct its missing or out-of-date documentation. In data-oriented applications the reverse engineering complexity can be broken down by considering that the database can be reverse engineered independently of the procedural components. Database reverse engineering can be defined as the process of recovering the database's schema(s) of an application from database declaration text and program source code that use the data in order to understand their exact structure and meaning. A database reverse engineering methodology is broken down into three processes: project preparation, data structure extraction that recovers the database's logical schema and data structure conceptualization that interprets the logical schema in conceptual terms. In order to validate our methodology and program understanding techniques, we have developed tools to support them. Those tools have proved absolutely necessary to perform database reverse engineering of medium to larger applications in reasonable time and at reasonable cost. To cut down on the cost of large projects, we have stressed the need for automation to reduce the manual work of the analyst. Our experience with real size projects has taught us that the management aspects of a project are essential success factors. The management of a project comprises different aspects such as database reverse engineering explanation, cost evaluation and database reverse engineering result evaluation.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Jean-Henrard-Thesis.pdf [full text]]

===''Database engineering process modelling''===

:'''Author''': Didier Roland

:'''Date''': 2002

:'''Abstract'''
:An important research subject in Software engineering is concerned with modelling the development process of huge software in order to bring some help to engineers when designing and maintaining an application. In general, every design process is seen a rational application of transformation operators to one or more products (mainly specifications) in order to produce new products that satisfy some given criteria: O=f(I). I and O being sets of products compliant with formalisable models, f is a transformation composition whose specifications are the properties of I and O. This modelling is a sound basis for a methodological guidance. Indeed, at each step of the process, the set of pertinent activities and types of products are proposed to the designer, without any other.
:This guidance can be reinforced with some help. Furthermore, this modelling allows to document the process with its history, i.e. with a representation of performed activities. This history is itself the basis of maintenance activities.
:The thesis holds in four phases:
:*elaboration of a general model of design processes, a method specification language (MDL), and a history representation
:*basic methodological recommendation proposals for the elaboration of engineering methods according to the defined model
:*development and integration of some methodological control functions in the DB-MAIN CASE tool, including an extension of the repository, the definition of the interface of the methodological functions, the development of the methodological engine and the development of history processors (recording, replay, analysis,...)
:*evaluation of this model with case studies using classical methods.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Didier-Roland-Thesis.pdf [full text]]

===''Evolution of relational databases applications'' (in French)===

:'''Author''': Jean-Marc Hick

:'''Date''': 2001

:'''Abstract'''
:If the recent DBMS technologies consider the problem of databases schema evolution, standard Information Systems in use raise hard problems when evolution is concerned. This work studies these problems in the current developer context. It gives a complete typology of modifications and analyses the evolution of systems and its impact on the data structures, data and programs through typical strategies.
:The document introduces the DB-Main CASE environment, with which an evolution tool prototype has been developed. This tool can automatically generate the conversion programs for the database from the operational trace of the conceptual and logical schema modifications. It can also help the programmer to modify the application programs.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Jean-Marc-Hick-Thesis.pdf [full text]]

===''A smart meta-CASE: towards an integrated solution''===

:'''Author''': Vincent Englebert

:'''Date''': 2000

:'''Abstract'''
:For twenty years now, software engineers use CASE (Computer Aided Software Engineering) tools to design systems, to verify specifications, to generate programs, \dots Unfortunately, their use is not as widespread as one could expect it. They are often both too limited and too coercive. But because computer projects become larger and more complex every year, such tools are now essential to ensure the correctness, the schedules, and the documentation of programs. For these reasons, researchers have proposed complementary (or alternative) approaches with meta-CASE tools. The latter are flexible frameworks that allow engineers to customize, to extend them, or even to define brand-new CASE tools in a dynamic way.
:This thesis presents the results of a study about the implementation of a new meta-CASE. This research starts from a dozen case studies in this realm to draw up an assessment of the requirements that future meta-CASE tools should meet. This work has examined a subset of them to propose an integration of meta-modelling techniques that are generally both simpler and more expressive than the former approaches.
:We have investigated the requirements about three major components that make up meta-CASEs: the repository, the representation of the information stored in this repository, and the processes that animate it. Our work has been guided by two key ideas: simplicity and expressivity. Although they are generally seen as contradictory requirements, we prove that it is possible to bring them together. Indeed, (1) we have defined a repository with a very limited number of concepts coming from the object-oriented paradigm and we have demonstrated that complex methods can be represented with; (2) a graphical symbolic language allows method engineers to define advanced representations of these methods; and finally (3) a new programming language has provided the repository with an operational intelligence. Moreover, this architecture has been endowed with a mirroring service that blurs the distinction between the the meta-CASE (i.e., the meta-model level) and the CASE tools it describes (i.e., the specification level). This service made it possible to bootstrap some other major components of the meta-CASE (A meta-model editor, a Grasyla script editor, meta-extensions of Voyager 2).

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Vincent-Englebert-Thesis.pdf [full text]]

LIBD:THESES

2010-10-19T12:54:35Z

Rra : /* Reverse Engineering User-Drawn Form-based Interfaces for Interactive Database Conceptual Analysis */

<center><big>Page en développement</big></center>

<center><big><big>Theses / Thèses</big></big></center>

[[LIBD:Publications|<''Retour à la page des publications / Back''>]]

===''Reverse Engineering User-Drawn Form-based Interfaces for Interactive Database Conceptual Analysis''===

:'''Author''': Ravi Ramdoyal

:'''Date''': 2010

:'''Abstract'''

The first step of most database design methodologies consists in eliciting part of the user requirements from various sources such as user interviews and corporate documents. These requirements are formalised into a conceptual schema of the application domain, that has proved difficult to validate, especially since the graphical representations of data models have shown understandability limitations from the end-users standpoint. On the other hand, electronic forms seem to be more natural and intuitive to express data requirements for laymen. Besides, the necessity to associate end-users of a future system with its specification and development steps has long been advocated.

In this doctoral research, we consequently explore the possible reverse engineering of user-drawn form-based interfaces to perform an interactive database conceptual analysis, and subsequently present the tool-supported RAINBOW approach resulting from this investigation. This user-oriented approach relies on the adaptation and integration of principles and techniques coming from various fields of study, ranging from Database Forward and Reverse Engineering to Prototyping and Participatory Design.

:[ [full text]]

===''Program Analysis and Transformation for Data-Intensive System Evolution''===

:'''Author''': Anthony Cleve

:'''Date''': 2009

:'''Abstract'''
:Data-intensive software systems are generally made of a database (sometimes in the form of a set of files) and a collection of application programs in strong interaction with the former. They constitute critical assets in most enterprises, since they support business activities in all production and management domains. Data-intensive systems form most of the so-called legacy systems: they typically are one or more decade old, they are very large, heterogeneous and highly complex. Many of them significantly resist modifications and change due to the lack of documentation, to the use of aging technologies and to inflexible architectures. Therefore, the evolution of data-intensive systems clearly calls for automated support. This thesis particularly explores the use of automated program analysis and transformation techniques in support to the evolution of the database component of the system. The program analysis techniques aim to ease the database evolution process, by helping the developers to understand the data structures that are to be changed, despite the lack of precise and up-to-date documentation. The objective of the program transformation techniques is to support the adaptation of the application programs to the new database. This adaptation process is studied in the context of two realistic database evolution scenarios, namely database platform migration and database schema refactoring.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Anthony-Cleve-Thesis.pdf [full text]]

===''Legacy database federation. A combined forward-Reverse approach''===

:'''Author''': Philippe Thiran

:'''Date''': 2003

:'''Abstract'''
:Most large organizations maintain their data in many distinct independent databases that have been developed at different times on different platforms and DMS (Data Management Systems). The new economic challenges force enterprises to integrate their functions and therefore their information systems including the databases they are based on. In most cases, these databases cannot be replaced with a unique system, nor even reengineered due to the high financial and organizational costs of such restructuring. Hence the need for interoperation frameworks that allow the databases to be accessed by users and application programs as if they were a unique homogeneous and consistent database, through an architecture called federated databases. We refer to software services allowing such so-called legacy database systems to cooperate, as providing interoperability. Such services provide users and application programs with an integrated view of data dispersed over various component databases. In this thesis, we focus on the interoperability of legacy and heterogeneous databases. We introduce the thesis by first giving the main issues about interoperability. Next, a short overview of the interoperability research is presented. We then develop a small example that illustrates some of the problems we intend to address. Finally, we present the purpose and the topic of the thesis.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Philippe-Thiran-Thesis.pdf [full text]]

===''Program comprehension in database reverse engineering''===

:'''Author''': Jean Henrard

:'''Date''': 2003

:'''Abstract'''
:For many years software engineering has primarily focused on the development of new systems and neglected maintenance and reengineering of legacy applications. Maintenance typically represents 70% of the cost during the life cycle of a system. In order to allow an efficient and safe maintenance of a legacy system, we need to reverse engineer it in order to reconstruct its missing or out-of-date documentation. In data-oriented applications the reverse engineering complexity can be broken down by considering that the database can be reverse engineered independently of the procedural components. Database reverse engineering can be defined as the process of recovering the database's schema(s) of an application from database declaration text and program source code that use the data in order to understand their exact structure and meaning. A database reverse engineering methodology is broken down into three processes: project preparation, data structure extraction that recovers the database's logical schema and data structure conceptualization that interprets the logical schema in conceptual terms. In order to validate our methodology and program understanding techniques, we have developed tools to support them. Those tools have proved absolutely necessary to perform database reverse engineering of medium to larger applications in reasonable time and at reasonable cost. To cut down on the cost of large projects, we have stressed the need for automation to reduce the manual work of the analyst. Our experience with real size projects has taught us that the management aspects of a project are essential success factors. The management of a project comprises different aspects such as database reverse engineering explanation, cost evaluation and database reverse engineering result evaluation.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Jean-Henrard-Thesis.pdf [full text]]

===''Database engineering process modelling''===

:'''Author''': Didier Roland

:'''Date''': 2002

:'''Abstract'''
:An important research subject in Software engineering is concerned with modelling the development process of huge software in order to bring some help to engineers when designing and maintaining an application. In general, every design process is seen a rational application of transformation operators to one or more products (mainly specifications) in order to produce new products that satisfy some given criteria: O=f(I). I and O being sets of products compliant with formalisable models, f is a transformation composition whose specifications are the properties of I and O. This modelling is a sound basis for a methodological guidance. Indeed, at each step of the process, the set of pertinent activities and types of products are proposed to the designer, without any other.
:This guidance can be reinforced with some help. Furthermore, this modelling allows to document the process with its history, i.e. with a representation of performed activities. This history is itself the basis of maintenance activities.
:The thesis holds in four phases:
:*elaboration of a general model of design processes, a method specification language (MDL), and a history representation
:*basic methodological recommendation proposals for the elaboration of engineering methods according to the defined model
:*development and integration of some methodological control functions in the DB-MAIN CASE tool, including an extension of the repository, the definition of the interface of the methodological functions, the development of the methodological engine and the development of history processors (recording, replay, analysis,...)
:*evaluation of this model with case studies using classical methods.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Didier-Roland-Thesis.pdf [full text]]

===''Evolution of relational databases applications'' (in French)===

:'''Author''': Jean-Marc Hick

:'''Date''': 2001

:'''Abstract'''
:If the recent DBMS technologies consider the problem of databases schema evolution, standard Information Systems in use raise hard problems when evolution is concerned. This work studies these problems in the current developer context. It gives a complete typology of modifications and analyses the evolution of systems and its impact on the data structures, data and programs through typical strategies.
:The document introduces the DB-Main CASE environment, with which an evolution tool prototype has been developed. This tool can automatically generate the conversion programs for the database from the operational trace of the conceptual and logical schema modifications. It can also help the programmer to modify the application programs.

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Jean-Marc-Hick-Thesis.pdf [full text]]

===''A smart meta-CASE: towards an integrated solution''===

:'''Author''': Vincent Englebert

:'''Date''': 2000

:'''Abstract'''
:For twenty years now, software engineers use CASE (Computer Aided Software Engineering) tools to design systems, to verify specifications, to generate programs, \dots Unfortunately, their use is not as widespread as one could expect it. They are often both too limited and too coercive. But because computer projects become larger and more complex every year, such tools are now essential to ensure the correctness, the schedules, and the documentation of programs. For these reasons, researchers have proposed complementary (or alternative) approaches with meta-CASE tools. The latter are flexible frameworks that allow engineers to customize, to extend them, or even to define brand-new CASE tools in a dynamic way.
:This thesis presents the results of a study about the implementation of a new meta-CASE. This research starts from a dozen case studies in this realm to draw up an assessment of the requirements that future meta-CASE tools should meet. This work has examined a subset of them to propose an integration of meta-modelling techniques that are generally both simpler and more expressive than the former approaches.
:We have investigated the requirements about three major components that make up meta-CASEs: the repository, the representation of the information stored in this repository, and the processes that animate it. Our work has been guided by two key ideas: simplicity and expressivity. Although they are generally seen as contradictory requirements, we prove that it is possible to bring them together. Indeed, (1) we have defined a repository with a very limited number of concepts coming from the object-oriented paradigm and we have demonstrated that complex methods can be represented with; (2) a graphical symbolic language allows method engineers to define advanced representations of these methods; and finally (3) a new programming language has provided the repository with an operational intelligence. Moreover, this architecture has been endowed with a mirroring service that blurs the distinction between the the meta-CASE (i.e., the meta-model level) and the CASE tools it describes (i.e., the specification level). This service made it possible to bootstrap some other major components of the meta-CASE (A meta-model editor, a Grasyla script editor, meta-extensions of Voyager 2).

:[http://www.info.fundp.ac.be/~dbm/Documents/Theses/Vincent-Englebert-Thesis.pdf [full text]]

DUNOD2009 Cours complet

2009-05-04T07:58:46Z

Rra :

'''PROGRAMME DE COURS COMPLET'''

Ce second parcours couvre de manière détaillée un ensemble raisonnablement complet de connaissances nécessaires à la compréhension, à l'utilisation et au développement de bases de données relationnelles et relationnelles objet. Il est destiné plus particulièrement à l'étudiant en informatique et au professionnel des bases de données, qu'il soit analyste, programmeur ou administrateur de bases de données. Il intéressera également le lecteur du parcours introductif désireux d'approfondir l'un ou l'autre point tel que la normalisation, les SGBD, le modèle Entité-association, UML, la rétro-ingénierie ou les outils de conception de bases de données.

Les annexes apportent des compléments techniques, théoriques ou applicatifs.

[[DUNOD2009|<Retour à la page de l'ouvrage>]]

A l'exception des annexes, les documents de support du cours se présentent sous la forme de diaporamas en Powerpoint 97. Les supports des chapitres 14, 15, 17, 18, 19 et 21 sont rédigés de manière autonome, de sorte qu'il n'est pas nécessaire d'utiliser au préalable leurs versions simplifiées des chapitres 10, 11, 12 et 13. Les documents actuellement manquants seront disponibles en septembre 2009.

{| border="1"
| colspan="3" | <center>'''LES CONCEPTS DES BASES DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Concepts des bases de données
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-02/Concepts-des-BD-(Concepts).ppt Concepts-des-BD-(Concepts).ppt]
| Chapitre 2
|-
| Modèle relationnel et normalisation
| Concepts-des-BD-(Modele-relationnel).ppt
| Chapitre 3
|-
| Implémentation des structures de données
| Concepts-des-BD-(Implementation).ppt
| Chapitre 4
|-
| Les systèmes de gestion de bases de données
| Concepts-des-BD-(SGBD).ppt
| Chapitre 5
|-
| colspan="3" | <center>'''L'UTILISATION DES BASES DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Le langage SQL DDL
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-06/Utilisation-des-BD-(SQL-DDL).ppt Utilisation-des-BD-(SQL-DDL).ppt]
| Chapitre 6
|-
| Le langage SQL DML (1)
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-07/Utilisation-des-BD-(SQL-DML-1).ppt Utilisation-des-BD-(SQL-DML-1).ppt]
| Chapitre 7
|-
| Le langage SQL DML (2)
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-08/Utilisation-des-BD-(SQL-DML-2).ppt Utilisation-des-BD-(SQL-DML-2).ppt]
| Chapitre 8
|-
| Le langage SQL avancé
| Utilisation-des-BD-(SQL-avance).ppt
| Chapitre 9
|-
| colspan="3" | <center>'''LE DEVELOPPEMENT D'UNE BASE DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Methodologie des bases de données
| Methodologie-des-BD-(Methodologie).ppt
| Chapitre 14
|-
| Le modèle Entité-association étendu
| Methodologie-des-BD-(Modele-EA-etendu).ppt
| Chapitre 15
|-
| Analyse conceptuelle du domaine d'application
| Methodologie-des-BD-(Analyse-conceptuelle).ppt
| Chapitre 17
|-
| Conception logique d'une BD relationnelle
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-18/Methodologie-des-BD-(Conception-logique-relat).ppt Methodologie-des-BD-(Conception-logique-relat).ppt]
| Chapitre 18
|-
| Conception logique d'une BD relationnelle objet
| Methodologie-des-BD-(Conception-logique-rel-objet).ppt
| Chapitre 19
|-
| Conception physique d'une BD relationnelle
| Methodologie-des-BD-(Conception-physique).ppt
| Chapitre 20
|-
| Production du code d'une BD
| Methodologie-des-BD-(Production-code-BD).ppt
| Chapitre 21
|-
| Etudes de cas
|
| Chapitre 23
|-
| colspan="3" | <center>'''COMPLEMENTS FACULTATIFS'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Les diagrammes de classes UML
| Methodologie-des-BD-(UML).ppt
| Chapitre 16
|-
| Rétro-ingénierie d'une base de données
| Methodologie-des-BD-(Retro-ingenierie-BD).ppt
| Chapitre 22
|-
| Exercices additionnels
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-01/JLH-A-Exercices-resolus.pdf JLH-A-Exercices-resolus.pdf]
| Annexe A
|-
| Applications avancées des bases de données
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-01/JLH-C-Applications-avancees.pdf JLH-C-Applications-avancees.pdf]
| Annexe C
|-
| Conventions graphiques
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-01/JLH-D-Graphique-ER.pdf JLH-D-Graphique-ER.pdf]
| Annexe D
|-
| Transformations de schémas
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-01/JLH-E-Transfos.pdf JLH-E-Transfos.pdf]
| Annexe E
|-
| Etudes de cas
| JLH-D-Etudes-de-cas.pdf
| Annexe F
|}

DUNOD2009 Cours introductif

2009-05-04T07:56:50Z

Rra :

'''PROGRAMME DE COURS INTRODUCTIF'''

Ce premier parcours est proposé au lecteur débutant, désireux d'aborder l'essentiel des concepts des bases de données, du langage SQL et des méthodes de construction d'une base de données sans toutefois rentrer dans trop de détails. Au terme de ce parcours, le lecteur sera à même de comprendre les enjeux, les problèmes et les solutions propres au domaine des bases de données. Sur le plan pratique, il sera capable d'interroger une base de données de complexité moyenne à l'aide du langage SQL. Il aura enfin suffisamment d'assurance pour construire de manière systématique et raisonnée de petites bases de données de faible complexité.

[[DUNOD2009|<Retour à la page de l'ouvrage>]]

A l'exception des annexes, les documents de support du cours se présentent sous la forme de diaporamas en Powerpoint 97. Les documents manquants seront disponibles en septembre 2009.

{| border="1"
| colspan="3" | <center>'''LES CONCEPTS DES BASES DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Motivation et introduction
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-01/Concepts-des-BD-(Introduction).ppt Concepts-des-BD-(Introduction).ppt]
| Chapitre 1
|-
| Concepts des bases de données
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-02/Concepts-des-BD-(Concepts).ppt Concepts-des-BD-(Concepts).ppt]
| Chapitre 2
|-
| colspan="3" | <center>'''L'UTILISATION DES BASES DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Le langage SQL DDL
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-06/Utilisation-des-BD-(SQL-DDL).ppt Utilisation-des-BD-(SQL-DDL).ppt]
| Chapitre 6
|-
| Le langage SQL DML (1)
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-07/Utilisation-des-BD-(SQL-DML-1).ppt Utilisation-des-BD-(SQL-DML-1).ppt]
| Chapitre 7
|-
| Le langage SQL DML (2)
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Chapitres/Chapitre-08/Utilisation-des-BD-(SQL-DML-2).ppt Utilisation-des-BD-(SQL-DML-2).ppt]
| Chapitre 8
|-
| colspan="3" | <center>'''LE DEVELOPPEMENT D'UNE BASE DE DONNEES'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Construction d'une BD
| Developpement-BD-(Introduction).ppt
| Chapitre 10
|-
| Le modèle Entité-association de base
| Developpement-BD-(Modele-EA-de-base).ppt
| Chapitre 11
|-
| Elaboration d'un schéma conceptuel
| Developpement-BD-(Elaboration-schema-conceptuel).ppt
| Chapitre 12
|-
| Production du schéma de la BD
| Developpement-BD-(Production-schema-BD).ppt
| Chapitre 13
|-
| Etudes de cas
|
| Chapitre 23 (Cas 23.2)
|-
| colspan="3" | <center>'''COMPLEMENTS FACULTATIFS'''</center>
|-
| bgcolor="#00FF00" | Thématique
| bgcolor="#00FF00" | Support de cours
| bgcolor="#00FF00" | Chapitre de l'ouvrage
|-
| Exercices additionnels
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Annexes/Annexe-A/JLH-A-Exercices-resolus.pdf JLH-A-Exercices-resolus.pdf]
| Annexe A
|-
| Mise à niveau
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Annexes/Annexe-B/JLH-B-Ensembles-et-Logique.pdf JLH-B-Ensembles-et-Logique.pdf]
| Annexe B
|-
| Conventions graphiques
| [http://www.info.fundp.ac.be/~dbm/Documents/Ouvrages/Dunod-2009/Annexes/Annexe-D/JLH-D-Graphique-ER.pdf JLH-D-Graphique-ER.pdf]
| Annexe D
|}

MediaWiki:Sidebar

2009-04-08T09:42:03Z

Rra :