Databases Reference
In-Depth Information
Exhibit 29-3. Differences between transactional and foundation applications.
plication. Architectural separation of foundation and transactional
applications along with their data stores is recommended. The demarca-
tion of update responsibilities is very clear — the transactional application
updates its transactional data and the foundation application updates the
foundation data store. Access to the foundation data store is critical to the
transactional application. Administrators usually need to be able to join
data within two data stores. Technology solutions such as gateways make
this possible, even across heterogeneous database environments.
The foundation application should be a centrally developed application
deployed in a distributed fashion. The purpose of the interaction between
foundation and transactional applications, as shown in Exhibit 2, is not
only to give the transactional application user access to the foundation ap-
plication, but to make it appear seamless to the user. For example, to create
a new customer entry while taking an order, the customer service repre-
sentative does not have to log into the foundation application. Exhibit 3
shows the differences between transactional and foundation applications.
FDS AND THE CORPORATE INFORMATION FACTORY
Inmon, Imhoff, and Battas, in their topic
Building the Operational Data
Store
(New York: John Wiley & Sons, Inc., 1995), proposed a common archi-
tecture called the
that includes the operation-
al data store (ODS), data warehouse, and legacy applications (see
Exhibit 4). They describe the flow of data within the corporate information
factory as follows:
corporate information factory
1. Raw, detailed data is put into the corporate information factory by
means of data capture, entry, and transaction interaction with the
older legacy applications.
Search WWH ::
Custom Search