Considering integrity constraints during federated database design

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.

Download Full-text

Semantic integrity constraints in knowledge-based database design systems

Data & Knowledge Engineering ◽

10.1016/0169-023x(95)00035-q ◽

1996 ◽

Vol 20 (1) ◽

pp. 1-37 ◽

Cited By ~ 2

Author(s):

Veda C. Storey ◽

Heng-Li Yang ◽

Robert C. Goldstein

Keyword(s):

Database Design ◽

Integrity Constraints ◽

Knowledge Based ◽

Design Systems

Download Full-text

Gambit: An Interactive Database Design Tool for Data Structures, Integrity Constraints, and Transactions

IEEE Transactions on Software Engineering ◽

10.1109/tse.1985.232501 ◽

1985 ◽

Vol SE-11 (7) ◽

pp. 574-583 ◽

Cited By ~ 13

Author(s):

R.P. Braegger ◽

A.M. Dudler ◽

J. Rebsamen ◽

C.A. Zehnder

Keyword(s):

Data Structures ◽

Database Design ◽

Design Tool ◽

Integrity Constraints

Download Full-text

Semantic Integrity Constraints in Federated Database Schemata (Extended Abstract)

Ausgezeichnete Informatikdissertationen 1999 ◽

10.1007/978-3-322-84823-9_23 ◽

2000 ◽

pp. 243-252

Author(s):

Can Türker

Keyword(s):

Integrity Constraints ◽

Federated Database ◽

Database Schemata

Download Full-text

Federated Enterprise Architecture

Advances in Business Information Systems and Analytics - A Systemic Perspective to Managing Complexity with Enterprise Architecture ◽

10.4018/978-1-4666-4518-9.ch010 ◽

2014 ◽

pp. 331-360

Author(s):

Edward M. Newman

Keyword(s):

Case Studies ◽

Business Process ◽

Enterprise Architecture ◽

It Governance ◽

Database Design ◽

Process Standardization ◽

Federated Search ◽

Federated Database ◽

It Innovation ◽

Business Process Standardization

The purpose of the chapter is to provide clarity on what a Federated Enterprise Architecture (FEA) is and what the benefits as well as risks are in contrast to a non-federated enterprise architecture. The chapter draws upon organizational theory, federalist theory, and case studies to explicate what constitutes a federated model and the expected federated EA benefits. There are a number of challenges with the concept of a FEA. Two are focused on in this chapter: the meaning of federated EA and associated benefits and risks. The first is the use of the term “federated,” which occurs rather frequently in ICT literature, such as “federated search” or “federated database design,” and in the context of IT governance, “federal model” in Drs. Weill and Ross’s book IT Governance. The term also appears in the non-ICT context such as “federated insurance.” However, the term “federated” is frequently not defined and when defined speaks to a decentralization concept. This distinction is relevant to the understanding and success of a federated EA implementation. In reviewing federalist theory, there is a clear difference between decentralization and federalism. It is argued that the so-called federal or federated “model,” as described, is not federated but is a form of decentralization. The second challenge within the EA discipline is the lack of benefits attributed to a FEA. In the few sources that exist for FEA benefits are either not stated or the stated benefits could equally apply to a non-FEA. It is argued that scalability is the singular key benefit that FEA provides over a non-FEA, and the following non-FEA benefits are enhanced: 1) agility and IT innovation, 2) process consolidation and business process standardization and discipline, and 3) interoperability. However, while there are clear benefits to FEA, there are inherent risks.

Download Full-text

Methodical Spatial Database Design with Topological Polygon Structures

Geographic Information Systems ◽

10.4018/978-1-4666-2038-4.ch019 ◽

2013 ◽

pp. 295-304 ◽

Cited By ~ 2

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.

Download Full-text