WER09 - Workshop em Engenharia de Requisitos 2009: Valparaíso, Chile


Claudia Ayala, Carla Silva, Hernán Astudillo (Ed.): Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009.

voltar

@proceedings{WERpapers: WER09,
  editor = {Claudia Ayala, Carla Silva, Hernán Astudillo},
  title = {Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009},
  publisher = { },
  ISBN = {978-956-319-941-3},
  year = {2009}
}

A Introduction

1 - Preface. Claudia Ayala, Carla Silva. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp i-vii. [pdf] [scholar] Downloads: 610

Abstract:

2 - Tacit Knowledge in Requirements. Peter Sawyer, . Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 1-1. [pdf] [scholar] Downloads: 385

Abstract:

Early Requirements

3 - Towards a Framework for Improving Goal-Oriented Requirement Models Quality. Carlos Cares, Xavier Franch. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 3-14. [pdf] [scholar] Downloads: 442

Abstract: Goal-orientation is a widespread and useful approach to Requirements Engineering. However, quality assessment frameworks focused on goaloriented processes are either limited or remain on the theoretical side. Requirements quality initiatives range from simple metrics applicable to requirements documents, to general-purpose quality frameworks that include syntactic, semantic and pragmatic concerns. In some recent works, we have proposed a metrics framework for goal-oriented models, but the approach did not cover the cycle of quality assessment. In this paper we present a semiotic-based quality assessment proposal built upon the i* framework and the SEQUAL proposal. We propose a simplification of SEQUAL which can be applied to i* models by defining semantic, pragmatic and social metrics. As a result, we obtain suites of metrics that can be applied to i* goaloriented requirements models. This theoretical work is put into practice by using iStarML, a XML representation of i* models, over which XQuery sentences compute the proposed metrics.

4 - Comparing GORE Frameworks: i-star and KAOS. Vera Maria Bejamim Werneck, Antonio de Padua Albuquerque Oliveira, Julio Cesar Sampaio do Prado Leite. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 15-26. [pdf] [scholar] Downloads: 528

Abstract: Goal-Oriented Requirements Engineering (GORE) is an approach to requirements engineering dealing with intentionality in accordance with the relations among different actors. KAOS and i* (i-star) frameworks have been receiving many references as being important GORE proposals. This paper presents an conceptual analysis comparing characteristics of those methods giving examples related to actors’ relations definition, goal organizational model, tasks representation, risk analysis, and non-functional requirements. The aim of this work is to show both frameworks benefits and drawbacks. We believe that this analysis helps the understanding of the core concepts of GORE as well as it draws attention to key representation issues for both KAOS and i*.

5 - An Initial Analysis on How Software Transparency and Trust Influence each other. Luiz Marcio Cysneiros, Vera Maria Benjamim Werneck. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 27 - 32. [pdf] [scholar] Downloads: 409

Abstract: If we make a simple search on the internet for the definition of transparency there will be several different ones from optics to protocols. But most of the definitions will overlap among the notion that transparency is about how something is open enough to allow things to be deeply observed from different perspectives. Orthogonally, Transparency has been demanded in several different areas in our society. Governments are demanded to be more transparent, banks are being blamed for not being transparent and so on. In a world where software is already pervasive and where the internet is connecting individuals all over the world, software transparency seems to be not only a remote possibility but something we will have to deliver sooner than many have thought. This paper aims at showing that trust is one of the important features to achieve transparency although this trust can be sometimes misleading.

Late Requirements and Architecture

6 - Modularizando Modelos i*: uma Abordagem baseada em Transformação de Modelos. Marcia Lucena, Carla Silva, Emanuel Santos, Fernanda Alencar, Jaelson Castro. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 33 - 44. [pdf] [scholar] Downloads: 481

Abstract: Este artigo apresenta uma estratégia para melhorar a modularidade dos modelos i* baseada na separação de interesses. São propostos um processo e um conjunto de regras de transformação para gerar modelos mais modulares.

7 - Descubriendo la Arquitectura de Sistemas de Software Híbridos: Un Enfoque Basado en Modelos i*. Juan Pablo Carvallo, Xavier Franch. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 45 - 56. [pdf] [scholar] Downloads: 440

Abstract: La mayoría de sistemas de software modernos se construyen integrando componentes de diversa naturaleza (comerciales, código libre, componentes legados, etc.), formando arquitecturas híbridas. La construcción de este tipo de sistemas se caracteriza por la adquisición de diversos componentes a proveedores externos a la organización que se integran con algún software hecho a medida. La correcta aplicación de este enfoque requiere la temprana identificación de los servicios que el sistema deberá brindar y su agrupación en dominios atómicos (los actores del sistema), que serán posteriormente remplazados de una manera “oportunista”, por los componentes más apropiados, independientemente de su naturaleza y origen. En este artículo abordamos este aspecto y proponemos un método basado en la utilización de modelos i*, que permite identificar los actores del sistema y su estructuración en una arquitectura de partida. El método es ilustrado con un caso práctico en una empresa de telecomunicaciones.

8 - UM PROCESSO DE VALIDAÇÃO DE REQUISITOS NÃO-FUNCIONAIS BASEADO NO NFR-FRAMEWORK. Anselmo de Araujo Couto, Luiz Eduardo Galvão Martins. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 57 - 62. [pdf] [scholar] Downloads: 651

Abstract: This paper presents a proposal to validate non functional requirements based on the NFR-framework. Our aim is to offer a systematization to validate nonfunctional requirements, analyzing its evolution and the quality of the original document specification regarding the non-functional requirements. In order to achieve that we tested the systematization in 3 (three) documents of requirement specification for distinct systems, although in this paper only one is referred. The studies followed the proposed activities step-bystep. The case was applied in a requirement document specified for software of requirements management. The finding results allows us to verify that: a) the proposed process serves as instrument of quality improvement during the non-functional requirement validation; b) the process assists the requirements engineers to develop a refinement of non-functional requirements, identifying system properties that were previously obscure.

Requirements Elicitation and Management

9 - Explicitar Requisitos del Software usando Escenarios. Graciela Hadad, Jorge Doorn, Gladys Kaplan. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 63 -74. [pdf] [scholar] Downloads: 678

Abstract: Los escenarios describen situaciones del proceso del negocio, tanto del proceso observable actual como del proceso proyectado o futuro. En este último caso los escenarios resultan ser contenedores de la mayoría de los requisitos del sistema de software, pero no son los requisitos propiamente dichos. Muchas de las buenas prácticas o prácticas recomendadas en el proceso de desarrollo de software se basan en la existencia de un documento de requisitos en el que éstos se individualizan en forma precisa. En el presente artículo se presenta una estrategia para confeccionar un documento de requisitos a partir de escenarios ya construidos. La particularidad que presenta la misma es que los requisitos individualizados tienden a ser libres de conflictos y de ambigüedad a consecuencia del propio proceso de producción.

10 - Facilitando la Asignación de Prioridades a los Requisitos. Graciela Hadad, Jorge Doorn, Marcela Ridao, Gladys Kaplan. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 75 -84. [pdf] [scholar] Downloads: 595

Abstract: Existe una gran variedad de propuestas y estándares internacionales que ofrecen guías de contenido y estilo para la generación de un documento de especificación de requisitos (SRS). Adicionalmente, la literatura da cuenta de diversos métodos para asignar prioridades a los requisitos, que parten de un conjunto de requisitos perfectamente individualizados, frecuentemente plasmados en un SRS. En este artículo se presenta una estrategia alternativa para asignar prioridades a los requisitos, que se apoya en el proceso previo que les dio origen: su derivación desde escenarios y la descomposición de objetivos en subobjetivos.

11 - Una Propuesta Metodológica para Modelar Procesos de Negocio de Decisión como Técnica de Elicitación de Requisitos para Sistemas de Business Intelligence. Aldo Quelopana Retamal, Vianca Vega Zepeda, José Gallardo Arancibia, Claudio Meneses Villegas. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 85 - 90. [pdf] [scholar] Downloads: 782

Abstract: Entre las etapas de la Ingeniería de Requerimientos, una de las más complejas es la de Elicitación, por la dificultad propia que existe en el proceso de traspasar las necesidades y expectativas del futuro usuario de un sistema, al analista del sistema en desarrollo. Esta dificultad se incrementa cuando el sistema en desarrollo no es transaccional, sino un sistema de apoyo a la toma de decisiones. Como respuesta a esta problemática, en el presente trabajo se introduce y define el concepto de proceso de negocio decisional, el cual considera la toma de decisiones como un proceso más a ser modelado, y se propone una heurística basada en la Notación de Modelado de Procesos de Negocio (BPMN) para llevarla a cabo.

Requirements Specification and Management

12 - Research Findings on Empirical Evaluation of Requirements Specifications Approaches. Nelly Condori-Fernandez, Maya Daneva, Klaas Sikkel, Roel Wieringa, Oscar Dieste, Oscar Pastor,. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 121 - 128. [pdf] [scholar] Downloads: 404

Abstract: Numerous software requirements specification (SRS) approaches have been proposed in software engineering. However, there has been little empirical evaluation of the use of these approaches in specific contexts. This paper describes the results of a mapping study, a key instrument of the evidence-based paradigm, in an effort to understand what aspects of SRS are evaluated, in which context, and by using which research method. On the basis of 46 identified and categorized primary studies, we found that understandability is the most commonly evaluated aspect of SRS, experiments are the most commonly used research method, and the academic environment is where most empirical evaluation takes place.

13 - OpenReq: uma Ferramenta para Auxílio à Gerência de Requisitos. Claiton Luís Grings, Miriam Sayão. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 129 - 138. [pdf] [scholar] Downloads: 1087

Abstract: The activity of requirements specification demands considerable efforts from professionals that execute it. To accomplish the activity, it’s not enough to obtain the requirements with customers. It is necessary to have a clear and complete understanding of customer’s necessities. Considering the issues associated to requirement’s registration and management, and the necessity of process’s optimization during product’s conception, the OpenReq tool was developed. The objective of OpenReq is to offer the possibility of requirements managements through an automated tool that is different from the other tools because it is open source and consequently, doesn’t have monetary costs for its utilization. The OpenReq was developed to Web platform, enabling the decentralized management of software requirements in just one base. The creation of this tool looks for the stimulation of the adoption of requirement management practices for small and medium companies and contribute with open source development community too, using open source technology.

Traceability and Product Lines

14 - Towards a requirements reuse method using Product Line in distributed environments. Thais Ebling, Jorge Luis Nicolas Audy, Rafael Prikladnicki. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 91 - 102. [pdf] [scholar] Downloads: 430

Abstract: Distributed Software Development (DSD) is a recent approach where the teams are geographically distributed. Some characteristics of these environments have significant impact in activities that require constant communication, shared vision and stakeholder’s cooperation, as we have in Requirements Engineering (RE). The goal of this paper is to present a requirements reuse method that integrates software reuse in the context of Product Lines (PL), to improve the RE in a DSD environment.

15 - A Systematic Process for Defining Meshing Tool Software Product Line Domain Model. Pedro O. Rossel, María Cecilia Bastarrica, Nancy Hitschfeld-Kahler. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 103 - 114. [pdf] [scholar] Downloads: 443

Abstract: Once an organization decides to develop a software product line (SPL), one of the first activities that needs to be done is to build a domain model. Here, commonalities and variabilities are identified, as well as the particular characteristics that products of the SPL will have. Although there exist some methods proposed for domain modeling, they are general and not specifically designed for scientific software, let alone for meshing tools. Meshing tools are highly complex software for generating and managing geometrical discretizations. Due to this complexity, they have generally been developed by end users with ad-hoc methodologies and not applying well established software engineering practices. Nevertheless, many meshing tools with varying degrees of variability have been developed over the years, making them a good application domain for SPL. This paper proposes a systematic process for building the domain model, specially suited for the case of a meshing tool SPL. We formally define the structure of the domain model, the process for building this model in a rigorous way, and we apply it to produce a meshing tool domain model. Both, the model and the process, are described and exemplified along the paper.

16 - Uma Avaliação sobre Rastreabilidade de Software no Contexto do MPS.BR. Marcelio D’Oliveira Leal, Sandro Ronaldo Bezerra Oliveira, Cleidson Ronald Botelho de Souza. Anais do WER09 - Workshop em Engenharia de Requisitos, Valparaíso, Chile, Julho 16-17, 2009, pp 115 - 120. [pdf] [scholar] Downloads: 853

Abstract: The need to increase the productivity and competitiveness among software development organizations has demanded additional quality from these companies. Thus, the adoption of a processes quality model is a growing activity, mainly with the creation of the MPS.BR model, the Brazilian program for software process improvement. In this context, an activity that increases the quality and is basic is the software traceability. This paper presents an overview about the software traceability activity, one of the expected results of the requirements management in the MR-MPS.BR.

  voltar