Automatic generation of production rules for integrity maintenance
ACM Transactions on Database Systems (TODS)
Database modeling and design (3rd ed.)
Database modeling and design (3rd ed.)
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
An algebraic approach to static analysis of active database rules
ACM Transactions on Database Systems (TODS)
Specifying and implementing the operational use of constraints in object-oriented applications
CRPIT '02 Proceedings of the Fortieth International Conference on Tools Pacific: Objects for internet, mobile and embedded applications
Deriving Production Rules for Constraint Maintainance
VLDB '90 Proceedings of the 16th International Conference on Very Large Data Bases
Transformation Rules for UML Class Diagrams
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
CASE tool evaluation: experiences from an empirical study
Journal of Systems and Software
Using UML/OCL constraints for relational database design
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Constraint support in MDA tools: a survey
ECMDA-FA'06 Proceedings of the Second European conference on Model Driven Architecture: foundations and Applications
Incremental integrity checking of UML/OCL conceptual schemas
Journal of Systems and Software
Hi-index | 0.00 |
Transforming integrity constraints into active rules or triggers for verifying database consistency produces a serious and complex problem related to real time behaviour that must be considered for any implementation. Our main contribution to this work is to provide a complete approach for deriving the active mechanisms for Relational Databases from the specification of the integrity constraints by using OCL. This approach is designed in accordance with the MDA approach which consists of transforming the specified OCL clauses into a class diagram into SQL:2003 standard triggers, then transforming the standard triggers into target DBMS triggers. We believe that developing triggers and plugging them into a given model is insufficient because the behaviour of such triggers is invisible to the developers, and therefore not controllable. For this reason, a DBMS trigger verification model is used in our approach, in order to ensure the termination of trigger execution. Our approach is implemented as an add-in tool in Rational Rose called OCL2Trigger.