MDD Approach for Maintaining Integrity Constraints in Databases

2009 ◽  
pp. 145-153
Author(s):  
Harith T. Al-Jumaily ◽  
Dolores Cuadra ◽  
Paloma Martínez
Keyword(s):  
Life Cycle ◽  
Database Systems ◽  
Complex Problem ◽  
Integrity Constraints ◽  
Cardinality Constraint ◽  
Conceptual Schema ◽  
Database Development ◽  
Model Driven ◽  
Graphical Interfaces ◽  
The Universe

In the context of database, we believe that MDD (Model-Driven Development) (OMG, 2006) is a very ambitious task because we find that when applying database development methodologies such as (Elmasri, et al., 2007), there are processes devoted to transforming conceptual into logical schemata. In such processes, semantic losses are produced since logical elements are not coincident with conceptual elements. A correct constraints transformation is necessary to preserve the semantics that reflects the Universe of Discourse. The multiplicity constraint, also called cardinality constraint, is one of these constraints that can be established in a conceptual schema. It has dynamic aspects that are transformed into the logical model as certain conditions to verify the insertion, deletion, and update operations. The verification of these constraints is a serious and complex problem because currently database systems are not able to preserve the multiplicity constraints of their objects. To solve the modeling problem, CASE tools have been introduced to automate the life cycle of database development. These platforms try to help the database developers in different design phases. Nevertheless, these tools are frequently simple graphical interfaces and do not completely carryout the design methodology that they are should to support.

Methodical Spatial Database Design with Topological Polygon Structures

2013 ◽  
pp. 295-304 ◽  
Author(s):  
Jean Damascène Mazimpaka
Keyword(s):  
Design Process ◽  
Spatial Data ◽  
Spatial Databases ◽  
Early Stage ◽  
Spatial Database ◽  
Database Design ◽  
Integrity Constraints ◽  
Data Infrastructure ◽  
Database Development ◽  
Model Driven

Spatial databases form the foundation for a Spatial Data Infrastructure (SDI). For this, a spatial database should be methodically developed to accommodate its role in SDI. It is desirable to have an approach to spatial database development that considers maintenance from the early stage of database design and in a flexible way. Moreover, there is a lack of a mechanism to capture topological relations of spatial objects during the design process. This paper presents an approach that integrates maintenance of topological integrity constraints into the whole spatial database development cycle. The approach is based on the concept of Abstract Data Types. A number of topological classes have been identified and modelling primitives developed for them. Topological integrity constraints are embedded into maintenance functions associated with the topological classes. A semi-automatic transformation process has been developed following the principles of Model Driven Architecture to simplify the design process.

Model Driven Integration of Heterogeneous Software Artifacts in Service Oriented Computing

2015 ◽  
pp. 825-854
Author(s):  
Eric Simon ◽  
Jacky Estublier
Keyword(s):  
Life Cycle ◽  
Complex Problem ◽  
Third Parties ◽  
Model Driven ◽  
Software Artifacts ◽  
Service Oriented Computing ◽  
Service Oriented ◽  
Integration Mechanisms ◽  
Execution Environment ◽  
Oriented Approach

Systems evolutivity requires complex operations on services, including migration, duplication, updating, and a number of administration-related actions. However, current environments are heterogeneous and require integration to manage services. It is a complex problem, because it implies a transformation of life cycle related concepts. This integration does not fit very well in the service-oriented approach: indeed this approach is consumer-centered and considers that services are hosted by third parties, while administration is a provider view. Therefore, there is a gap between technologies used to compose applications and technologies that provide them. In the context of system adaptability, this gap becomes a major challenge to be solved. The authors propose an execution environment, which provides a homogeneous service representation used to integrate: their functionalities, their life-cycle and management operations, and lifecycle related concerns, like deployment. Their approach includes two integration mechanisms: the technologies integration supported by wrappers and concerns integration supported by the run-times.

Model Driven Integration of Heterogeneous Software Artifacts in Service Oriented Computing

2012 ◽  
pp. 332-360
Author(s):  
Eric Simon ◽  
Jacky Estublier
Keyword(s):  
Life Cycle ◽  
Complex Problem ◽  
Third Parties ◽  
Model Driven ◽  
Software Artifacts ◽  
Service Oriented Computing ◽  
Service Oriented ◽  
Integration Mechanisms ◽  
Execution Environment ◽  
Oriented Approach

Systems evolutivity requires complex operations on services, including migration, duplication, updating, and a number of administration-related actions. However, current environments are heterogeneous and require integration to manage services. It is a complex problem, because it implies a transformation of life cycle related concepts. This integration does not fit very well in the service-oriented approach: indeed this approach is consumer-centered and considers that services are hosted by third parties, while administration is a provider view. Therefore, there is a gap between technologies used to compose applications and technologies that provide them. In the context of system adaptability, this gap becomes a major challenge to be solved. The authors propose an execution environment, which provides a homogeneous service representation used to integrate: their functionalities, their life-cycle and management operations, and lifecycle related concerns, like deployment. Their approach includes two integration mechanisms: the technologies integration supported by wrappers and concerns integration supported by the run-times.

CODAR

2003 ◽  
pp. 266-297
Author(s):  
Zahir Tari ◽  
Abdelkamel Tari ◽  
Surya Setiawan
Keyword(s):  
Business Processes ◽  
Database Systems ◽  
Complex Problem ◽  
Heterogeneous Databases ◽  
Business Organizations ◽  
Data Repositories ◽  
Web Based ◽  
Business Applications ◽  
Core Elements ◽  
New Generation

Connecting heterogeneous databases through the World Wide Web (WWW) is crucial for most business organizations. The underlying complex problem is the handling of heterogeneity and communication between different data repositories (or database systems). Such interoperability is crucial as it enables the integration of business processes across different business organizations, and therefore becomes a key issue within the new generation of Web-based business applications (called Web Services). CORBA (Common Object Request Broker Architecture) provides protocols and components that allow interoperability between different software platforms (Tari & Bukhres, 2001), such as C++ and Java. However, CORBA does not deal with WWW-based interoperability. In this paper we propose an extension of one of the core elements of CORBA, called Portable Object Adapter (POA), to deal with persistency of business information. The proposed extension, called CODAR, manages the whole life cycle of persistent objects, including activation, deactivation, instantiation, and deletion. At the end of this paper we describe an extension of CODAR to deal with performance by including advanced caching and prefetching techniques.

Automate Model Transformation From CIM to PIM up to PSM in Model-Driven Architecture

2020 ◽  
pp. 262-283
Author(s):  
Yassine Rhazali ◽  
Asma El Hachimi ◽  
Idriss Chana ◽  
Mohammed Lahmer ◽  
Abdallah Rhattoy
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Business Process ◽  
Model Transformation ◽  
Source Code ◽  
Elementary Transformation ◽  
Multiple Points ◽  
Model Driven ◽  
Computer Scientists ◽  
Synthesis Methodology

The CIM, PIM, and PSM models are the main levels of the MDA approach. Model transformation is an important step in the MDA process. Indeed, in MDA there are two elementary transformation kinds: CIM to PIM transformation and PIM to PSM transformation. However, most searches propose approaches transforming PIM to PSM, since there are multiple points in common between PIM and PSM. Nevertheless, transforming CIM to PIM is rarely addressed in research because these two levels are mainly different. However, there is not a synthesis work that makes it possible to carry out a model transformation from CIM to PIM towards PSM until obtaining the code. This synthesis methodology allows controlling models transformation from CIM to PIM to PSM, indeed, up to obtaining code according the MDA. This approach makes it possible to limit the intervention of computer scientists in the life cycle of software development. Indeed, this methodology allows modeling only CIM, the business process, and then obtains the source code through successive semi-automatic transformations.

Methodical Spatial Database Design with Topological Polygon Structures

2012 ◽  
Vol 3 (1) ◽  
pp. 21-30
Author(s):  
Jean Damascène Mazimpaka
Keyword(s):  
Design Process ◽  
Spatial Data ◽  
Spatial Databases ◽  
Early Stage ◽  
Spatial Database ◽  
Database Design ◽  
Integrity Constraints ◽  
Data Types ◽  
Data Infrastructure ◽  
Database Development

Spatial databases form the foundation for a Spatial Data Infrastructure (SDI). For this, a spatial database should be methodically developed to accommodate its role in SDI. It is desirable to have an approach to spatial database development that considers maintenance from the early stage of database design and in a flexible way. Moreover, there is a lack of a mechanism to capture topological relations of spatial objects during the design process. This paper presents an approach that integrates maintenance of topological integrity constraints into the whole spatial database development cycle. The approach is based on the concept of Abstract Data Types. A number of topological classes have been identified and modelling primitives developed for them. Topological integrity constraints are embedded into maintenance functions associated with the topological classes. A semi-automatic transformation process has been developed following the principles of Model Driven Architecture to simplify the design process.

Utilizing new capabilities of XML languages to verify integrity constraints

2012 ◽  
Author(s):  
Jakub Malý ◽  
Martin Nečaský
Keyword(s):  
Error Recovery ◽  
Higher Order ◽  
Integrity Constraints ◽  
Object Constraint Language ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Constraint Language ◽  
Higher Order Functions ◽  
Xml Technologies

In this work, we show how integrity constraints expressed using Object Constraint Language (OCL) can be verified using XML technologies - Schematron, XPath/XQuery and XSLT - and using Model Driven Architecture (MDA) principles. Some constructs typical for OCL constraints are different from the methods used in XPath/XQuery expressions. That is why for translating some OCL expressions, the standard XML toolset must be extended. We introduce such extension for the 2.0 versions of the languages, but with the new features and constructs proposed in drafts for XSLT 3.0, XPath 3.0 and XQuery 3.0, the transition from OCL is much more seamless and transparent. Higher-order functions, maps, error-recovery instructions etc. provide us with necessary power to translate a general OCL expression and we discuss in detail their potential.

Sign in / Sign up

Export Citation Format

Share Document