Samuel Sepúlveda

Requirements modeling languages for software product lines

There is a concern for generating proposals with higher levels of expressiveness.There is not a strong relationship between the proposals and SPL development process.There is a need for better ways to validate the modeling proposals.The proposals have a low level of empirical validation and adoption in industry.The level of maturity, expressive power and tool support of the proposals is low. Display Omitted Context: Software product lines (SPLs) have reached a considerable level of adoption in the software industry, having demonstrated their cost-effectiveness for developing higher quality products with lower costs. For this reason, in the last years the requirements engineering community has devoted much effort to the development of a myriad of requirements modelling languages for SPLs.Objective: In this paper, we review and synthesize the current state of research of requirements modelling languages used in SPLs with respect to their degree of empirical validation, origin and context of use, level of expressiveness, maturity, and industry adoption.Method: We have conducted a systematic literature review with six research questions that cover the main objective. It includes 54 studies, published from 2000 to 2013.Results: The mean level of maturity of the modelling languages is 2.59 over 5, with 46% of them falling within level 2 or below -no implemented abstract syntax reported-. They show a level of expressiveness of 0.7 over 1.0. Some constructs (feature, mandatory, optional, alternative, exclude and require) are present in all the languages, while others (cardinality, attribute, constraint and label) are less common. Only 6% of the languages have been empirically validated, 41% report some kind of industry adoption and 71% of the languages are independent from any development process. Last but not least, 57% of the languages have been proposed by the academia, while 43% have been the result of a joint effort between academia and industry.Conclusions: Research on requirements modeling languages for SPLs has generated a myriad of languages that differ in the set of constructs provided to express SPL requirements. Their general lack of empirical validation and adoption in industry, together with their differences in maturity, draws the picture of a discipline that still needs to evolve.

Using GORE in Data Warehouse: A Systematic Mapping Study

The Goal-Oriented Requirements Engineering, known as GORE, is the first step in the development process of systems Data Warehouses (DW). It is based on the identification of the goal of the business that wants to analyze the executive, which enables developers to obtain the information requirements of DW through a set of transformations from the goal modeling in specifications model. This paper provides an overview of how some development proposals DW used GORE to elicit, negotiate, specify and validate information requirements. The methodology is the systematic mapping studies.

An Overview of Syntactic and Semantic Issues in Software Product Lines

Feature models are at the core of Software Product Lines (SPL). Along the years different feature modeling languages have been proposed. Although they share a set of core concepts, feature languages present differences such as specification meta language, visual and textual emphasis and language constructs, among others. The result of this situation is a contemporary set of dialects with dissimilarities. This paper presents a metamodel and a semantic framework to categorize syntactic variations and semantic anomalies in SPL.

On Optimizing the Path to Information Security Compliance

Information Security Management has been contemporarily confronted by standards covering business aspects related to Information Technology. Different standards map the problem of information security to a set of controls that represent safeguards for different security vulnerabilities. Several procedure-oriented maturity models have been proposed for managing the progress on information security, however, few approaches use quantitative techniques for analyzing the progress on information security. In this paper we propose that the problem of becoming security compliance can be analyzed as a problem of multi-paths where checking different controls means choosing different ways of reaching a security compliance. We identify a set of concepts from security ontologies in order to identify a set of variables influencing these paths. The main contribution is formulating the problem of reaching some standard compliance in the shape of optimization problems, thus existing optimization techniques can be applicable.

Methodologies, techniques and tools for OLAP design: A Systematic Mapping Study

The OLAP cubes allow to visualizing information from a data warehouse to be analyzed by business executives. An interesting research topic is the OLAP design because they must be created according to the need of users, the context, how to process queries, among other research topics. This paper presents a systematic mapping study of the main research topics for designing OLAP.

Building feature models: A framework for comparing and classifying proposals

There are several proposals to build models feature either semi-automatic or fully automatic in the field of Software Product Lines. Unfortunately, there is no clarity on the common elements, their main differences and elements that characterize these proposals. The wide variety of terms used to refer to the process of building a feature model (e.g. synthesis, location, re engineering) makes the proposals are varied and very heterogeneous, which makes it complex to understand and classify them. This paper introduces a conceptual framework for classifying and comparing proposals related to the construction of feature models by semi-automatic or fully automatic means. The proposal considers six dimensions mainly focused on characterizing the input sources, methods and techniques, the results and the type of evaluation. The conceptual framework provides guidance to researchers for choosing the appropriate aspects to build feature models and helps to understand and clarify the various approaches proposed in the literature.

Feature modeling tool: A proposal using ADOxx technology

Recently there have been several efforts to address the problem of development tools for building feature models. However, such efforts have not considered a number of factors due to human imprecision such as syntax, semantics or congruence, that must be taken into account to build these models. This paper presents a proof of concept for a tool for building feature models. The tool (i) is based on a previously defined meta model, (ii) includes a set of constraints to prevent building syntactically incorrect models, (iii) use of ADOxx technology and ADO script programming language. The tool aims to provide engineers and researchers the ability to build feature models exploiting the potential that delivers ADOxx.

Un enfoque de ingeniería de requerimientos basada en el alineamiento de almacenes de datos y la estrategia del negocio

Garantizar que los almacenes de datos esten alineados a la estrategia del negocio es primordial para su exito, ya que estos son utilizados por los gerentes del negocio con el fin de analizar los datos estrategicos de la organizacion. En este trabajo presentamos un enfoque de ingenieria de requerimientos orientado al negocio que alinea el Almacen de Datos a su plan estrategico. El proceso se describe mediante un conjunto de directrices que incluyen: el analisis VMOST para obtener los objetivos desde los usuarios, el modelo BMM para comprobar que los objetivos definidos esten alineados con la estrategia, el modelado de objetivos por medio de i* con el fin de obtener los requerimientos de informacion del Almacen de Datos, y el modelado multidimensional mediante un perfil UML. Se presenta un estudio de caso para mostrar el proceso completo.