A Scalable Business Intelligence Decision-Making System in the Era of Big Data
Fatima Kalna1, Allae Erraissi2, Mouad Banane3, Abdessamad Belangour4

1Fatima Kalna, Laboratory of Information Technology and Modeling, Hassan II University, Faculty of sciences Ben M‟Sik. Casablanca, Morocco.
2Allae Erraissi*, Laboratory of Information Technology and Modeling, Hassan II University, Faculty of sciences Ben M‟Sik. Casablanca, Morocco.
3Mouad Banane, Laboratory of Information Technology and Modeling, Hassan II University, Faculty of sciences Ben M‟Sik. Casablanca, Morocco.
4Abdessamad Belangour, LTIM, Hassan II University. FSBM. Faculty of Sciences Ben M‟Sik. Casablanca, Morocco.

Manuscript received on September 16, 2019. | Revised Manuscript received on 24 September, 2019. | Manuscript published on October 10, 2019. | PP: 2034-2042 | Volume-8 Issue-12, October 2019. | Retrieval Number: L32511081219/2019©BEIESP | DOI: 10.35940/ijitee.L3251.1081219
Open Access | Ethics and Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)

Abstract: Transformation presents the second step in the ETL process that is responsible for extracting, transforming and loading data into a data warehouse. The role of transformation is to set up several operations to clean, to format and to unify types and data coming from multiple and different data sources. The goal is to get data to conform to the schema of the data warehouse to avoid any ambiguity problems during the data storage and analytical operations. Transforming data coming from structured, semi-structured and unstructured data sources need two levels of treatments: the first one is transformation schema to schema to get a unified schema for all selected data sources and the second treatment is transformation data to data to unify all types and data gathered. To ensure the setting up of these steps we propose in this paper a process switch from one database schema to another as a part of transformation schema to schema, and a meta-model based on MDA approach to describe the main operations of transformation data to data. The results of our transformations propose a data loading in one of the four schemas of NoSQL to best meet the constraints and requirements of Big Data.
Keywords: Model Driven Engineering, Meta-Model; Business Intelligence, Big Data.
Scope of the Article: Big Data Analytics and Business Intelligence