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

Measuring Software Process: A Systematic Mapping Study

Context: Measurement is essential to reach predictable performance and high capability processes. It provides support for better understanding, evaluation, management, and control of the development process and project, as well as the resulting product. It also enables organizations to improve and predict its process’s performance, which places organizations in better positions to make appropriate decisions. Objective: This study aims to understand the measurement of the software development process, to identify studies, create a classification scheme based on the identified studies, and then to map such studies into the scheme to answer the research questions. Method: Systematic mapping is the selected research methodology for this study. Results: A total of 462 studies are included and classified into four topics with respect to their focus and into three groups based on the publishing date. Five abstractions and 64 attributes were identified, 25 methods/models and 17 contexts were distinguished. Conclusion: capability and performance were the most measured process attributes, while effort and performance were the most measured project attributes. Goal Question Metric and Capability Maturity Model Integration were the main methods and models used in the studies, whereas agile/lean development and small/medium-size enterprise were the most frequently identified research contexts.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2- RMinisterio de Economía y Competitividad TIN2015-71938-RED

ILR Research in Progress 2011-12

The production of scholarly research continues to be one of the primary missions of the ILR School. During a typical academic year, ILR faculty members published or had accepted for publication over 25 books, edited volumes, and monographs, 170 articles and chapters in edited volumes, numerous book reviews. In addition, a large number of manuscripts were submitted for publication, presented at professional association meetings, or circulated in working paper form. Our faculty's research continues to find its way into the very best industrial relations, social science and statistics journals.Research_in_Progress_2011_12.pdf: 46 downloads, before Oct. 1, 2020

What to Fix? Distinguishing between design and non-design rules in automated tools

Technical debt---design shortcuts taken to optimize for delivery speed---is a critical part of long-term software costs. Consequently, automatically detecting technical debt is a high priority for software practitioners. Software quality tool vendors have responded to this need by positioning their tools to detect and manage technical debt. While these tools bundle a number of rules, it is hard for users to understand which rules identify design issues, as opposed to syntactic quality. This is important, since previous studies have revealed the most significant technical debt is related to design issues. Other research has focused on comparing these tools on open source projects, but these comparisons have not looked at whether the rules were relevant to design. We conducted an empirical study using a structured categorization approach, and manually classify 466 software quality rules from three industry tools---CAST, SonarQube, and NDepend. We found that most of these rules were easily labeled as either not design (55%) or design (19%). The remainder (26%) resulted in disagreements among the labelers. Our results are a first step in formalizing a definition of a design rule, in order to support automatic detection.Comment: Long version of accepted short paper at International Conference on Software Architecture 2017 (Gothenburg, SE

Formal software measurements for object-oriented business models.

This paper presents a set of metrics and pseudo-metrics for the measurement of conceptual distances in M.E.R.O.D.E. business models. The measures are developed and validated using measure and measurement theory. It is argued that this metrics set constitutes a strong formal basis for the further assessment and prediction of relevant internal and external attributes of object-oriented specifications.Keywords: object type, business model, conceptual distance, measure theory, measurement theory, metric, pseudo-metric, scale type, measure validation.Measurement; Model; Models; Software;

Evolution of statistical analysis in empirical software engineering research: Current state and steps forward

Software engineering research is evolving and papers are increasingly based on empirical data from a multitude of sources, using statistical tests to determine if and to what degree empirical evidence supports their hypotheses. To investigate the practices and trends of statistical analysis in empirical software engineering (ESE), this paper presents a review of a large pool of papers from top-ranked software engineering journals. First, we manually reviewed 161 papers and in the second phase of our method, we conducted a more extensive semi-automatic classification of papers spanning the years 2001--2015 and 5,196 papers. Results from both review steps was used to: i) identify and analyze the predominant practices in ESE (e.g., using t-test or ANOVA), as well as relevant trends in usage of specific statistical methods (e.g., nonparametric tests and effect size measures) and, ii) develop a conceptual model for a statistical analysis workflow with suggestions on how to apply different statistical methods as well as guidelines to avoid pitfalls. Lastly, we confirm existing claims that current ESE practices lack a standard to report practical significance of results. We illustrate how practical significance can be discussed in terms of both the statistical analysis and in the practitioner's context.Comment: journal submission, 34 pages, 8 figure

Development of the Occupational Performance Inventory of Sexuality and Intimacy (OPISI): Phase One

Background: The occupational therapy profession needs a framework to guide understanding of the occupational nature of sexuality and intimacy, assessment, intervention design, and measurement of outcomes. This study aimed to define the occupational nature of sexuality and intimacy and develop a theoretical and occupation-based screen, in-depth self-assessment, and performance measure. Method: The Occupational Performance Inventory of Sexuality and Intimacy (OPISI) was developed following DeVellis’s (2017) guidelines for scale development that involved mapping the construct, generating an item pool, determining the format for measurement, and reviewing the initial item pool. Results: The Occupational Therapy Sexual Assessment Framework (OTSAF) was developed to define the occupational nature of sexuality and intimacy, depict how the theoretical constructs intertwine with the domain of occupational therapy, and guide scale development. The OPISI includes a self-screen, in-depth self-assessment, and an individualized measure to establish baseline performance and detect self-perceived change in ability, satisfaction, understanding, and confidence in skills and ability to improve occupational performance associated with sexuality and intimacy over time. Conclusion: The OTSAF defines the occupational nature of sexuality and intimacy and informs the occupational therapy scope of practice. The OPISI includes theoretical and occupation-based tools to adequately screen, assess, and measure performance related to the complex occupational nature of sexuality and intimacy. Formal validation is needed prior to releasing the OPISI for clinical use