LUCENTIA Research Group Department of Software and Computing Systems Using i* modeling for the multidimensional design of data warehouses Jose-Norberto.

Slides:



Advertisements
Similar presentations
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
C6 Databases.
Department of Software and Computing Systems Physical Modeling of Data Warehouses using UML Sergio Luján-Mora Juan Trujillo DOLAP 2004.
Accessing Organizational Information—Data Warehouse
A Pattern-Driven Security Process for SOA Applications
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
7 July 2003 MDA presentation Dennis Wagelaar 1 Model-Driven Architecture The current state of affairs.
Organizing Data & Information
Model Driven Architecture (MDA) Partha Kuchana. Agenda What is MDA Modeling Approaches MDA in a NutShell MDA Models SDLC MDA Models (an Example) MDA -
Data and Knowledge Management
Chapter 13 The Data Warehouse
Business Intelligence System September 2013 BI.
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Database Systems: Design, Implementation, and Management Ninth Edition
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Recommender Systems on the Web: A Model-Driven Approach Gonzalo Rojas – Francisco Domínguez – Stefano Salvatori Department of Computer Science University.
MDA Guide Version CYT. 2 Outline OMG Vision and Process Introduction to MDA How is MDA Used? MDA Transformations Other MDA Capabilities Using the.
Intro to MIS – MGS351 Databases and Data Warehouses Chapter 3.
Understanding Data Warehousing
Using MDA in Web Software Architectures Santiago Meliá Cristina Cachero Jaime Gómez Universidad de Alicante Spain.
MDA and QVT  Tom Gullion, Director of Product Management, Together Products.
ITEC224 Database Programming
1 Introduction to Database Systems. 2 Database and Database System / A database is a shared collection of logically related data designed to meet the.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
3 April SOA: Services Oriented Architecture MDA: Model Driven Architecture.
Model transformation with a dedicated imperative language IRISA Rennes (France) - Triskell team Jean-Marc Jézéquel Didier Vojtisek Jean-Philippe Thibault.
Introduction to MDA (Model Driven Architecture) CYT.
Secure Systems Research Group - FAU Securing Service-Oriented Architectures using a Model-driven Approach Nelly A Delessy.
Alignment of ATL and QVT © 2006 ATLAS Nantes Alignment of ATL and QVT Ivan Kurtev ATLAS group, INRIA & University of Nantes, France
SMML: Software Measurement Modeling Language Beatriz Mora, Félix García, Francisco Ruiz, Mario Piattini Department of Information Technologies & Systems.
ISO/IEC CD and WD : Core Model and Model Mapping ISO/IEC JTC1/SC32/WG September 2005, Toronto SC32/WG2 Japan (Kanrikogaku Ltd) Masaharu.
1 Data Warehouses BUAD/American University Data Warehouses.
Data and Knowledge Management
Model Driven Development An introduction. Overview Using Models Using Models in Software Feasibility of MDA MDA Technologies The Unified Modeling Language.
1 Introduction to Software Engineering Lecture 1.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Department of Industrial Engineering Sharif University of Technology Session# 9.
Foundations of Business Intelligence: Databases and Information Management.
MDA & RM-ODP. Why? Warehouses, factories, and supply chains are examples of distributed systems that can be thought of in terms of objects They are all.
DATABASES. -2 Competencies Distinguish between the physical and logical view of data Describe how data is organized Describe databases Describe the five.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Metasolv-OCDM Connector Metasolv OCDM. What is the MSS Adapter for Oracle Communications Data Model? The Oracle Communications Metasolv and Solution Adapter.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
Model Driven Architecture MDA SE-548 Lale Doğan
Chapter 8: Data Warehousing. Data Warehouse Defined A physical repository where relational data are specially organized to provide enterprise- wide, cleansed.
Page 1 Hitachi Ltd. – FhI FOKUS TTCN-3 User Conference, June 2005 MDA based approach for generation of TTCN-3 test specifications Hideto Ogawa, Hitachi.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Data Mining and Data Warehousing: Concepts and Techniques What is a Data Warehouse? Data Warehouse vs. other systems, OLTP vs. OLAP Conceptual Modeling.
Intro to MIS – MGS351 Databases and Data Warehouses
Object Management Group Information Management Metamodel
Chapter 13 The Data Warehouse
Data Warehouse.
OLAP Systems versus Statistical Databases
Databases and Data Warehouses Chapter 3
Business Rule Based Configuration Management and Software System Implementation Using Decision Tables Olegas Vasilecas, Aidas Smaizys VGTU, Vilnius, Lithuania.
MANAGING DATA RESOURCES
Evaluating Compuware OptimalJ as an MDA tool
Conceptual, Logical, and Physical Design of Data Warehouses
CS310 Software Engineering Dr.Doaa Sami
Data Model.
UML profiles.
Constructing MDA-based Application Using Rational XDE for .NET
Metadata Framework as the basis for Metadata-driven Architecture
Introduction of Week 9 Return assignment 5-2
Data Warehouse.
Database Systems: Design, Implementation, and Management Tenth Edition
Presentation transcript:

LUCENTIA Research Group Department of Software and Computing Systems Using i* modeling for the multidimensional design of data warehouses Jose-Norberto Mazón, Juan Trujillo, Toronto, 17 th July 2008

Using i* modeling for the multidimenional design of data warehouses 2 Contents Introduction Current research Requirements for DWs Reconciling with data sources Deriving logical representations Conclusions and short term research

Using i* modeling for the multidimenional design of data warehouses 3 Contents Introduction Current research Requirements for DWs Reconciling with data sources Deriving logical representations Conclusions and short term research

Using i* modeling for the multidimenional design of data warehouses 4 Introduction Research problem Data warehouse Integrated collection of historical data in support of decision making process Multidimensional (MD) modeling Fact Contains interesting measures of a business process Dimension Represents context of analysis Resembles traditional method for database design Model at conceptual level Abstracting details related to specific technologies

Using i* modeling for the multidimenional design of data warehouses 5 DATA SOURCES INTERNAL EXTERNAL DATA WAREHOUSE ETL CUBES OLAP DATA MINING REPORTS WHAT-IF ANALYSIS - Integrated collection of historical data in support of decision makers Introduction Research problem

Using i* modeling for the multidimenional design of data warehouses 6 DATA SOURCES INTERNAL EXTERNAS DATA WAREHOUSE ETL CUBES OLAP DATA MINING REPORTS WHAT-IF ANALYSIS DATA SOURCES - Integrated collection of historical data in support of decision makers Introduction Research problem

Using i* modeling for the multidimenional design of data warehouses 7 DATA SOURCES INTERNAL EXTERNAS DATA WAREHOUSE ETL CUBES OLAP DATA MINING REPORTS WHAT-IF ANALYSIS DATA SOURCES - Integrated collection of historical data in support of decision makers - Information needs cannot be understood by only analyzing data sources Introduction Research problem

Using i* modeling for the multidimenional design of data warehouses 8 DATA SOURCES INTERNAL EXTERNAS DATA WAREHOUSE ETL CUBES OLAP DATA MINING REPORTS DECISION MAKERS DATA SOURCES - Integrated collection of historical data in support of decision makers Introduction Research problem - Information needs cannot be understood by only analyzing data sources

Using i* modeling for the multidimenional design of data warehouses 9 WHAT-IF ANALYSIS DATA SOURCES INTERNAL EXTERNAS DATA WAREHOUSE ETL CUBES OLAP DATA MINING REPORTS WHAT-IF ANALYSIS DECISION MAKERS DATA SOURCES - Integrated collection of historical data in support of decision makers Introduction Research problem - Information needs cannot be understood by only analyzing data sources - Decision making processes must be understood by designers

Using i* modeling for the multidimenional design of data warehouses 10 Only data sources are analyzed to define the conceptual MD model Incorrect information needs may be modeled Requirements are specified once the conceptual MD model is defined (even after the deployment of the DW) Incorrect MD elements may be modeled Requirements and data sources are not reconciled Complex ETL processes to populate the DW Thus, the DW is not viewed as a valuable resource Introduction Drawbacks of the state-of-the-art

Using i* modeling for the multidimenional design of data warehouses Explicit requirement analysis stage Focus on decision making processes Information requirements 2. Transformation to a conceptual MD model Model Driven approach MD model agrees with decision makers’ expectations 3. Reconcile requirement model with data sources MD model agrees with data sources Completeness Faithfulness Introduction Novelty of our proposal

Using i* modeling for the multidimenional design of data warehouses Explicit requirement analysis stage Focus on decision making processes Information requirements 2. Transformation to a conceptual MD model Model Driven approach MD model agrees with decision makers’ expectations 3. Reconcile requirement model with data sources MD model agrees with data sources Completeness Faithfulness Introduction Novelty of our proposal

Using i* modeling for the multidimenional design of data warehouses Explicit requirement analysis stage Focus on decision making processes Information requirements 2. Transformation to a conceptual MD model Model Driven approach MD model agrees with decision makers’ expectations 3. Reconcile requirement model with data sources MD model satisfies decision makers’ needs MD model agrees with data sources Completeness Faithfulness Introduction Novelty of our proposal

Using i* modeling for the multidimenional design of data warehouses 14 Defining a goal-oriented approach for DWs Based on i* Model decision processes Decision makers are concerned about GOALS not directly DATA Traceability to a conceptual MD model Align with MDA Integrate requirements and data sources Introduction Objectives of our proposal

Using i* modeling for the multidimenional design of data warehouses 15 MDA Model Driven Architecture (MDA) Object Management group (OMG) standard Using models in software development Computation Independent Model (CIM) Platform Independent Model (PIM) Platform Specific Model (PSM) Transformations between models Query/View/Transformation language (QVT) The code is obtained from PSMs

Using i* modeling for the multidimenional design of data warehouses 16 MDA Model Driven Architecture (MDA) Describes user requirements Contains information about functionality and structure of the system without taking into account the technology used to implement it Includes information about the specific technology that is used in the implementation of the system on a specific platform Every PSM is transformed into code to be executed, obtaining the final software product.

Using i* modeling for the multidimenional design of data warehouses 17 MDA Query/View/Transformation language (QVT) Declarative part of QVT Transformation  set of relations Relations between metamodels formally defined and automatically performed Relations applied to models

Using i* modeling for the multidimenional design of data warehouses 18 MDA MODEL 1 MODEL2 R DOMAIN CANDIDATE MODEL WHEN & WHERE CLAUSES KIND OF RELATION METAMODEL NAME Declarative approach of QVT specifies relationships that must hold between candidate models

Using i* modeling for the multidimenional design of data warehouses 19 Introduction Our proposal [REBNITA 2005] [RIGIM 2007] [ER 2006] [ER 2007] [DKE 2007] [DOLAP 2005] [DaWaK 2006] [DSS 2008]

Using i* modeling for the multidimenional design of data warehouses 20 Contents Introduction Current research Requirements for DWs Reconciling with data sources Deriving logical representations Conclusions and short term research

Using i* modeling for the multidimenional design of data warehouses 21 Goal Oriented Requirement Engineering DW supports the decision making process to fulfill goals of an organization Decision makers are concerned about goals Information requirements are obtained by refining decision makers’ goals MDA approach Information requirements must be derived into a conceptual MD model Requirements for DWs

Using i* modeling for the multidimenional design of data warehouses 22 CIM Goals and information requirements PIM Conceptual MD model QVT Transformation between models Requirements for DWs

Using i* modeling for the multidimenional design of data warehouses 23 Requirements for DWs Defining a CIM Classification of DW goals Strategic goals Change to a better situation Decision goals Take appropiate actions Information goals Related to required information Information requirements Interesting measures of business process Context of analysis

Using i* modeling for the multidimenional design of data warehouses 24 i* framework Modeling goals of decision makers and the required tasks and resources to fulfil them Several decision makers with different goals Two extensions of UML Profile for i* Profile for adapting i* to the DW domain Requirements for DWs Defining a CIM

Using i* modeling for the multidimenional design of data warehouses 25 Requirements for DWs Defining a CIM

Using i* modeling for the multidimenional design of data warehouses 26 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 27 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 28 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 29 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 30 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 31 Requirements for DWs Sample CIM

Using i* modeling for the multidimenional design of data warehouses 32 Conceptual MD model UML Profile for MD modeling Luján, Trujillo, Song. A UML profile for Multidimensional Modeling in Data Warehouses. Data and Knowledge Engineering Class diagram StereotypeIcon Fact Dimension Base FactAttribute DimensionAttribute Rolls-UpTo >

Using i* modeling for the multidimenional design of data warehouses 33 Conceptual MD model

Using i* modeling for the multidimenional design of data warehouses 34 Conceptual MD model Obtaining an initial PIM

Using i* modeling for the multidimenional design of data warehouses 35 Conceptual MD model Obtaining an initial PIM

Using i* modeling for the multidimenional design of data warehouses 36 Conceptual MD model Sample initial PIM

Using i* modeling for the multidimenional design of data warehouses 37 USER REQUIREMENTS DATA SOURCES RECONCILIATION PIM PSM INITIAL PIM Reconciling with data sources

Using i* modeling for the multidimenional design of data warehouses 38 Reconciling with data sources The MD conceptual model is reconciled with the available data sources The DW will be properly populated from data sources The analysis potential provided by the data sources is captured by the MD conceptual model Redundancies are avoided Optional dimension levels are controlled to enable summarizability and to avoid inconsistent queries Reconciliating process is automatically performed QVT relations based on Multidimensional Normal Forms Lechtenbörger and Vossen. Multidimensional normal forms for data warehouse design. Information Systems 28(2003)

Using i* modeling for the multidimenional design of data warehouses 39 Reconciling with data sources

Using i* modeling for the multidimenional design of data warehouses 40 n_t1=district, n_t2=state > 1..n +d 1 +r Reconciling with data sources

Using i* modeling for the multidimenional design of data warehouses 41 Deriving logical representations PIM UML profile for MD modeling [Luján et al. DKE 2006] PSM Common Warehouse Metamodel (CWM) From PIM to each PSM QVT transformation

Using i* modeling for the multidimenional design of data warehouses 42 Common Warehouse Metamodel (CWM) Resource layer Standard to represent the structure of data according to certain technologies Relational metamodel Tables, columns, primary keys, and so on Multidimensional metamodel Generic data structures Vendor specific extension Oracle Express extension Deriving logical representations

Using i* modeling for the multidimenional design of data warehouses 43 Contents Introduction Current research Requirements for DWs Reconciling with data sources Deriving logical representations Conclusions and short term research

Using i* modeling for the multidimenional design of data warehouses 44 DW projects fail in support decision making process Requirement analysis stage is overlooked for defining a conceptual MD model Using i* framework together with MDA Conclusions Objectives

Using i* modeling for the multidimenional design of data warehouses 45 MDA framework UML profile for i* Extension for using i* in the DW domain Transformations to obtain a conceptual MD model Several kind of logical representations Multidimensional normal forms Reconciling data sources and requirements in a hybrid approach Eclipse-based prototype Conclusions Scientific contributions

Using i* modeling for the multidimenional design of data warehouses 46 Eclipse-based prototype

Using i* modeling for the multidimenional design of data warehouses 47 Conclusions Related work at LUCENTIA research group UML Profile for MD Modeling at DKE 2006 UML for Physical Modeling at JCIS 2006 Common Warehouse Metamodel CIM PIM PSM MDA [DKE 2007 & DSS 2008] Requirements for DWs [RIGiM 2007] Security [DSS 2006 & IS 2007] UML profile for Data mining [DKE 2007] Data sources analysis [ER 2007]

Using i* modeling for the multidimenional design of data warehouses 48 Studying unstructured decision processes in-deth to model them in i* diagrams Taking advantage of every i* feature Considering complex mechanisms to reason about goals and structure decision processes Prioritization of goals Short term research

LUCENTIA Research Group Department of Software and Computing Systems Using i* modeling for the multidimensional design of data warehouses Jose-Norberto Mazón, Juan Trujillo, Toronto, 17 th July 2008