2003
DOI: 10.1007/978-3-540-45275-1_6
|View full text |Cite
|
Sign up to set email alerts
|

An Architecture for Managing Database Evolution

Abstract: Abstract. This paper presents an architecture for managing database evolution when all the components of the database (conceptual schema, logical schema and extension) are available. The strategy of evolution in which our architecture is based is that of 'forward database maintenance', that is, changes are applied to the conceptual schema and propagated automatically down to the logical schema and to the extension. In order to put into practice this strategy, each component of a database is seen under this arc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2004
2004
2015
2015

Publication Types

Select...
3
3

Relationship

1
5

Authors

Journals

citations
Cited by 8 publications
(7 citation statements)
references
References 11 publications
(30 reference statements)
0
7
0
Order By: Relevance
“…In the existing literature, there are several works that focus on schema evolution [9], database evolution [10], and workflow evolution [11]. Roddick et al [12] proposed a taxonomy-based approach for schema evolution.…”
Section: Related Workmentioning
confidence: 99%
“…In the existing literature, there are several works that focus on schema evolution [9], database evolution [10], and workflow evolution [11]. Roddick et al [12] proposed a taxonomy-based approach for schema evolution.…”
Section: Related Workmentioning
confidence: 99%
“…As it is said in the introduction, the scaffolding of our approach is constituted by an architecture we presented in [4,5] applied within a database evolution setting. Although the architecture has been proven within this setting, it was designed with the aim of being independent of any particular modeling technique.…”
Section: Evolution Architecture Overviewmentioning
confidence: 99%
“…More specifically, the architecture includes a conceptual component, a translation component, a logical component and an extensional component. We will describe briefly the meaning and purpose of each component (see [4,5] for details).…”
Section: Evolution Architecture Overviewmentioning
confidence: 99%
See 1 more Smart Citation
“…This problem faces how to reflect in the logical and extensional schemas the changes that have occurred in the conceptual schema of a database. As a contribution towards achieving a satisfactory solution to this problem (that has not been found yet, despite a lot of efforts by different researchers [7,5]), authors of the [9] have presented an architecture for managing database evolution. Another problem in Database System is productivity, w.r.t.…”
Section: Introductionmentioning
confidence: 99%