Using Ontologies for the Design of Data Warehouses

Obtaining an implementation of a data warehouse is a complex task that forces designers to acquire wide knowledge of the domain, thus requiring a high level of expertise and becoming it a prone-to-fail task. Based on our experience, we have detected a set of situations we have faced up with in real-world projects in which we believe that the use of ontologies will improve several aspects of the design of data warehouses. The aim of this article is to describe several shortcomings of current data warehouse design approaches and discuss the benefit of using ontologies to overcome them. This work is a starting point for discussing the convenience of using ontologies in data warehouse design.Comment: 15 pages, 2 figure

The determinants of the quality of Sales-Marketing Interface in a Multinational Customer Brand Focused Company: The Latin American Branches

Customer evolution and changes in consumers, determine the fact that the quality of the interface between marketing and sales may represent a true competitive advantage for the firm. Building on multidimensional theoretical and empirical models developed in Europe and on social network analysis, the organizational interface between the marketing and sales departments of a multinational high-growth company with operations in Argentina, Uruguay and Paraguay is studied. Both, attitudinal and social network measures of information exchange are used to make operational the nature and quality of the interface and its impact on performance. Results show the existence of a positive relationship of formalization, joint planning, teamwork, trust and information transfer on interface quality, as well as a positive relationship between interface quality and business performance. We conclude that efficient design and organizational management of the exchange network are essential for the successful performance of consumer goods companies that seek to develop distinctive capabilities to adapt to markets that experience vertiginous change

Combining Objects with Rules to Represent Aggregation Knowledge in Data Warehouse and OLAP Systems

Data warehouses are based on multidimensional modeling. Using On-Line Analytical Processing (OLAP) tools, decision makers navigate through and analyze multidimensional data. Typically, users need to analyze data at different aggregation levels (using roll-up and drill-down functions). Therefore, aggregation knowledge should be adequately represented in conceptual multidimensional models, and mapped in subsequent logical and physical models. However, current conceptual multidimensional models poorly represent aggregation knowledge, which (1) has a complex structure and dynamics and (2) is highly contextual. In order to account for the characteristics of this knowledge, we propose to represent it with objects (UML class diagrams) and rules in Production Rule Representation (PRR) language. Static aggregation knowledge is represented in the class diagrams, while rules represent the dynamics (i.e. how aggregation may be performed depending on context). We present the class diagrams, and a typology and examples of associated rules. We argue that this representation of aggregation knowledge allows an early modeling of user requirements in a data warehouse project.Aggregation; Conceptual Multidimensional Model; Data Warehouse; On-line Analytical Processing (OLAP); Production Rule; UML

Combining Objects with Rules to Represent Aggregation Knowledge in Data Warehouse and OLAP Systems

Les entrepôts de données reposent sur la modélisation multidimensionnelle. A l'aide d'outils OLAP, les décideurs analysent les données à différents niveaux d'agrégation. Il est donc nécessaire de représenter les connaissances d'agrégation dans les modèles conceptuels multidimensionnels, puis de les traduire dans les modèles logiques et physiques. Cependant, les modèles conceptuels multidimensionnels actuels représentent imparfaitement les connaissances d'agrégation, qui (1) ont une structure et une dynamique complexes et (2) sont fortement contextuelles. Afin de prendre en compte les caractéristiques de ces connaissances, nous proposons de les représenter avec des objets (diagrammes de classes UML) et des règles en langage PRR (Production Rule Representation). Les connaissances d'agrégation statiques sont représentées dans les digrammes de classes, tandis que les règles représentent la dynamique (c'est-à-dire comment l'agrégation peut être effectuée en fonction du contexte). Nous présentons les diagrammes de classes, ainsi qu'une typologie et des exemples de règles associées.Agrégation ; Entrepôt de données ; Modèle conceptuel multidimensionnel ; OLAP ; Règle de production ; UML

Measuring Process Modelling Success

Process-modelling has seen widespread acceptance, par ticularly on large IT-enabled Business Process Reengineering projects. It is applied, as a process design and management technique, across all life-cycle phases of a system. While there has been much research on aspects of process-modelling, little attention has focused on post-hoc evaluation of process-modelling success. This paper addresses this gap, and presents a process-modelling success measurement (PMS) framework, which includes the dimensions: process-model quality; model use; user satisfaction; and process modelling impact. Measurement items for each dimension are also suggested

Business intelligence systems and user's parameters: an application to a documents' database

This article presents earlier results of our research works in the area of modeling Business Intelligence Systems. The basic idea of this research area is presented first. We then show the necessity of including certain users' parameters in Information systems that are used in Business Intelligence systems in order to integrate a better response from such systems. We identified two main types of attributes that can be missing from a base and we showed why they needed to be included. A user model that is based on a cognitive user evolution is presented. This model when used together with a good definition of the information needs of the user (decision maker) will accelerate his decision making process