Architecture for Symbolic Object Warehouse

Table 2. Taxonomy Figure 2 shows a conceptual architecture to identify

the most important modules of the system. A manager A
Country Continent is associated to each of them, so that they achieve
Spain Europe flexibility (it is simple to add new functions); and the
China Asia functionality encapsulation in every component helps
Australia Oceania the design organization and modularization. Thus, we
Sudan Africa can distinguish:
Argentina America
• System functionalities.
India Asia
• What component carries out each task
France Europe
• Information/knowledge workflows.
Canada America
Italy Europe In the next paragraphs, a briefly explanation of each
Germany Europe component functionality is completed.
EEUU America Intelligent Interface: It is responsible for the con-
nection between the system and the user. We design this
component with two Intelligent Discovery Assistants
(Bernstein et al., 2005); one assists in DW tasks and
SO-Services (4) [Study Level ={“medium”(0.25), the other with analysis or DM.
“high”(0.75)}] ∧ [Continent = {“Africa” ETL Manager: The user defines the SO descriptor
(0.25), “America”(0.25), “Asia”(0.25), “Eu- and the system must obtain the data from operational
rope”(0.25)}] ∧ [Age= [39:60]]]. databases and external sources. Two different types
loads are assumed:
Now we have second order units representing the
concept activity of our clients. The number in brackets • Initial a predefined SO descriptor, which models
is the quantity of individuals belonging to the SO, the the principal business concepts.
variables show the values for the class, for example • Ad hoc with new SOs, which respond to new
SO-Manufactures: the variable Study Level shows informational requirements.
equal probability. The clients are distributed 33 % in
Asia and 66 % in Europe. The age is between 39 and The major sub components of ETL Manager mod-
60 years. ule are:
To plan the analysis units or SOs we need:
• ETL Scheduler
• Knowledge domain, • Extraction Engine &Load Engine
• Rules of the business, • Transformation & Clean Engine
• Type of information stored in the operational
systems, -organizational structures. Mining & Layout Manager: It is the core analysis.
It shows SOs descriptors and makes all type of graphics.
We call the former elements Background Knowl- Particularly, graphic subcomponent has to implement
edge. Zoom Star graphic (Noirhomme, 2000, 2004), which
is the best way to visualize SOs. The main subcom-
Architecture ponents are:

Figure 1 shows the information flows, information • Mining Scheduler

knowledge and the most important tasks covered by this • Method Engine
architecture (González Císaro, Nigro & Xodo, 2006). • Method DB
Generally, almost all current DW and DM solutions are • Graphic Manager
based on decoupled architectures. DM tools suppose the • Exploration Manager
data to be already selected, cleaned and transformed.
Solutions integrating steps must be addressed.