An Evaluation Framework for Data Quality Tools

International audienceData Quality is a major stake for large organizations and software companies are proposing increasing numbers of tools focusing on these issues. The scope of these tools is moving from specific applications (deduplication, address normalization etc ...) to a more global perspective integrating all areas of data quality (profiling, rule-detection...). A framework is needed to help managers to choose this type of tool. In this article, we focus on tool-functionalities which aim to measure the quality of data(bases). We explain what one can expect of such functionalities in a CRM context, and we propose a general matrix which can be used for the evaluation and comparison of these tools

Adoption of a visual model for temporal database representation

Today, in the world of information technology, conceptual model representation of database schemas is challenging for users both in the Software Development Life Cycle (SDLC) and the Human-Computer Interaction (HCI) domain. The primary way to resolve this issue, in both domains, is to use a model that is concise, interpretable and clear to understand, yet encompasses all of the required information to be able to clearly define the database. A temporal database is understood as a database capable of supporting reasoning of time-based data for e.g.: a temporal database can answer questions such as: - for what period was Mrs Jones single before she got married? On the other hand, an atemporal database stores data that is valid today and has no history. In the thesis, I looked at different theoretical temporal visual conceptual models proposed by temporal researchers and aimed, by means of a user-survey consisting of business users, to ascertain towards which models users a preference has. I further asked the users for firstly; whether they prefer textual or graphical representations for the entities, attributes and constraints represented by the visual models, or secondly; whether there is a preference for a specific graphical icon for the temporal entities and lastly; to ascertain if the users show a preference towards a specific theoretical temporal conceptual model. The methodology employed to reach my goal in this thesis, is one of experiments on business users with knowledge enhancements after each experiment. Users were to perform a task, and then based on analysis of the task results, they are taught additional temporal aspects so as improve their knowledge before the next experiment commences. The ultimate aim was to extract a visual conceptual model preference from business users with enhanced knowledge of temporal aspects. This is the first work done in this field and thus will aid researchers in future work, as they will have a temporal conceptual model that promotes effective communication, understandability and interpretability

Relational database design using an ER approach and Prolog

In the context of CASE tool development for relational database design, this paper develops a methodology that maps an enhanced Entity- Relationship (ER) schema into a relational schema and normalizes the latter into inclusion normal form (IN-NF). Unlike classical normalization that characterizes individual relations only, IN-NF concerns interrelational redundancies. The paper formalizes sources such redundancies in ER schemas. Our methodology enhances several other proposals, in particular [10]. The paper briefly presents our implementation of the methodology using Prolog.Proceedings of the 6th International Conference on Information Systems and Management of Data, CISMOD’95 (Bombay, India, November 1995)SCOPUS: cp.kinfo:eu-repo/semantics/publishe

The Rejuvenation of Materialized Views (Extended Abstract)

) Inderpal Singh Mumick AT&T Bell Laboratories 600 Mountain Avenue Murray Hill, NJ 07974, USA. [email protected] Abstract. This is a short summary of a talk presented at the sixth International Conference on Information Systems and Management of Data (CISMOD 95) held in Bombay in November 1995. The summary describes some of the applications that are causing a renewed interest in materialized views, the problems in supporting the applications, and sketches how the current work in this area is addressing some of the problems. 1 Introduction What is a view? A view is a derived relation defined in terms of base (stored) relations. A view thus defines a function from a set of base tables to a derived table; this function is typically recomputed every time the view is referenced. What is a materialized view? A view can be materialized by storing the tuples of the view in the database. Index structures can be built on the materialized view. Consequently, database accesses to the mate..