Ania Cravero

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.

From Business Process to Data Model: A Systematic Mapping Study

In the field of software engineering, modeling business processes can complement the tasks currently carried out to capture various requirements, providing a common, easy graphical language to understand, allowing communication between the various actors. One type of important requirement that must be addressed is that of the data. Several studies show techniques and methods to obtain the data model of system from business process models. This study presents an overview of this research topic, through a systematic mapping studies.

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.

Methodological Proposal of Requirements Engineering Aligning IS/IT to the Business Strategy

It is important that the IS/IT are aligned with the business strategies for the organization success. In this work I present a methodological proposal of requirements engineering that uses BMM to obtain the business strategy i to represent the needs of the system actors, and BPMN to model the business processes so that they are lined up to the business strategy. As a further work it is expected to create a tool that generates the requirements of the system in a semi-automatic way.

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.

GORE in the IT aligment to business strategy: A Systematic Mapping Study

The enterprises cannot be competitive if their business and IT strategies are not aligned. In the last years, the alignment issue was addressed in several researches and numerous methods, approaches and techniques, using GORE were proposed. This paper proposes a systematic mapping study useful to evaluate differents alignment approaches, with the aim of discovering the objectives models used in the requirements engineering stage, serving as a starting point for future research in this area.

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.