Overview of Requirements Engineering Process for Software Product Lines

Software Product Lines is an important strategy to minimize costs and time-to market, and maximize quality and productivity of the software development. It involves the management of variabilities and commonalities among several applications, which increases its complexity compared to traditional software development. In this context, a Requirements Engineering and management are central tasks, important to reduce the risks involved in a development of product line. System requirements must be properly identified, analysed and reviewed in order to provide adequate solution to manage variabilities and integrating them for making easy the products derivation. In this paper Requirements Engineering process and techniques used in some of the product line practices are reviewed and discussed. Also, Requirements Engineering techniques for traditional single product software development are analysed and their applicability in product line development is assessed. This work is licensed under a&nbsp;Creative Commons Attribution-NonCommercial 4.0 International License.</p

La variabilité due à la sensibilité au contexte dans les processus téléologiques

National audienceVariability has proved to be a central concept in different engineering domains, manufacturing, software development etc. in order to develop solutions that can be easily adapted to different organizational settings and different sets of customer at a low price. Teleological processes have, by nature, a high level of variability. Our position is that the integration of "context-awareness" in that kind of processes increases their intrinsic variability with specific criteria. We propose an indicator typology with an usage process and illustrate it with the MAP intentional process model

Processus téléologique et variabilité: Utilisation de la sensibilité au contexte

International audienceVariability has proved to be a central concept in different engineering domains, manufacturing, software development etc. in order to develop solutions that can be easily adapted to different organizational settings and different sets of customer at a low price. Teleological processes have, by nature, a high level of variability. Our position is that the integration of "context-awareness" in that kind of processes increases their intrinsic variability with specific criteria. We propose an indicator typology with an usage process and illustrate it with the MAP intentional process model

Uma solução de implantação auto-adaptativa para plataformas Android

Orientador: Cecília Mary Fischer RubiraDissertação (mestrado) - Universidade Estadual de Campinas, Instituto de ComputaçãoResumo: Os dispositivos móveis, hoje em dia, fornecem recursos semelhantes aos de um computador pessoal de uma década atrás, permitindo o desenvolvimento de aplicações complexas. Consequentemente, essas aplicações móveis podem exigir tolerar falhas em tempo de execução. No entanto, a maioria das aplicações móveis de hoje são implantados usando configurações estáticas, tornando difícil tolerar falhas durante a sua execução. Nós propomos uma infraestrutura de implantação auto-adaptativa para lidar com este problema. A nossa solução oferece um circuito autônomo que administra o modelo de configuração atual da aplicação usando um modelo de características dinâmico associado com o modelo arquitetônico da mesma. Em tempo de execução, de acordo com a seleção dinâmica de características, o modelo arquitetônico implantado na plataforma se re-configura para fornecer uma nova solução. Uma aplicação Android foi implementada utilizando a solução proposta, e durante sua execução, a disponibilidade de serviços foi alterada, de tal forma que sua configuração corrente foi dinamicamente alterada para tolerar a indisponibilidade dos serviçosAbstract: Mobile devices, nowadays, provide similar capabilities as a personal computer of a decade ago, allowing the development of complex applications. Consequently, these mobile applications may require tolerating failures at runtime. However, most of the today¿s mobile applications are deployed using static configurations, making difficult to tolerate failure during their execution. We propose an adaptive deployment infrastructure to deal with this problem. Our solution offers an autonomic loop that manages the current configuration model of the application using a dynamic feature model associated with the architectural model. During runtime, according to the dynamic feature selection, the deployed architectural model can be modified to provide a new deployment solution. An Android application was implemented using the proposed solution, and during its execution, the services availability was altered so that its current configuration was changed dynamically in order to tolerate the unavailability of servicesMestradoCiência da ComputaçãoMestre em Ciência da Computação131830/2013-9CNP

Towards a Taxonomy of Aspect-Oriented Programming.

As programs continue to increase in size, it has become increasingly difficult to separate concerns into well localized modules, which leads to code tangling- crosscutting code spread throughout several modules. Thus, Aspect-Oriented Programming (AOP) offers a solution to creating modules with little or no crosscutting concerns. AOP presents the notion of aspects, and demonstrates how crosscutting concerns can be taken out of modules and placed into a centralized location. In this paper, a taxonomy of aspect-oriented programming, as well as a basic overview and introduction of AOP, will be presented in order to assist future researchers in getting started on additional research on the topic. To form the taxonomy, over four-hundred research articles were organized into fifteen different primary categories coupled with sub-categories, which shows where some of the past research has been focused. In addition, trends of the research were evaluated and paths for future exploration are suggested

Estudo de interdependências e rastreabilidade no processo RUP : análise do micro-processo V-Model e do método 4SRS

Dissertação de mestrado em Engenharia e Gestão de Sistemas de InformaçãoDado que a maioria dos artefactos desenvolvidos durante o processo de engenharia de requisitos se relacionam e se afetam mutuamente de diversas formas, é emergente a necessidade de identificar as interdependências entre os artefactos, de forma a conhecer detalhadamente como estes se relacionam ao longo do desenvolvimento de software. Sendo o Rational Unified Process (RUP) um processo que fornece as melhores práticas e orientações para o desenvolvimento de software bem sucedido, conhecer pormenorizadamente como os seus elementos se relacionam traz bastante utilidade. Este trabalho de investigação tem como propósito efetuar uma sistematização das interdependências existentes no processo RUP e na sua utilização para estudar um micro-processo (V-Model) e um método (Four Step Rule Set - 4SRS) do ponto de vista da cobertura que garantem relativamente às recomendações do RUP. Desta forma, primeiramente pretende-se estudar os diversos elementos que constituem o RUP, assim como, os seus relacionamentos. E em seguida, com base nesse conhecimento, pretende-se demonstrar como é vantajoso conhecer as interdependências e a rastreabilidade entre os diversos elementos que constituem o RUP, quando se compara um determinado método/modelo de processo com o RUP.Given that most artifacts developed during the requirements engineering process are related and affect each other in different ways, it is emergent the need to identify the interdependencies between artifacts, in order to know in detail how they relate during software development. Being the Rational Unified Process (RUP) a process that provides best practices and guidelines for successful software development, to know in detail how its elements are related bring enough utility. This research work aims to make a systematization of existing interdependencies in the RUP process and in its use to study a microprocess (V-Model) and a method (Four Step Rule Set - 4SRS) from the viewpoint of ensuring coverage of the recommendations of RUP. Thus, first intend to study the different elements that constitute the RUP, as well as their relationships. Then, based on that knowledge, it is intended to demonstrate how it is advantageous to know the interdependencies and the traceability between different elements that constitute the RUP, when comparing a given method/process model with RUP

Aspect-Oriented Requirements Engineering for Software Product Lines

The cost of fixing a requirements defect later in the development stage is much higher than the cost of identifying and fixing it in the early stages of development. In order to do this the system requirements must be properly identified, analyzed and reviewed early in the development process. Requirements engineering is such a process that focuses on discovering, analyzing, documenting and managing system requirements. Several processes and techniques have been developed to assist requirements engineering activities. A product line is a set or group of products that have a majority of features in common and vary only in certain specific features. Developing a group of products that have a majority of features in common supports a great deal of reuse in all the phases of system development. Due to the complexity and extensive nature of product line development, requirements engineering is much more important for a product line practice. In this paper an attempt is made to review requirements engineering techniques used in existing software product line practices. Also the applicability of several requirements engineering techniques to software product line development is assessed. Keywords