Reverse Engineering User Interfaces for Database Conceptual Analysis

La première étape des méthodologies de conception de base de données consiste à éliciter les besoins à partir, entre-autres, dŠinterviews des utilisateurs. Ces besoins sont formalisés au sein dŠun schéma conceptuel du domaine dŠapplication, typiquement un diagramme Entité-Relation (ER). Le processus de validation de ces besoins demeure pourtant problématique car la représentation visuelle du modèle ER ne permet pas toujours une bonne compréhension par les utilisateurs finaux. En revanche, des prototypes dŠinterfaces utilisateurs peuvent être utilisés comme un moyen plus efficace pour exprimer, capturer et valider des besoins en termes de données. Considérant ces interfaces comme une vue physique de la base de données à concevoir, il est possible d’en dériver le schéma conceptuel sous-jacent en combinant des techniques de rétro-ingénierie, de transformation et d’intégration de schémas. Cet article présente les fondements d’une approche interactive et outillée mettant en oeuvre ces principes.

[1]  Jean-Luc Hainaut,et al.  The Transformational Approach to Database Engineering , 2005, GTTSE.

[2]  Joobin Choobineh,et al.  A form-based approach for database analysis and design , 1992, CACM.

[3]  Fernando Berzal Galiano,et al.  Mining Induced and Embedded Subtrees in Ordered, Unordered, and Partially-Ordered Trees , 2008, ISMIS.

[4]  Shamkant B. Navathe,et al.  Conceptual Database Design: An Entity-Relationship Approach , 1991 .

[5]  William E. Winkler,et al.  String Comparator Metrics and Enhanced Decision Rules in the Fellegi-Sunter Model of Record Linkage. , 1990 .

[6]  Gerhard Fischer,et al.  Beyond "Couch Potatoes": From Consumers to Designers and Active Contributors , 2002, First Monday.

[7]  Kurt Schneider,et al.  Prototypes as assets, not toys. Why and how to extract knowledge from prototypes. (Experience report) , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[8]  James H. Cross,et al.  Reverse engineering and design recovery: a taxonomy , 1990, IEEE Software.

[9]  Pradeep Ravikumar,et al.  A Comparison of String Distance Metrics for Name-Matching Tasks , 2003, IIWeb.

[10]  Daniel M. Berry,et al.  A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains , 2000, Requirements Engineering.

[11]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[12]  Sudha Ram Deriving functional dependencies from the entity-relationship model , 1995, CACM.

[13]  I. Illich Tools for Conviviality , 1973 .

[14]  Hall Chapman,et al.  Software Reuse and Reverse Engineering in Practice , 1992 .

[15]  Vincent Englebert,et al.  Data Conceptualisation for Web-Based Data-Centred Application Design , 2006, CAiSE.

[16]  Simon R. Rollinson,et al.  Formalizing the Informational Content of Database User Interfaces , 1998, ER.

[17]  Jean Vanderdonckt,et al.  USIXML: A User Interface Description Language Supporting Multiple Levels of Independence , 2004, ICWE Workshops.

[18]  Georg Kösters,et al.  Combined analysis of user interface and domain requirements , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[19]  Lois M. L. Delcambre,et al.  Querying through a user interface , 2007, Data Knowl. Eng..

[20]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[21]  Howard J. Hamilton,et al.  Mining functional dependencies from data , 2007, Data Mining and Knowledge Discovery.

[22]  Fabio Paternò,et al.  Design and development of multidevice user interfaces through multiple logical descriptions , 2004, IEEE Transactions on Software Engineering.

[23]  Hassan Gomaa,et al.  Prototyping as a tool in the specification of user requirements , 1981, ICSE '81.

[24]  Stefano Spaccapietra,et al.  Model independent assertions for integration of heterogeneous schemas , 1992, The VLDB Journal.

[25]  Alan M. Davis,et al.  Operational prototyping: a new development approach , 1992, IEEE Software.

[26]  Michael V. Mannino,et al.  Inferring Database Requirements from Examples in Forms , 1988, ER.