Generating Requirements Views: A Transformation-Driven Approach

This paper reports the use of transformations based on XML to generate requirements views. A strategy to generate views is defined and scenarios and class diagrams are automatically created from a goal oriented model; the V-graph

The impacts of non-functional requirements in web system projects

In web system development, the Non-Functional Requirements (NFRs) are typically considered only briefly during the requirements elicitation stage and not rigorously articulated by either web developers or the client. This paper reports on an investigation into this issue involving interviews with web developers who were engaged in commercial web development projects. The results from this qualitative research highlight that web developers commonly do not pay sufficient attention to NFRs. This arises due to uncertainty, lack of time, lack of knowledge in the importance of NFRs and partly because NFRs are not readily available and documented from previous similar projects. Web developers also do not elicit NFR at the same time and at the same level of details as Functional Requirements (FRs). This study highlights that exploring the domain at an early stage of development will help developers to better understand NFR. A lack of rigour in articulating NFRs may significantly impact on the development effectiveness and the quality of the resulting web system. An evaluation of NFRs may also lead to discovering new FRs. © Copyright 2008, Inderscience Publishers

A Systematic Classification and Analysis of NFRs

The main agenda of Requirements Engineering (RE) is the development of tools, techniques and languages for the elicitation, specification, negotiation, and validation of software requirements. However, this development has traditionally been focused on functional requirements (FRs), rather than non-functional requirements (NFRs). Consequently, NFR approaches developed over the years have been fragmental and there is a lack of clear understanding of the positions of these approaches in the RE process. This paper provides a systematic classification and analysis of 89 NFR approaches

Selecting Communication Artifacts for Requirements Engineering

In this paper, we identify and explicate the factors that lead organizations to select particular communication artifacts in the requirements engineering (RE) process and to determine the communication artifacts that they prefer in particular RE phases and with which RE methods. We do so to improve RE communication. Information systems (IS) projects often fail due to poorly specified or misunderstood requirements. We articulate a process framework for RE, which serves as a basis for our discussing and analyzing RE communication artifacts. In doing so, we extend the RE process by adding two transitional phases (pre-validation and pre-approval) to ensure that organizations identify all of the essential requirements. We employ qualitative methods to identify the criteria for selecting communication artifacts. We discover that organizational culture plays a key role in this process. Our findings suggest that the traditional phases occur more in organizations that use waterfall development processes than in organizations that agile development methods

Aplicando una estrategia de mejora que incluye conceptos de requisitos funcionales y no funcionales

Organizations should set and reach business goals for varied purposes using the suitable strategies. Basically, a strategy specifies the activities, methods and another related resources that should be considered in order to achieve a given goal purpose. Goal purposes and their associated strategies can aim at evaluating, testing, developing, or maintaining some entity. Some concrete evaluation purposes such as to understand or monitor can be achieved by strategies embracing non-functional requirements definition, measurement, evaluation and analysis activities. Other specific evaluation purposes such as to improve or control also imply changing the target entity; therefore, strategies should embrace functional requirements definition activities as well. Moreover, specific development and maintenance purposes always involve functional requirements. In this work, we relate business and information need goals with functional and nonfunctional requirements concepts, which are paramount for well-defined strategies. Therefore, we specify vocabularies for them, and illustrate the applicability of an improving strategy –which embeds these concepts- in the context of a running example. Having well-structured vocabularies serving as common ground for diverse strategies may promote a more effective operationalization of projects dealing with evaluation, testing, development and maintenance goal purposes.Las organizaciones deben establecer y alcanzar metas de negocio para diferentes propósitos utilizando las estrategias adecuadas. Básicamente, una estrategia especifica las actividades, los métodos y los recursos relacionados que deben considerarse para lograr un determinado propósito. Los propósitos de las metas y sus estrategias asociadas pueden apuntar a la evaluación, prueba, desarrollo o mantenimiento de alguna entidad. Algunos propósitos específicos de evaluación, como comprender o monitorear, pueden lograrse mediante estrategias que abarcan actividades de definición de requisitos no funcionales, medición, evaluación y análisis. Otros propósitos de evaluación, como mejorar o controlar, implican además cambiar la entidad o su contexto; por lo tanto, las estrategias también deben incluir actividades de definición de requisitos funcionales. En cuanto a los propósitos específicos de desarrollo y mantenimiento, estos siempre implican requisitos funcionales. Este trabajo relaciona las metas de negocio y de necesidad de información con conceptos de requisitos funcionales y no funcionales, que son fundamentales para estrategias bien definidas. Por lo tanto, especificamos sus vocabularios e ilustramos la aplicabilidad de una estrategia de mejora –la cual embebe estos conceptos- mediante un ejemplo que desarrollamos a lo largo de las secciones. Tener vocabularios bien estructurados que sirvan de base común para diversas estrategias puede promover una operacionalización más efectiva de los proyectos que tienen que ver con propósitos de metas de evaluación, prueba, desarrollo y mantenimiento.Facultad de Informátic

25 years of Requirements Engineering in Brazil: a systematic mapping

Abstract. The celebration of 25th anniversary of the Brazilian Symposium of Software Engineering (SBES) as well as the forthcoming Requirements Engineering Conference to be held in Brazil for the first time, has led us to have a closer look at the local Requirements Engineering (RE) Community. A systematic mapping was performed in order to find out the main Brazilian research groups, authors as well as their topics of interest and publications with greatest impact. This information may be useful for those that do not know well the local requirements engineering community, such as local newcomers or foreign researchers. It may also help to identify potential groups for collaboration. Similarly, it may provide valuable information to assist local agencies when granting research funds