Constraints checking in UML class diagrams: SQL vs OCL

  • Authors:
  • D. Berrabah;F. Boufarès

  • Affiliations:
  • LIPN, Paris13 University, Villetaneuse, France;LIPN, Paris13 University, Villetaneuse, France

  • Venue:
  • DEXA'07 Proceedings of the 18th international conference on Database and Expert Systems Applications
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

Numerous CASE tools are used for applications analysis and design. These tools often do not take into account all the information (structures and constraints) given in a conceptual level. So, the elements obtained at the physiccal level do not completely coincide with the conceptual elements. Consequently, some semantics are lost. Our goal, in this paper, is to give rules to translate some constraints not taken into account in the processes used to translate the conceptual schema. In object databases, these constraints are expressed in OCL while they are expressed, in relational databases, using active mechanisms. Consequently, these constraints are checked during databases updates.