2005
DOI: 10.1007/978-3-540-30587-3_18
|View full text |Cite
|
Sign up to set email alerts
|

COTS Components and DB Interoperability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2010
2010
2010
2010

Publication Types

Select...
2

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 12 publications
0
3
0
Order By: Relevance
“…SA from Figure 1 is a layered model, based on software architectural styles principles [9,10] and exploited in other models, which use architectural layering to address interoperability in software systems [11,12]. A set of repositories {DB 1 … DB n } at the Persistence Layer are heterogeneous sources of data /information, generated by various parties, users and applications.…”
Section: The Outline Of Go-cidmentioning
confidence: 99%
“…SA from Figure 1 is a layered model, based on software architectural styles principles [9,10] and exploited in other models, which use architectural layering to address interoperability in software systems [11,12]. A set of repositories {DB 1 … DB n } at the Persistence Layer are heterogeneous sources of data /information, generated by various parties, users and applications.…”
Section: The Outline Of Go-cidmentioning
confidence: 99%
“…A full data-model that supports the example has been generated in ORACLE 8i [19]. We chose the J2EE platform for our implementation, because of our positive experiences of implementing software architecture for interoperable databases as an EJB application [12].…”
Section: Related Backgroundmentioning
confidence: 99%
“…The choice of the J2EE technology has influenced our software design decisions and design patterns. Any discussion on the suitability of EJB [http://java.sun.com] and its impact to our design decisions, is outside the scope of this paper, but is available in our other publications [12,13,14].…”
Section: Introductionmentioning
confidence: 99%