rithms. Section 4 discusses performance analysis of
how games data can be effective in identifying cogni-
tion while section 5 presents conclusions and future
work.
2 RELATED WORK
2.1 Computer Games, Cognition and
Learning
Positive effects of playing computer games on cog-
nitive development include improving visual intelli-
gence skills which are useful in science and technol-
ogy, and generally in such fields requiring manipu-
lation of images on a screen (Subrahmanyam et al.,
2000). Although other consequences of playing com-
puter and video games have been studied (Marti-
novic et al., 2011) computer-based games may en-
hance hand-eye coordination, visual scanning, au-
ditory discrimination, and spatial skills (DeLisi and
Wolford, 2002). It has been stated that repetitive
game playing may increase young children’s working
memory (Thorell et al., 2009), mental rotation accu-
racy (DeLisi and Wolford, 2002), and spatial rotation,
iconic skills, and visual attention (Subrahmanyam
et al., 2001). Playing the carefully and purpose-
fully designed computer games may positively affect
learning among children of wide range of ages (Sub-
rahmanyam et al., 2000), (Martinovic et al., 2014a),
(Martinovic et al., 2014b). This is because playing
computer games involves integration of “touch, voice,
music, video, still images, graphics, and text” (IBM,
1991), and can stimulate a variety of intelligences
(e.g., linguistic, logical, spatial, kinaesthetic, musi-
cal), that may particularly influence development of
literacy skills and ability to problem-solve.
2.2 Data Warehouse Schema
Integration Approaches
A data warehouse is a historical, integrated, subject-
oriented database storing data from multiple data
sources in the one data warehouse schema (Han et al.,
2011). Construction of a data warehouse is done
through processes of schema and data integration of
different data sources which involve data cleaning
(Ezeife and Ohanekwu, 2005), data transformation
and loading with periodic refreshing. A popular data
warehouse schema approach is the star schema where
there is a central fact table having foreign key at-
tributes that include the main subjects of interest, the
integration attribute, the historical time attribute and
some non-foreign key aggregate measures of inter-
est. Other descriptive tables in the data warehouse
design using the star schema are dimension attributes
for describing the foreign key attributes in the fact ta-
ble (Ezeife, 2001). A measure such as score achieved
during a game by a child can be calculated from
a multidimensional model version of the data ware-
house called the data cube (Ezeife, 2001). Existing
schema integration approaches (Kern et al., 2011),
(Fan and Poulovassilis, 2004), (Rahm and Bernstein,
2001) process some common steps during schema
integration. The first step in integrating schemas
(e.g., integrating schema1(Cust, C#, CName, First-
Name, LastName) and schema2(Customer, CustID,
Company, Contact, Phone)) is to identify and char-
acterize these inter-schema relationships between the
multiple data source schemas to be integrated. This
schema element relationships can be identified auto-
matically through integration approaches such as ap-
plication domains, match operator, architecture for
generic match, schema-level matchers, instance-level
approach. Application domains approach integrates
an independently developed schema with a given con-
ceptual schema and requires semantic query process-
ing. Once these schema relationships are identi-
fied, matching elements can be unified under a co-
herent, integrated schema or view. Match operator re-
quires a representation for its input schemas and out-
put mapping and needs to explore many approaches
to match. For example, the result of calling Match
on the two schemas above could be Cust.C# = Cus-
tomer.CustID, Cust.CName = Customer.Company,
and {Cust.FirstName, Cust.LastName} = Cus-
tomer.Contact. Schema-level matchers only consider
schema information, not instance data. The available
information includes the usual properties of schema
elements, such as name, description, data type, re-
lationship types (part-of, is-a, etc.), constraints, and
schema structure. Instance-level data can give impor-
tant insight into the contents and meaning of schema
elements. For example, a data-guide or an approx-
imate schema graph can be generated automatically
from XML documents. In (Kern et al., 2011) a frame-
work for building logical schema for federated data
warehouse from different data warehouse resources
was proposed. The logical schema of the federated
data warehouse is generated as a result of integration
of components of data warehouses (the fact and di-
mension tables). The input to the integration process
consists of several sets of fact table (F) with dimen-
sion tables (Dim) that are related to the fact table F
through foreign key constraints. To integrate the data
warehouses into one federated data warehouse, the al-
gorithm begins with an empty fact table (F
output),
AutomaticUpdatingofComputerGamesDataWarehouseforCognitionIdentification
339