Enterprise Architecture Integration: Decomposition and Recomposition

This report provides an in-depth analysis of Enterprise Architecture Integration (EAI), focusing on the EAI diagram of Royal Wallace and the application of business objects as a wrapping technique. The diagram includes Schema Translation Processor (STP), Query Translation Processor (QTP), and Data Translation Processor (DTP) connected to intelligent queuing and control broker features for unified data gathering. The report also explores decomposition and recomposition within the SEEBEYOND project, which is based on OMG's spread object management architecture, and discusses the transformation of SQL queries to relational algebra. It covers normalization, analysis, redundancy reduction, and spinning techniques to optimize query processing. The report concludes with a bibliography of relevant sources.

Running head: ENTERPRISE ARCHITECTURE INTEGRATION
Enterprise Architecture Integration
Name of the Student
Name of the University

1ENTERPRISE ARCHITECTURE INTEGRATION
1. EAI Diagram of Royal Wallace:
Figure 1: The EAI Diagram of Royal Wallace
(Source: Created by Author)
Business objects has been used as the wrapping technique within this EAI diagram. The
wrapping technique can be considered as the part of integration of system. These objects are
consist of Schema Translation Processor (STP), Query Translation Processor (QTP) and Data
Translation Processor (DTP). These wrappers are connected to the intelligent queuing feature
and control broker of the system. This allows the system to gather all the data regarding the
business process and back office for having it in a single place. This allows better data
processing for individual legacy system.

2ENTERPRISE ARCHITECTURE INTEGRATION
2. Decomposition and Recomposition:
Environment: The query processing approach presented in this paper is implemented in
the SEEBEYOND (METU Interoperable DBMS) project. SEEBEYOND structure is established
on OMG's1 spread object management architecture. The infrastructure of the unit is construct on
a CORBA implementation, particularly DEC's Ob jectBroker2. A program of a common
Database Object through CORBA IDL has been numerous implementations with this software
for Sybase3 , Oracle74 , Adabas D5 and MOOD (METU Ob jectOriented DBMS) have already
been developed. Therefore, what customers with this stage see are homogeneous DBMS ob jects
available through a common interface. The main element structure of SEEBEYOND is provided
in Figure 1. The fundamental the various elements of the unit actually certainly are a
International Database Agent (GDA) school and a Local Database Agent (LDA) class. Whenever
a customer actually really wants to communicate with SEEBEYOND, a GDA object (GDAO) is
produced by sending a develop concept to the Object Factory. ORB offers the location and
implementation transparency for GDAOs. The positioning of GDAOs are dynamically
determined by the ORB using the data furnished by the ORB administrator. The default website
for the GDAO is generally the local variety to prevent communication costs.
Decomposition: The query decomposition is the process of transforming an SQL query to
a relational algebra. Normalization, analysis, elimination of redundancy and rewriting. The
normalization can be considered as the procedure of organizing the information within a
database. This process is done mainly for removing the redundancy as much as possible. The
normalization also assist in preventing anomalies like update, insertion and deletion. Taken as an
example, the update of a data that is associated to two different attributes, must be done for both
the rows. There are four main normal forms such as first normal form, second normal form, third

3ENTERPRISE ARCHITECTURE INTEGRATION
normal form and boyce & code normal form. Through the analysis, the rejection of incorrect one.
This means that if any incorrect or unnecessary calculation or normalization is done then it will
be rejected. The wrong types may be that the relations or attributes do maybe not exist and the
incorrect operations. There will be the likelihood of semantically wrong forms such as for
instance like areas don't donate to the consequence, recognition possible applying instances
which does not contain disjunction or negation, issue chart and join graph. Reduction of
Redundancy refers to the exchange of expression that's formerly found in views. Customer error
or this exchange may possibly contain redundant predicates. Spinning is the strategy of
transforming SQL to Relational Algebra straightaway. Spinning could be named restructuring
operators to boost efficiency.

4ENTERPRISE ARCHITECTURE INTEGRATION
Bibliography:
Borril, P., Burgess, M., Craw, T. and Dvorkin, M., 2014. A promise theory perspective on data
networks. arXiv preprint arXiv:1405.2627.
Da Xu, L., 2014. Enterprise integration and information architecture. CRC Press.
Fischer, R., Aier, S. and Winter, R., 2015. A federated approach to enterprise architecture model
maintenance. Enterprise Modelling and Information Systems Architectures, 2(2), pp.14-22.
Kolev, B., Valduriez, P., Bondiombouy, C., Jiménez-Peris, R., Pau, R. and Pereira, J., 2016.
CloudMdsQL: querying heterogeneous cloud data stores with a common language. Distributed
and parallel databases, 34(4), pp.463-503.
Simon, D., Fischbach, K. and Schoder, D., 2014. Enterprise architecture management and its role
in corporate strategic management. Information Systems and e-Business Management, 12(1),
pp.5-42.