Anais da. Primeira Escola Latino America de Engenharia de Software ELA-ES Volume II Sessão de Estudantes. PUC-Rio, Rio de Janeiro, Brasil

Transcrição

1 PUC! Anais da Primeira Escola Latino America de Engenharia de Software ELA-ES 2013 Volume II Sessão de Estudantes PUC-Rio, Rio de Janeiro, Brasil 9 a 12 de Julho de 2013 Departamento de Informática PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO RUA MARQUÊS DE SÃO VICENTE, CEP RIO DE JANEIRO - BRASIL

2 Organização Coordenador Geral Carlos José Pereira de Lucena (PUC-Rio, BR) Coordenadores de Programa Alessandro Garcia (PUC-Rio, BR) Nelly Bencomo (Aston University, UK) Coordenadores de Organização Ingrid Oliveira de Nunes (UFRGS, BR) Bruno Barbieri de Pontes Cafeo (PUC-Rio, BR) Coordenadores da Sessão de Estudante Elder José Reioli Cirilo (PUC-Rio, BR) Bruno Barbieri de Pontes Cafeo (PUC-Rio, BR) Eiji Adachi Medeiros Barbosa (PUC-Rio, BR) Coordenador do Painel da Indústria Isela Macia Bertran (General Electric Global Research, BR) Coordenador Financeiro Francisco Dantas de Medeiros Neto (UERN, BR) Coordenador de Publicidade Vanius Zapalowski (UFRGS, BR) Organizadores Locais Davy Baía (PUC-Rio, BR) Carolina Valadares (PUC-Rio, BR) Eiji Adachi Medeiros Barbosa (PUC-Rio, BR)

3 Supporting Requirements Engineering Processes in Small Software Enterprises Alcides Quispe, Sergio F. Ochoa Computer Science Department, Universidad de Chile, Santiago, Chile {aquispe, Abstract. Selecting software development practices according to the features of the project to address, has been emphasized as relevant research topic by the software engineering community. A one-size fits-all approach does not work for software development in general, and also to perform the Requirements Engineering (RE) activities. RE practices play an important role in the success of a software project, particularly when they are run by Small Software Enterprises (SSEs), due these organizations are usually fragile in terms of human, technological and economic resources. Therefore, selecting the most appropriate RE practices according to the project features, tends to be mandatory for them. Although several RE practices have been included in software processes proposed for SSEs (e.g. ISO/IEC 29110, MoproSoft, MPS.BR, Tutelkan Reference Process, REPM, Uni-REPM, and OWPL), it is difficult to identify which RE practices are specifically appropriate to address specific projects. The current proposals do not provide guidelines to support this selection of RE practices. Trying to address this problem, this thesis work has developed a general RE process that embeds a minimal set of RE best practices and includes variability points. This process can be tailored according to the project characteristics, which have been captured through a project context meta-model. It includes several project attributes (e.g. project type, application domain, customer type, project duration, etc.) that they have been obtained from the empirical observation of various SSE in Chile. Once developed the RE general process for SSE, we used a MDE tailoring approach to support the adaptation of the RE process according to the characteristics of particular projects. Two types of scenarios were used as support for the development and validation of the proposed approach: a) an academic scenario, where real software projects are undertaken by undergraduate students of the fifth year of Computer Science at the Universidad de Chile; and b) a software industry scenario, where four Chilean SSEs (that are part of the ADAPTE research project: contributed in this research. The preliminary results indicate that the eighteen practices embedded in the RE general process are good enough to cover the RE practices needed for project types usually developed by SSEs. Considering that SSEs represent an important percentage of the software industry in Latin America, as elsewhere in the world (88% in Chile; 70% in Brazil; 78% in Canada; 94% in the USA; and 91% in Finland), the results of this research work could have a major impact. Keywords: Requirement Engineering Practices, Requirement Engineering Process, Small Software Companies, Software Process Tailoring.

4 Analyzing Architectural Properties During Design of Architectures Using SysML Models Daniel Cunha da Silva, Jair Cavalcanti Leite Department of Computer Science and Applied Mathematics (DIMAp) Federal University of Rio Grande do Norte (UFRN) Abstract. Decisions to design software architectures of software-intensive systems are driven mainly by functional and non-functional requirements. Requirements have a significant impact on the overall structure of the architecture. Thus, the decisionmaking performed by architects for tradeoff between different requirements is not, in most cases, a trivial task. This problem is recognized by the literature that says there is currently a lack of tools or techniques to assist the architect in this sense, and when there are, many of them are carried out on an ad hoc or through non-integrated methods. In order to assist the design activity and solve the problem mentioned above, this work presents a way to anticipate possible conflicts among non-functional requirements occasioned by architectural decisions taken by analyzing the properties of the architecture. To assist in this analysis were used software metrics associated with the properties. The idea is to verify that during the design of architecture, the decisions are taken that, consequently, generate adjustments in the architectural properties, affect the non-functional requirements. This effect can be measured by a metric associated with such architectural properties. Currently, work has raised the following architectural properties: number of elements, number of ports, number of connections, coupling and introducing security mechanisms. These properties, which are not unique to particular requirement, impact the requirements for performance, security, maintainability and modifiability, and their respective measured by software metrics. In order to extract the architectural properties evaluated in architecture, this paper uses the modeling language SysML, which is a general purpose language that includes information about hardware, software, processes and stakeholders, extended UML. It allows modeling the behavior and design of a system and its environment, and its relationship with non-functional requirements using constraints and parameters. In this approach we use SysML to include the specification of requirements and traceability relationships between architectural elements that fit into our purpose. SysML allows the representation through notes and use the requirements diagram, architectural properties as derived requirements. The work was implemented as proof of concept in a web system for evaluating postgraduate courses developed by UFRN. The study showed that, through the use of SysML, changes in architectural properties affected their nonfunctional requirements of the system, assisting architects in decision-making. It was also verified that the analysis was facilitated by the use of SysML. As future work we intend to identify other architectural properties of other non-functional requirements and applying SysML to represent other elements involved in the design activity, such rationales, architectural patterns and styles, among others. Keywords: Non-functional requirements, architectural properties, decision-making and SysML.

5 Tecnologias Facilitadoras de Aprendizagem Organizacional em Programas de Melhoria de Processo de Software Davi Viana e Tayana Conte Instituto de Computação Universidade Federal do Amazonas (UFAM) {davi.viana, tayana}@icomp.ufam.edu.br Resumo. A Melhoria de Processo de Software (MPS) tem se tornado uma estratégia constante em organizações para aumentar a qualidade dos seus produtos. Essas organizações partem da premissa que a qualidade do software pode ser elevada devido ao aumento da qualidade do processo de desenvolvimento. Contudo, é preciso criar mecanismos que institucionalizem a melhoria contínua dos processos. Esses programas envolvem diversos conhecimentos que podem ser novos para os membros da organização. Um programa de MPS não deve ser visto como esforço único, mas sim como algo evolutivo necessitando, assim, de constante aprendizagem. Desta forma, busca-se focar no seguinte questão de pesquisa: Como facilitar a aprendizagem organizacional em programas de Melhorias de Processo de Software?. A aprendizagem organizacional é um processo de aperfeiçoar ações por meio de compreensão e conhecimento, ampliando os conhecimentos existentes. Além disso, a aprendizagem organizacional consiste em uma série de interações entre a adaptação no nível individual (ou de subgrupo) e adaptação no nível organizacional. Pesquisas tem sido realizadas buscando apoiar organizações que aprendem no contexto de aplicação, evolução e desenvolvimento de software. Essas pesquisas utilizam mecanismos tecnológicos para apoiar a aprendizagem, como wikis e sistemas de gerenciamento do conhecimento. Contudo, somente a tecnologia não é suficiente, uma vez que as pessoas estão no centro do processo de aprendizagem, pois são elas que criam e compartilham o conhecimento. Desta forma, esta proposta de Doutorado visa pesquisar tecnologias (técnicas, métodos, processos e ferramentas) que apoiem a aprendizagem organizacional em programas de MPS do ponto de vista dos profissionais de software, contando com as seguintes inovações: identificação do ciclo de vida das lições aprendidas/conhecimento da organização; questões que podem influenciar positivamente e negativamente a aprendizagem organizacional em MPS; identificação e avaliação de meios de transferência do conhecimento. Como resultados obtidos até o momento, tem-se uma revisão sistemática da literatura (RSL), onde foi possível identificar formas de disseminar o conhecimento em organizações de software. A revisão permitiu identificar também fatores que influenciam no compartilhamento de conhecimento, como a influência das comunidades de prática e treinamentos. Adicionalmente, foi realizado um estudo qualitativo que analisou como as lições aprendidas de projetos são compartilhadas na organizações. A partir dos resultados da RSL, serão criados modelos visuais das tecnologias disponíveis com o objetivo de identificar melhores formas de facilitar a aprendizagem organizacional em organizações de software. Em seguida, as tecnologias identificadas e as novas tecnologias propostas serão validadas através de diferentes Estudos Experimentais em Engenharia de Software e irão compor o arcabouço de tecnologias facilitadoras. Espera-se que essas tecnologias integrem-se às atividades do programa de MPS promovendo meios de aprendizagem dos conhecimentos necessários. Palavras-chave: Melhoria de Processo de Software, Aprendizagem Organizacional, Engenharia de Software Experimental.

6 MoDre4CLouD - A Framework for Agile Requirements Modelling for Cloud Computing Fernando Wanderley 1 1 Departamento de Informática Faculdade de Ciências e Tecnologia Universidade Nova de Lisboa (FCT/UNL), Lisboa, Portugal. f.wanderley@campus.fct.unl.di, p191@fct.unl.pt Abstract. The complexity and social impact of emerging technologies is dramatically growing and poses new challenges to many engineering disciplines. Requirements Engineering (RE) is not an exception, and will be our target one. Among these emerging technologies we highlight the strong growth of Cloud Computing (CC) adoption. CC represents a fundamental shift on how cloud applications need to be built and run. The different nature of cloud application development will drive changes in software development process frameworks, which will become more agile and practice-oriented. So, the traditional requirements models need to be flexible enough making them able to adapt quickly to environment dynamic behaviour changes (e.g. CC environment) especially related to context-aware systems. Another important factor is that there is much less work covering the usage of MDD for early requirements models in general and mainly for cloud requirements models in particular. It would be desirable to integrate dynamically and consistently these requirements to cloud architecture. More recently, models for requirements at runtime have been developed, aiming at managing the complexity of evolving software behavior while it is executing. Other works proposes an approach for the design of adaptive systems based on requirements and inspired in control theory to monitor its requirements at runtime. Other proposals focus on requirements adaptive systems. KAOS-based proposals use linear temporal logic to specify requirements. For example, RELAX is based on SHALL statements and fuzzy branching temporal logic, which is also more complex than the approach we propose. Tropos-based proposals use the Belief-Desire-Intention model as reference architecture for cloud systems. Therefore, the main goal here is to propose an Agile Requirements Modelling Framework for Cloud Systems (MoDrE4Cloud), flexible (autoconfiguration) and able to represent a set of dynamic variations in the context of cloud systems architecture. The main components of this framework are: (i) Agile requirements elicitation with Mind Map Modelling used as a seed for generation of Goaloriented models; (ii) Composition (Safe) of Partial goal Models representing the variabilities of goals and soft-goals; (iii) and then the architectural derivation from these models by MDD techniques. As the main contributions, we ll have: (i) The representation of variability of goals through partial goal-oriented model definition; (ii) the formal definition of the dynamic composition of these partial models to represent more flexible dynamic behavior; (iii) an agile process of generating these partial models through Mind Maps adoption; (iv) finally, to develop MDD techniques to build early RE models for cloud applications and from them derive architectural models. Keywords: Goal-Oriented Requirements, Model-Driven Engineering, Agile Requirements Modelling, Cloud Computing, Software Architecture.

7 Providing real-time decision support in flood management using volunteered information Flávio E. A. Horita 1, João Porto de Albuquerque 1 1 Department of Computer Systems, ICMC/USP University of São Paulo (USP) {horita, jporto}@icmc.usp.br Abstract. The recent catastrophic events in Haiti, Pakistan and Chile in 2010, Queensland in , Christchurch and Japan in 2011 and the United States in , highlighted the growing problem of natural disasters and the numerous economic and social damages caused. Within this context, floods have an important role, they occur when the water level exceeds its usual state, causing significant losses for both residents and governments of the affected region. As a result, the Flood Management (FM) acquires pronounced importance as a measure of adaptation to climate change and the consequent increasing frequency in the occurrence of floods. Thus, FM is composed by three phases, pre-flood planning, emergency management and post-flood, all these phases aims to execute activities to improve the capacity of communities on resist to changes or adapt in order to achieve a new level of functioning or structure. In all its phases, information plays a key role in ensuring the reduction of impacts. Therefore, it is important that there are accurate, timely and complete information about the current state of environmental, social, structural and economic variables. Geographical information is particularly important in this context, since environmental changes and floods are always bound to a geographical context. Thus, Spatial Decision Support Systems (SDSS) can be important technological resources. These are interactive systems designed to support one or more users in making decisions in a semi-structured decision context. SDSS thus integrate technologies related to Geographic Information Systems (GIS) with the features of Decision Support Systems (DSS). However, these traditional systems in most cases use static and limited data to simulate or help on the decision-making. Thus, it becomes necessary to develop procedures for their modification in accordance with changing conditions in the local emergency. In this context, VGI (Volunteered Geographic Information), i.e. information provided by the local population, who are smart, familiar with the area and equipped with appropriate devices, presents itself as an alternative to provide rich and updated information in order to facilitate community organization and reaction measures of official agencies. Nevertheless, these voluntary information create a huge number information that highlight issues related with its, credibility, quality and integration. In this sense, this proposal aims to develop an approach to support the process of decision making in FM exploring the integration of VGI and SDSS focused on increasing the capacity of prevention, control and response of communities affected by floods. Among its expected results, we highlight the development of software tools and processes to integrate of available data, increase and analyze the quality of volunteer information and support the decision making process by community members, agencies and official organizations. Keywords: Spatial Decision Support Systems, VGI, Floods Management, Decision Support Systems, Crowdsourcing.

8 Do Language Constructs for Concurrent Execution Have Impact on Energy Efficiency? Gustavo Pinto 1 and Fernando Castor¹ 1 Centro de Informática Universidade Federal de Pernambuco (UFPE) ghlp@cin.ufpe.br, castor@cin.ufpe.br Abstract. Multicore applications can use many different approaches to manage parallel execution. These techniques have different trade-offs in terms of performance and generality. In this study, we present an approach that aims analyze whether taking energy consumption into account creates additional trade-offs. Furthermore, since parallel programming enables programmers to run their applications faster, a common belief is that this application will also consume less energy. We call this as the Race to idle philosophy. In summary: faster programs will consume less energy because they will have the machine idle fast. In this poster, we demonstrate that it could not be necessarily true, at least for concurrent systems. Our study has analyzed the performance and energy consumption of three benchmark applications written in Java and Scala, using a number of techniques to manage parallel execution. We ran these experiments in a number of different configurations while varying a group of attributes (the number of threads in use, the JVM implementation and the clock frequency), in order to verify if these changes have impact on the application energy consumption, energy efficiency and performance. Our study shows that these factors could create great variations. For example, for a CPU-bound problem, the ForkJoin framework can perform better while using less energy. At the same time for a heavily IO-bound problem, it can consume about 10% more energy than a sequential implementation, although still 30% faster. Other techniques have great differences as well, and no single solution was the best in all aspects. Moreover, our experiments show that factors such as the nature of the problem to be solved, the CPU clock frequency, and the JVM implementation can create variations. The general conclusion that we can draw from this study is that yes, language constructs for parallel execution can impact energy consumption. Our approach indicates that it is possible to switch from one technique to another in order to consume less energy. These results lead us to conclude that it is very difficult to generalize a relationship between performance and energy consumption for concurrent systems. For these systems, winning the race to idle does not imply in more energy efficiency. This study is a step towards a better understanding of the interplay between energy efficiency and performance. Currently, however, it would still be very difficult to organize this information in a catalog. In the future, we intent to address this problem by conducting a broader-scoped study. The results of this new study will provide input for us to derive a catalog of energy code smell for concurrent software. Then we plan to proceed with the design of refactoring catalog that will enable application programmer to safely restructure their applications to use less energy. Keywords: Energy-Efficiency, Language Constructs, Parallel Execution

9 Agrupamento Automático de Solicitações de Manutenção Henrique S. C. Rocha 1, Marco Túlio de Oliveira Valente 1 1 Departamento de Ciência da Computação Universidade Federal de Minas Gerais hscr@ufmg.br, mtov@dcc.ufmg.br Resumo. Manutenção de software é uma das fases mais relevantes no ciclo de vida de projetos de software. Alguns estudos apontam, por exemplo, que essa fase pode representar até 80% dos recursos alocados durante o ciclo de vida de um sistema. Tipicamente, tarefas de manutenção são criadas a partir de requisições dos usuários de um sistema. Entretanto, em diversos sistemas, requisições de manutenção são tratadas de forma ad-hoc e isolada, à medida que as mesmas são criadas em um sistema de gerenciamento de issues, como Bugzilla. Essa política contínua para tratamento de manutenções tem como desvantagem o fato de não propiciar ganhos de escala, que ocorrem tipicamente quando requisições individuais são agrupadas, gerando-se projetos de manutenção de software. Em outras palavras, uma abordagem mais adequada consiste no agrupamento de diversas requisições de usuários durante um determinado período de tempo, com a consequente criação de projetos de manutenção. Se esses projetos incluírem requisições similares, então os desenvolvedores poderão implementá-los de uma forma mais rápida e ágil. Como benefício final, tais políticas podem propiciar uma e- conomia de escala se comparadas ao tratamento clássico tradicional. No entanto, uma dificuldade de abordagens periódicas é que elas dependem de uma autoridade com conhecimento global sobre todo desenvolvimento do software, a qual será como responsável pela criação anual dos projetos de manutenção. O estabelecimento de tal autoridade é particularmente complexa em projetos código-aberto. Assim, o principal objetivo desse trabalho é propor uma abordagem automática e não-supervisionada para criação de projetos de manutenção agrupando requisições semanticamente similares. A abordagem proposta funciona conforme descrito a seguir: (i) cada requisição é inicialmente pré-processada usando-se técnicas de processamento de linguagem natural, para, por exemplo, remover stop-words, tratamento de stemming, etc; (ii) dada uma nova requisição, se ela for semanticamente similar àquelas contidas em um projeto de manutenção ainda em aberto, então ela será alocada ao mesmo; (iii) caso contrário, cria-se um novo projeto para essa requisição. No estágio atual do trabalho, usa-se a similaridade do cosseno para verificar a similaridade entre as descrições textuais de duas requisições de manutenção. Por fim, cada projeto de manutenção fica aberto por um período de tempo pré-definido. Após esse período, o projeto é fechado e designado para uma equipe de desenvolvimento. Para testar e avaliar a abordagem, estamos criando um dataset sobre requisições de manutenção em sistemas de código aberto. Para validar a qualidade dos projetos propostos por nossa solução, pretende-se adotar uma variação do coeficiente de Jaccard, com o objetivo de expressar a existência de arquivos modificados em comuns pelas requisições incluídas em cada projeto. Se existirem muitos arquivos em comum, então isto é uma evidência de que nossa abordagem é capaz de introduzir ganhos efetivos de escala no tratamento de manutenções de software. Palavras-chave: Manutenção de Software; Mineração de Texto; Economia de escala.

10 Evidence of Software Inspection on Requirement Specification for Software Product Lines Iuri Santos Souza 1,3, Gecynalda Soares da Silva Gomes 1, Ivan do Carmo Machado 1,3, Paulo Anselmo da Mota Silveira Neto 2,3, Eduardo Santana de Almeida 1,3,4, Silvio Romero de Lemos Meira 2,3 1 Math Institute - Federal University of Bahia (UFBA) 2 Center for Informatics - Federal University of Pernambuco (UFPE) 3 Reuse in Software Engineering Group (RiSE), Brazil 4 Fraunhofer Project Center (FPC) for Software and Systems Engineering, Brazil iurisin@dcc.ufba.br, gecynalda@yahoo.com, ivanmachado@dcc.ufba.br, pamsn@cin.ufpe.br, esa@dcc.ufba.br, srlm@cin.ufpe.br Abstract. Requirement engineering is the discipline responsible for capturing, specifying, and detailing the software and systems requirements, and their behaviors and interactions. In Software Product Line (SPL) engineering, it is also responsible for capturing, specifying, and detailing the variations. Requirements are usually specified in natural language, which might lead to issues such as ambiguity, inconsistency, omissions, and lack of clarity. This poster reports on a portion of the analysis of the effects of applying an inspection approach in the specification of functional requirements, in the light of an industrial SPL project, in which the inspection team assessed one hundred and forty-four requirements. We performed an empirical study in order to investigate and identify correlations, tendencies, define predictive models and estimate non-conformities. The results showed that issues of completeness and ambiguity presented the highest non-conformity occurrences, and that the inspection meeting was the task, which demanded most effort. Errors coming from domain knowledge understanding, specification, and organization, were the main responsible for the non-conformities. This poster is a good opportunity to show and discuss practical and open issues revealed by the industrial study and also it can raise questions for other contributions. This work is a step toward a precise guide for the inspection activity in SPL, and interesting directions can be revealed from the work started here. Keywords: Software Product Line Engineering; Requirement Engineering; Software Inspection; Causal Analysis; Experimental Study

11 Fault Model-Based Variability Testing Ivan do Carmo Machado, Eduardo Santana de Almeida Computer Science Department Federal University of Bahia (UFBA), Salvador, BA, Brazil Abstract. Software Product Line (SPL) engineering has emerged as an important strategy to cope with the increasing demand of large-scale products customization. Owing to its capability of systematically reusing software artifacts, SPL has provided companies with an efficient and effective means of delivering products with higher quality at a reduced cost, when compared to traditional software engineering strategies. However, such a benefit does not come for free. SPL demands cost-effective quality assurance techniques that attempt to minimize the overall effort, while improving fault detection rates. Software testing, as one of the most important quality assurance techniques, have been largely explored to address this particular topic. An extensive analysis of existing techniques showed us that current SPL testing practices are mainly focused on handling variability at a higher level of abstraction, e.g., through the analysis of feature models, rather than carrying out about issues faced at the source code level. However, we believe that improvements in fault detection rates for variability testing in an SPL entail a more in-depth attention, that is, one should care about the variability implementation mechanisms particularities, which traverses abstractions at source code level. In this effect, this work analyzes the most occurring problems in variability implementation, aiming at constructing a fault model for variability testing, to serve as a driver for test case generation. Our research goal is to analyze the test effectiveness improvements enabled by the use of fault models in variability testing. We intend to build a defect classification scheme for variability implementation, that consists of the synthesis of evidence from three main sources: literature analysis; analysis of open source repositories; and case studies involving the development of SPL projects. The resulting scheme will serve as a basis for the fault model that will emerge. We are currently underway on such synthesis of evidence. It has been supported by a series of empirical studies. The literature analysis aims at leveraging reports on commonly occurring error in the mechanisms. The analysis of open source repositories will aid in the identification of reported defects in variability implementation. Next, the case studies, involving the use of variability implementation mechanisms in three different programming languages, namely Java, C, and the ios platform, might strengthen our generalizations. We plan to build the fault model by looking at software projects developed in such different programming languages, and compare the outcomes, so as to enable further refinements. Keywords: Software product line engineering, software testing, variability testing, fault model, empirical software engineering.

12 Beauty Technology as an Interactive Computing Platform Katia Vega 1 Hugo Fuks 1 1 Departamento de Informática Pontificia Universidade Católica do Rio de Janeiro kvega@inf.puc-rio.br, hugo@inf.puc-rio.br Abstract. Wearables add more than physical, social and psychological variables. The accessibility, reliability and miniaturization of technology give the opportunity to embed sensors and actuators into wearables to increase the possibilities of interacting with the world. Nowadays we cannot think of Wearable Computers just as an exploration of the capabilities of devices into clothing but also about breaking through barriers of technology to make them useful to us in a way never imagined. This work introduces the term Beauty Technology as an emerging field in Wearable Computers. We propose the use of products on the skin surface that hides electronics, are easy to attach and remove, are ergonomic to the human body and highlight the wearer s personality. Imagine that you don't need a card for opening your office door, or for paying your bus ticket. Imagine that you don't need any ticket for entering to your show or movie session. Go and buy at the supermarket or rent a book at the library without any wallet or ID card, just point and have it, everything at the top of your finger: your nails. Beauty Technology Nails embed technology components into false nails in order to interact with the world in different ways and through different surfaces. They could create personalized gestures and musical instruments. These nails contain embedded magnets for amplifying the wearers capabilities by giving the sense of reading magnetic fields but also give them access to different objects with magnetic switches and interact with magnetic sensors. A RFID nails wearer made a secret combination of finger movements to open the door in the project called Abrete Sesamo. Aquadjing is another project that a Dj could change between different tracks by touching into the water with her RFID nails. Blinking is something fascinating. It acts by the natural movement of your eyes and also gives us the possibility to understand different physical or psychological illness just with blinking. Even more, we could make gestures or create our own ones. What if we are not just could understand blinking but also activate the world with just a blink? Beauty Technology proposes the use of makeup for understanding blinking and other face movements. We used conductive makeup that connects sensors and actuators by the use of conductive materials that stick to the skin as well-defined eyeliners and eyebrows. Removable tattoos were used as aesthetics lights on the body skin and for enacting with the world by skin capacitance sensitivity. We also used black false eyelashes that were chemically metalized to react to blinking. As an example, a character called Arcana is a futuristic angel that communicates by amplifying her blinking and creates gestures that activates different music tracks and displays different images. Superhero is another example of the conductive false eyelashes and makeup used to levitate objects just by blinking. Keywords: Beauty Technology, Wearable Computers.

13 A Methodology for the Elicitation of Usability Requirements in the Development of Web Applications Luis Rivero and Tayana Conte Instituto de Computação Universidade Federal do Amazonas (UFAM) Abstract. Non-functional requirements play a fundamental role in software development because they specify software restrictions and how well the software shall perform its function. Usability has been pointed as the most important type of nonfunctional requirement for guaranteeing software quality. In Web applications, usability is crucial because it can determine whether the application succeeds or fails due to its effects in the users productivity and satisfaction. Usability requirements describe needs for the outlined system, such as the ability to prevent errors and reduce mental workload. However, despite their importance, usability requirements are usually forgotten or unconsidered during the software development process. The main reason for this lack of attention to usability requirements is that the technologies (techniques, processes or tools) that have been proposed to address them, are usually applied late in the development, where it is too expensive to develop usability requirements or fix usability problems. In this doctorate project, we aim to provide a solution for the late identification of usability requirements in Web projects. We are proposing an approach that will integrate several technologies to understand the users needs and identify usability requirements in the beginning of the development process. First, we will perform a systematic literature review to understand the current state of the field of Web usability requirements, and identify research opportunities. We will use these results to propose a set of techniques for the elicitation of usability requirements that will allow software engineers to produce descriptive elicitation documents such as: textual specifications, mockups specifications and navigational models. Such documents will guide the development team through the implementation of Web applications meeting usability principals. Then, we will develop a tool support for the identification and validation of usability requirements, and a monitoring system to examine how users perform tasks in low fidelity prototypes in order to identify further usability requirements. Also, to evaluate and evolve our approach, we will follow a research methodology based on empirical studies. During feasibility studies, we will evaluate the set of technologies by comparing them with other technologies that have been proposed for similar purposes. Thus, we will perform quantitative analyses and measure the accuracy (number of correct usability requirements), effectiveness (percentage of elicited usability requirements), and efficiency (speed when performing the elicitation) of our approach. Also, the qualitative results from observational and industrial case studies will be used to improve the performance of our approach in order to be used in the software industry. Our goal is to provide our approach, allowing the software development industry to: (a) develop Web applications that are intuitive and easy to navigate; and (b) reduce the cost in the development of Web applications by addressing usability problems in the beginning of the development. Keywords: Usability; Requirements Elicitation Technologies; Elicitation Artifacts; Web Applications.

14 Predicting Requirements Based on Organizational Changes Marília Guterres Ferreira 1 Julio Cesar Sampaio do Prado Leite 1 1 Pontifícia Universidade Católica do Rio de Janeiro, PUC - Rio, Brasil {mferreira, julio}@inf.puc-rio.br Abstract. Software evolution is a fact in industry life. Most of the changes in softwarebased systems are caused by changes in organizations from their need to adapt to a more and more competitive and dynamic environment. Those changes costs are far higher than the initial software development costs. In those software evolution projects, most of the time the software has to be developed from scratch because the maintenance on the running system is very difficult and consequently expensive and time-consuming. This research comes from the realization that some of the problems could be avoided if some requirements could be elicited in advance. If when we develop new software systems, we try to anticipate the ways in which they might change, then the software can be modified more easily to implement the new requirements. As most changes in software come from organizational change, to be able to predict how the organization will evolve, we should first define what its current state is and then determine for which state it will go. In this context Organizational Semiotics seems to be a promising theory. Organizational Semiotics is a discipline that studies the use of signs and their effects on social practices. On this subject, there is Stamper s School which proposes a set of methods, MEASUR research program, to the design of information systems based on the social-technical paradigm, considering social, political, cultural and ethical issues involved in understanding the problem in the process of requirements engineering. The general objective of this research is defining a strategy to anticipate requirements change and consequently make the software evolution less traumatic, less expensive and in less time. For this, we propose a 5-steps preliminary method. First we define the current state of the organization in two steps, the problems and then the semantic and norms, based in methods from Organizational Semiotics, PAM, SAM and NAM respectively. Then, based on the changes that the system might cause in the organization, the steps 3 and 4 define the future state of the organization, i.e., the new problems and the new requirements, again supported by Organizational Semiotics. Finally, the software-based system to be develop should address the current needs and be prepared for the ones anticipated, thus the software evolution will be less difficult. The strategy presented in this study is incremental, once the current model is defined, the next steps determine what is needed to be added, excluded or modified. It is an epistemic tool that aims to help in the design of the problems and requirements of the organization, either in the present and in the future. The expected results are to make the software evolution process less difficult and in a shorter time. Keywords: Requirements Engineering, Software Evolution, Organizational Semiotics, Anticipating Requirements, Organizational Change.

15 ONTOREQ: Um Processo para Identificação e Classificação de Interesses em Documentos de Requisitos com base em Ontologias de Domínio Paulo Afonso Parreira Júnior 1,2, Rosângela Aparecida Dellosso Penteado 1 1 Departamento de Computação Universidade Federal de São Carlos (UFSCar) 2 Curso de Bacharelado em Ciência da Computação Universidade Federal de Goiás/Câmpus Jataí (CAJ/UFG) paulo_junior@dc.ufscar.br, rosangela@dc.ufscar.br Resumo. Um software produzido com qualidade deve possuir módulos específicos que agrupam um conjunto de requisitos relacionados (interesses). Entretanto, há alguns tipos de interesses para os quais essa clara alocação em módulos não é possível, apenas com a utilização das abstrações usuais de engenharia de software, tais como casos de uso, classes e objetos, entre outros. Tais interesses são denominados Interesses Transversais (ITs) e referem-se a requisitos de software que se encontram espalhados ou entrelaçados com outros requisitos, o que pode dificultar o desenvolvimento e a evolução do software. Exemplos clássicos de ITs são logging, persistência, distribuição, entre outros. Este trabalho está inserido no contexto da Engenharia de Requisitos Orientada a Aspectos (EROA) e seu enfoque está na identificação de interesses, a partir do documento de requisitos do software, e na classificação desses interesses como base ou transversais. Na literatura, há estudos comparativos de abordagens para EROA, os quais mostram que o processo de identificação e classificação de interesses tem apresentado baixa cobertura e precisão, principalmente em relação aos ITs. Isso se deve, em grande parte, a dois problemas principais: i) a baixa qualidade do documento de requisitos; e ii) a existência de interesses não explícitos no texto do documento de requisitos, isto é, interesses que emergem a partir do relacionamento entre outros interesses. Como exemplo desse segundo caso, pode-se citar o interesse de concorrência que, em geral, pode emergir da necessidade de se atender, simultaneamente, a outros dois interesses do software, a saber: segurança e desempenho. Este trabalho difere dos demais existentes, pois tem como objetivo o desenvolvimento e avaliação de um processo semiautomatizado, denominado ONTOREQ, para identificação e classificação de interesses em documentos de requisitos, com base em ontologias de domínio. A inovação está na utilização de ontologias de domínio como base para minimizar os problemas citados anteriormente. Para isso, propõe-se: i) criar ontologias específicas para ITs, com o intuito de auxiliar na identificação de interesses implícitos no texto dos requisitos; e ii) criar/reutilizar ontologias específicas para o domínio do software a ser tratado, para verificar a qualidade de seus requisitos. A execução manual do processo proposto pode ser custosa, pouco escalável e propensa a erros, sendo assim, uma suíte de ferramentas, denominada ONTOREQ-Toolkit, para automatização de algumas das atividades desse processo deve ser desenvolvida. A avaliação do processo ONTOREQ será realizada por meio de estudos de caso, cujo objetivo é averiguar se a eficácia e a eficiência desse processo são maiores do que as das abordagens existentes na literatura, quando o mesmo é aplicado a sistemas de software de diversos domínios e níveis de complexidade. Para avaliação da ONTOREQ-Toolkit, quanto a sua utilidade e usabilidade, serão utilizados questionários confeccionados com base no modelo TAM (Technology Acceptance Model). Palavras-chave: Processo, Identificação e Classificação de Interesses, Engenharia de Requisitos Orientada a Aspectos, Early Aspects, Ontologias de Domínio.

16 An Ecological Perspective Towards the Evolution of Quantitative Studies in Software Engineering Rafael M. de Mello, Guilherme H. Travassos COPPE/ PESC Universidade Federal do Rio de Janeiro (UFRJ) rmaiani, Abstract. Context: Two of the most common external threats to validity in quantitative studies in software engineering (SE) are concerned with defining the population by convenience and nonrandom sampling assignment. Although these limitations can be reduced by increasing the number of replications and aggregating their results, the acquired evidence rarely can be generalized to the field. Objective: To investigate the state of practice of meta-analysis in SE and its limitations, intending to propose an alternative perspective to understand the relationships among experimentation, production, threats to validity and evidence. To propose and evaluate means to strengthen quantitative studies in software engineering and making them less risky due to population and sampling issues. Method: To use the underlying idea from the Theory of Food Chains to alternatively understand the impact of external threats to validity in the SE experimental cycle (experimental chains). Next, to accomplish an initial technical literature survey to observe basic features of secondary studies aggregating primary studies results. Third, to organize a set of experimental chain s concepts and make initial discussions regarding the observed secondary studies concerned with this metaphor. Results: By applying the experimental chains concepts it was initially observed that, although important and necessary, most of the current effort in the conduction of quantitative studies in SE does not produce (mainly due to population/sampling constraints) results strong enough to positively impact the engineering of software. It promotes an imbalance between research and practice. However, more investigation is necessary to support this claim. Conclusion: We argue that research energy has been lost in SE studies due to population/sampling constraints. Therefore, we believe more investigation must be undertaken to understand how better organizing, enlarging, setting up and sampling SE quantitative studies population by using, for instance, alternative technologies such as social networks or other crowdsourcing technologies. Keywords: population sampling, meta-analysis, food chains, experimental chains, evidence based software engineering.

17 Satisfying Requirements by Cloud Resources Using Models at Runtime Raphael Aquino Gomes 1,2 Fábio Moreira Costa 1 1 Institute of Informatics Federal University of Goiás (UFG), Brazil 2 Federal Institute of Goiás (IFG), Brazil raphael@ifg.edu.br, fmc@inf.ufg.br Abstract. Besides the definition of Non-Functional Requirements (NFR) in software development, another problem is to establish the hardware resources needed to meet these requirements. Cloud computing is a promising alternative for providing these required resources. However to enable and enhance the dynamic management of shared cloud resources two issues need to be addressed. They refer to how the customers of cloud services express their resource requirements and how additional resources are provided by the complementary use of external cloud infrastructures. To reduce these difficulties it is crucial to move some activities performed at design time to development and execution time. One strategy to achieve this goal is the use of models at runtime, which allows the customer to express their resource requirements based on the needs of the applications that will run on these resources; and a more precise management of available computational power. This work presents a group of solutions for requirements specification and resource discovery using cloud computing. The general goal of this research proposal is to develop a specification language for NFRs as well the mechanisms needed to dynamically transform NFR specifications into a specification of the resources needed to host the application on cloud environments. Several works propose the use of models@run.time but most of them focus on the development of architectural models of the system, especially in the self-adaptive systems area. Despite the existence of a series of works related to the specification of requirements for systems in general, the ones that are related to cloud environments are those that consider SOA environments. In our research the definition of the resources needed to run an application is built by the system based on application requirements specified by the user. After defining the necessary resources application deployment is performed taking into account both organization s local resources and third party resources allocated from public clouds. Resource allocation is made according to the resource model generated. Initially, the private cloud formed by the organization s computing infrastructure is analyzed to check the possibility of admitting a new application given the resource model derived from thhe requirements specification. During application execution continuous monitoring is carried out to assess possible changes in the application requirements and/or resource availability. In the case is made a requirements change, the resource specification is again generated and compared with the current one. If the two models are not compatible it is necessary perform again the derivation of resources, its discovery and allocation. The implementation of the proposed approach will be made in the form of a working prototype, which will be used to demonstrate and evaluate concepts, also serving as a basis for a subsequent complete implementation. Keywords: Requirements Specification, Models@run.time, Cloud Computing.

18 Understanding Lehman s Laws of Software Evolution in Software Product Lines: An Experimental Study Raphael Pereira de Oliveira 1, Eduardo Santana de Almeida 1, Gecynalda Soares da Silva Gomes 2, Silvia Abrahão 3 and Emilio Insfran 3 1 Department of Computer Science, 2 Department of Statistics Federal University of Bahia, Av. Adhemar de Barros, s/n, , Salvador, Brazil {raphaeloliveira, esa}@dcc.ufba.br, gecynalda@yahoo.com 3Department of Information Systems and Computation Universitat Polite cnica de Valeǹcia, Camino de Vera, s/n, 46022, Valencia, Spain {sabrahao, einsfran}@dsic.upv.es Abstract. Software Product Lines (SPL) has gained the attention of the software engineering community lately, however, the issue of how common, variable and productspecific assets evolve needs a broader investigation. This study evaluated the Lehman s Laws of Software Evolution in an SPL industrial project in order to understand how the SPL assets evolve over the time. The industrial project has 45 modules and a total of requests in the bug tracking system collected over 10 years. We applied the Augmented Dickey-Fuller Test and linear regression analysis to evaluate the statistical trends over the years of the collected data related to the laws. The results of the study showed that three laws were completely accepted (continuous change, increasing complexity and declining quality) and one was completely rejected (feedback system). The other laws were partly accepted or partly rejected, depending on the SPL asset (common, variable or product-specific). So far, the study has been evaluated in the medical domain with just one small (roughly 50 employees) company. Finally, besides the continuous change for all assets in an SPL, we found that complexity is raising and quality is decreasing in an SPL industrial project over the years. Based on this study, we intend to propose some guidelines for evolving an SPL. Keywords: Software Product Lines; Software Evolution; Lehman s Laws of Software Evolution; Empirical Study.

19 An Approach to Prioritize Code Smells for Refactoring Santiago Vidal, Claudia Marcos, Andrés Diaz Pace ISISTAN Research Institute, UNICEN University, Argentina exa.unicen.edu.ar, exa.unicen.edu.ar Abstract. Software evolution and maintenance involve high costs in the development process, particularly as systems become larger and complex. A usual concern that makes system maintenance and evolution difficult is the existence of structural design problems, which were not sufficiently taken care of in early development stages. These design problems are often described as code smells. A code smell is a symptom in the source code that helps to identify a design problem. In this way, code smells allow developers to detect fragments of code that should be re-structured, in order to improve the quality of the system. A technique commonly used to fix code smells is refactoring. Different semi-automated tools can be applied to identify code smells in a system. However, a major limitation of existing tools is that they usually find numerous code smells. This is a challenging problem for the developer, for a number of reasons. First, she can get overwhelmed by the amount of information to be analyzed. Second, the effort needed to fix all the code smells usually exceeds the budget that the developer has available for refactoring. Third, in practice, not all code smells are equally important for the goals of the system or its health. Therefore, the developer has to manually peruse the list of code smells and select a set of smells that will be fixed. In this context, the provision of tool support for assisting the developer to quickly identify high-priority code smells becomes essential. In our research, we propose a semiautomated approach called SpIRIT (Smart Identification of Refactoring opportunities) that treats refactoring as a cost-effective activity. By cost-effective, we mean that the analysis and re-structuring efforts are driven by a handful of code problems considered as critical for the current system, so that solving those problems will positively contribute to the system quality but with a limited refactoring expenditure. Given an object-oriented system with a number of code smells, SpIRIT assists the developer in two tasks: (i) prioritizing the code smells, and (ii) suggesting candidate refactorings for each smell using a cost-benefit analysis. The novel aspect of our approach is the prioritization of code smells based on assessing their relationships with modifiability issues. Our assessment of a code smell instance is determined by the following factors: past component modifications, important modifiability scenarios for the system, and types of code smells. Regarding the suggestion of refactorings, SpIRIT seeks to determine refactoring alternatives for each code smell of its ranking. After searching through the design space of refactoring alternatives, the tool should assess a set of candidate refactorings in terms of the improvement that their application would produce in the system. Keywords: Software evolution, Code Smells, Refactoring

20 Variability Realization in Service-Oriented Product Lines Tassio Vale 1,2 Eduardo Santana de Almeida 1,2 1 Computer Science Department- Federal University of Bahia (UFBA) 2 RiSE Labs - Reuse in Software Engineering tassio.vale@ufba.br, esa@dcc.ufba.br Abstract. The combination of Service-Oriented Computing (SOC) and Software Product Lines (SPL) together has started to receive attention from researchers and practitioners seven years ago, since SOC and SPL can address issues of each other. This combination results in a specific type of product line, called Service-Oriented Product Line (SOPL), and the area that studies the development of SOPLs is called Service-Oriented Product Line Engineering (SOPLE). Dynamic product reconfiguration involves making changes to a deployed product configuration at runtime, and SOPLE is a way to handle it for context-aware computing and adaptive systems scenarios. There is a lack of implementation proposals for SOPLs. Therefore, we propose an investigation of available implementation techniques for dynamic variability, aiming to create a systematic approach for developing SOPLs. As first results, our systematic mapping study did not identified processes for implementing service-oriented product lines. In fact, there are studies addressing specific issues of SOPL implementation without looking the big picture. On the other hand, we investigate existing variability implementation techniques trying to figure out their applicability in a SOPLE environment. As future work, we intend to perform an exploratory study by developing a testbed in order to identify similarities and differences among single system, service-oriented, product line and SOPLE implementations. After, evidence from the mapping study and testbed will guide the conception of the approach, that will be evaluated through a case study. Keywords: Service-Oriented Computing, Software Product Lines, Service-Oriented Product Lines, Variability Implementation Techniques.