Submitted by Pedro Henrique Rodrigues (pedro.henriquer@ufpe.br) on 2015-03-05T19:54:44Z No. of bitstreams: 2 rcaa-dissertacao.pdf: 2306258 bytes, checksum: c627fb646b9c6f3cadf93565c0b59dd9 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-05T19:54:44Z (GMT). No. of bitstreams: 2 rcaa-dissertacao.pdf: 2306258 bytes, checksum: c627fb646b9c6f3cadf93565c0b59dd9 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2012-03-02 / FACEPE, CNPq, INES / Companies are adopting the Software Product Line (SPL) development paradigm to obtain significant improvements in time to market, maintenance cost, productivity, and quality of products. SPL encompasses a family of software-intensive systems developed from reusable assets. By reusing such assets, it is possible to construct a large number of different products applying various compositions. There is a variety of widely used techniques to develop SPLs, such as aspect-oriented programming (AOP), feature-oriented programming (FOP), and conditional compilation. These techniques differ in the type of composition to create a product within the SPL static or dynamically. In this context, it is important to define when certain features should be activated in the product due to specific client requirements and different application scenarios. Thereby, the binding time of a feature is the time that one decides to activate or deactivate the feature from a product. In general, static and dynamic binding times are considered. For example, products for devices with constrained resources may use static binding time instead of dynamic due to the performance overhead introduced by the latter. For devices without constrained resources, the binding time can be flexible, features can be activated or deactivated statically or users may do it on demand (dynamically). To provide flexible binding time for features, researchers proposed an AOP idiom based on AspectJ and design patterns named Edicts. The idea consists of supporting binding time flexibility of features in a modular and convenient way. However, we observe modularity problems in the Edicts idiom. Although we usually use aspects to tackle crosscutting concerns common in classes, such a problem now appears within the own aspects. Indeed, several studies indicate that these concerns hurt software modularity. This way, we observe that Edicts clones, scatters, and tangles code throughout its implementation, which may lead to time consuming tasks, such as maintaining duplicated code. This way, we develop three idioms and implement them to provide flexible binding time for features of four different applications. In addition, we evaluate Edicts and the three idioms quantitatively by means of metrics with respect to code tangling, scattering, cloning, size, and also try to guarantee that our idioms do not change feature code behavior among the different implementations.

The dissertation is concerned with the analysis of the marketing mix of the czech cosmetic company Dermacol, in the concrete its products of firming care Enja Body Control Program. The objective is to review present application of marketing instruments and confront it with the opinion of consumers (design of product, comparison of czech anf foreign brands, price level, effectiveness of distribution and comunication etc.).

No description available.

No description available.

Submitted by Adriely Bruce (adriely_bruce@hotmail.com) on 2016-12-16T15:23:35Z No. of bitstreams: 1 Dissertação - Rafael Normando Cunha.pdf: 2634755 bytes, checksum: 1a601e8e730d9bca00432b2e7038ac0f (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2016-12-22T13:36:58Z (GMT) No. of bitstreams: 1 Dissertação - Rafael Normando Cunha.pdf: 2634755 bytes, checksum: 1a601e8e730d9bca00432b2e7038ac0f (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2016-12-22T13:39:39Z (GMT) No. of bitstreams: 1 Dissertação - Rafael Normando Cunha.pdf: 2634755 bytes, checksum: 1a601e8e730d9bca00432b2e7038ac0f (MD5) / Made available in DSpace on 2016-12-22T13:39:39Z (GMT). No. of bitstreams: 1 Dissertação - Rafael Normando Cunha.pdf: 2634755 bytes, checksum: 1a601e8e730d9bca00432b2e7038ac0f (MD5) Previous issue date: 2013-12-17 / Agência de Fomento não informada / Software Product Lines enable organizations to develop a number of similar products in the same application domain, which reduces development time and maintenance cost, and increases productivity. Software product line specifications need to be evaluated for improving software. In this context, software inspections aims do guarantee complete, consistent and correct artifacts finding defects in early stages in software lifecycle. In this work, we propose SPLIT (Software Product Line Inspection Technique), which is a set of modelbased inspection techniques for evaluating software product line specifications. A feasibility study was conducted for comparing SPLIT against a defect type-based inspection approach. The object of the feasibility study was a Twitter client software product line specification created for the experiment. The results indicated that the set of techniques found a greater number of defects than a defect type-based inspection approach. A second empirical study was conducted for comparing SPLIT against a defect type-based inspection approach using a real software product line for mobile robot vehicles. This study aimed to verify whether the set of techniques fits real world life-cycle development. The second empirical results supported the feasibility study in which SPLIT found a greater number of defects than a defect type-based inspection approach. Thus, software product line quality assurance can be improved using SPLIT for detecting defects in early stage of development. / Linha de produto de software permite que organizações desenvolvem um número similar de produtos específicos em um mesmo domínio de aplicação, reduzindo o tempo de desenvolvimento e o custo de manutenção, e aumentando a produtividade. Especificações de linha de produto de software necessitam ser avaliadas para aumentar a qualidade do software. Neste cenário, inspeções de software visam garantir que os artefatos estejam completos, consistentes e corretos ao encontrar defeitos em estágios iniciais do ciclo de vida de desenvolvimento. Neste trabalho, é proposta a SPLIT (Software Product Line Inspection Technique), um conjunto de técnicas de inspeção baseada em modelos para avaliar especificações de linha de produto de software. Um estudo de viabilidade foi conduzido para comparar a SPLIT com uma abordagem de inspeção baseada em tipos de defeitos. O objeto do estudo de viabilidade foi um cliente de Twitter desenvolvido para a execução do experimento. Os resultados indicaram que o conjunto de técnicas SPLIT encontrou um número maior de defeitos que uma abordagem de inspeção baseada em tipos de defeitos. Um segundo experimento foi conduzido para comparar a SPLIT com uma abordagem baseada em tipos de defeitos usando uma linha de produto de software real para veículos robóticos móveis. Este estudo visou verificar se o conjunto de técnicas se adaptam ao ciclo de vida de desenvolvimento real. O segundo experimento corroborou o resultado do estudo de viabilidade ao encontrar um número de defeitos maior que uma abordagem de inspeção baseada em tipos de defeitos. Com isso, a garantia da qualidade em linhas de produto de software pode ser melhorada ao utilizar a SPLIT para encontrar defeitos em estágios iniciais do desenvolvimento.

Nous avons commencé la thèse par la littérature d'enquête sur les approches SPLE et CbyC dans l'état de l'art. Sur la base de l'aperçu et des connaissances obtenues, nous avons analysé les problèmes existants et suggéré des moyens de les résoudre pour notre objectif principal. Nous avons proposé dans le chapitre 2 une méthodologie pour développer des lignes de produits afin que les produits générés soient corrects par construction. Notre intention principale est qu'un utilisateur n'a pas besoin de connaître le processus de génération de produit mais peut recevoir un produit final correct en sélectionnant une configuration de fonctionnalité. En utilisant la méthodologie, les produits finaux sont générés automatiquement et leur exactitude est garantie. À la suite de cette proposition, nous sommes passés au chapitre 3 pour définir la langue de FFML qui est utilisé pour l'écriture de modules. Le mécanisme de réutilisation et de modification, défini pour la langue et appliqué à toutes sortes d'artefacts (spécification, code et preuve de précision) réduit l'effort de programmation. Au chapitre 4, nous nous sommes concentrés sur la définition des mécanismes de composition pour la composition des modules FFML et les intégrons à l'outil FFML Product Generator. L'évaluation de notre méthodologie est réalisée par le développement de deux lignes de produits logiciels, le compte bancaire SPL et le SPL de poker, ce dernier étant un peu plus complexe que le premier. Dans l'évaluation, nous avons souligné les avantages et la limitation de notre méthodologie. / We began the thesis by survey literature on SPLE and CbyC approaches in the State of the Art. Based on the overview and the insights obtained, we have analyzed the existing problems and suggested ways to solve them for our main goal. We have proposed in Chapter 2 a methodology to develop product lines such that the generated products are correct-by-construction. Our main intention is that a user does not need to know the product generation process but can receive a correct final product from selecting a configuration of features. Using the methodology, the final products are generated automatically and their correctness is guaranteed. Following this proposal, we have moved in Chapter 3 to define the FFML language that is used for writing modules. The reuse and modification mechanism, defined for the language and applied to all kinds of artifacts (specification, code and correctness proof), reduce the programming effort. In Chapter 4, we have focused on defining the composition mechanisms for composing FFML modules and embedded them into the FFML Product Generator tool. The evaluation of our methodology is performed through the development of two software product lines, the Bank Account SPL and the Poker SPL, the latter being a bit more complex than the former. In the evaluation, we have highlighted the advantages and the limitation of our methodology.

Linha de Produto de Software (LP) é uma forma sistemática de promover a geração de produtos de software específicos baseados no reúso de uma infraestrutura bem definida. Conceitos de LP aplicados ao domínio de Gestão de Processos de Negócio (BPM - Business Process Management) já apresentaram resultados significativos, entretanto, o escopo de aplicação e os benefícios ainda são limitados. Essas limitações ocorrem, pois as abordagens de LP já existentes para BPM normalmente não cobrem todo o ciclo de vida de processos de negócio e não oferecem o devido tratamento aos aspectos dinâmicos que as organizações demandam para esse domínio. Linha de Produto de Software Dinâmica (LPD) é uma evolução das LPs tradicionais que tem proporcionado uma forma eficiente para lidar com adaptações de produtos em tempo de execução. LPDs podem ser aplicadas, por exemplo, no contexto de arquiteturas SOA (Service-oriented Architecture), que por sua vez podem ser usadas como base tecnológica para viabilizar BPM nas organizações. Dentro desse contexto, este trabalho propõe uma abordagem de LPD para atender as necessidades de organizações interessadas em realizar processos de negócio, por meio de um alinhamento entre conceitos de BPM e SOA. A abordagem proposta aqui, denominada Dynamic Product Line for Business Process Management (DynPL4BPM), visa ser abrangente o suficiente para cobrir todo o ciclo de vida de BPM, sendo previsto o tratamento de aspectos dinâmicos que o domínio de BPM requer. Uma avaliação sistemática e comparativa demonstrou que a abordagem proposta é bem sucedida em apresentar processos bem mais abrangentes que outras soluções similares já propostas na literatura para o mesmo fim. / Software Product Line (PL) is a systematic way to promote the generation of specific software products based on the reuse of a well-defined infrastructure. Concepts of PL applied to Business Process Management (BPM) have already presented significant results; however, the application scope and benefits are still limited. These limitations occur because the existing approaches of LP for BPM usually do not cover the entire lifecycle of business processes and do not provide proper treatment to the dynamic aspects that organizations demand for this domain. Dynamic Software Product Line (DPL) is an evolution of traditional PLs that has provided an efficient way to deal with adaptations of products at runtime. DPLs can be applied, for example, in the SOA (Service-oriented Architecture) context, which in turn can be used as technological basis to enable BPM within organizations. Within this context, this dissertation proposes a DPL approach to meet the needs of organizations interested in carrying out business processes by means of an alignment between BPM and SOA concepts. The approach proposed here, called Dynamic Product Line for Business Process Management (DynPL4BPM), aims to be comprehensive enough to cover the entire BPM lifecycle, including the treatment of dynamic aspects that the BPM domain requires. A systematic and comparative assessment showed that the proposed approach is successful in presenting processes much more comprehensive than other similar solutions already proposed in the literature for the same purpose.

Linha de Produto de Software (LP) é uma forma sistemática de promover a geração de produtos de software específicos baseados no reúso de uma infraestrutura bem definida. Conceitos de LP aplicados ao domínio de Gestão de Processos de Negócio (BPM - Business Process Management) já apresentaram resultados significativos, entretanto, o escopo de aplicação e os benefícios ainda são limitados. Essas limitações ocorrem, pois as abordagens de LP já existentes para BPM normalmente não cobrem todo o ciclo de vida de processos de negócio e não oferecem o devido tratamento aos aspectos dinâmicos que as organizações demandam para esse domínio. Linha de Produto de Software Dinâmica (LPD) é uma evolução das LPs tradicionais que tem proporcionado uma forma eficiente para lidar com adaptações de produtos em tempo de execução. LPDs podem ser aplicadas, por exemplo, no contexto de arquiteturas SOA (Service-oriented Architecture), que por sua vez podem ser usadas como base tecnológica para viabilizar BPM nas organizações. Dentro desse contexto, este trabalho propõe uma abordagem de LPD para atender as necessidades de organizações interessadas em realizar processos de negócio, por meio de um alinhamento entre conceitos de BPM e SOA. A abordagem proposta aqui, denominada Dynamic Product Line for Business Process Management (DynPL4BPM), visa ser abrangente o suficiente para cobrir todo o ciclo de vida de BPM, sendo previsto o tratamento de aspectos dinâmicos que o domínio de BPM requer. Uma avaliação sistemática e comparativa demonstrou que a abordagem proposta é bem sucedida em apresentar processos bem mais abrangentes que outras soluções similares já propostas na literatura para o mesmo fim. / Software Product Line (PL) is a systematic way to promote the generation of specific software products based on the reuse of a well-defined infrastructure. Concepts of PL applied to Business Process Management (BPM) have already presented significant results; however, the application scope and benefits are still limited. These limitations occur because the existing approaches of LP for BPM usually do not cover the entire lifecycle of business processes and do not provide proper treatment to the dynamic aspects that organizations demand for this domain. Dynamic Software Product Line (DPL) is an evolution of traditional PLs that has provided an efficient way to deal with adaptations of products at runtime. DPLs can be applied, for example, in the SOA (Service-oriented Architecture) context, which in turn can be used as technological basis to enable BPM within organizations. Within this context, this dissertation proposes a DPL approach to meet the needs of organizations interested in carrying out business processes by means of an alignment between BPM and SOA concepts. The approach proposed here, called Dynamic Product Line for Business Process Management (DynPL4BPM), aims to be comprehensive enough to cover the entire BPM lifecycle, including the treatment of dynamic aspects that the BPM domain requires. A systematic and comparative assessment showed that the proposed approach is successful in presenting processes much more comprehensive than other similar solutions already proposed in the literature for the same purpose.

The number and complexity of the systems realizing the functionality of the machines in the automotive domain are growing. In this arises the need for a systematic way to manage their development. As the technologies advance, the vehicles introduce an increasing range of capabilities. However, they have similar functions, which have the potential to be reused. One of the widely used approaches that manages the commonality and variability of the development artifacts in a systematic manner is Product Line Engineering (PLE). Consequently, PLE reduces the time to market and the development cost. The machines, realized in the automotive domain, interact with their operators and the surrounding environment. Possible malfunctions of the machines may introduce a risk of accidents with fatal consequences. Therefore, the products should be analyzed, developed and managed in a safe manner and certified according to different relevant safety standards like ISO 15998, ISO 61508 and ISO 26262. There is a diversity of functions in a Product Line (PL). Some of them are mandatory for all machines and others are optional for some models. This gives the opportunity to combine the functions in multiple configurations. However, not all combinations are possible due to dependencies among the functions. Furthermore, the configurations should be valid from a safety perspective, and the developed products should satisfy the requirements identified during the safety analysis. The above mentioned factors emphasize the need for explicit representation of the systems' characteristics, such as commonality and variability, functional dependencies and quality attributes. The purpose of the current work is to find an efficient way to satisfy this need. The scope of our research is limited to the automotive domain. In order to gain familiarity with the state of practice, we collaborated with Volvo Construction Equipment (Volvo CE) as an industrial partner. In particular, we: conducted an informal interview study with the practitioners, analyzed the requirements management tool used in Volvo CE and studied products typical for the domain in detail, examined the deliverables defined in the related domain specific safety standards. We gained knowledge on how variability is managed in an industrial context today, which safety aspects need to be considered and how functional safety artifacts are managed with regards to variability. We synthesized the characteristics that are explicitly represented during the development and safety certification of the products in a safety-critical product line. We identified the challenges that the practitioners meet today and the areas that need to be improved. As a result, we formulated evaluation criteria for search and assessment of possible solutions. Subsequently we searched in the literature for different modeling techniques, that are able to respond to the industrial needs, and found the following to be relevant in our context: Feature modeling techniques consider the different variability types and dependencies among the features. Model-based development techniques can represent different views of the system on each level of the development process. Orthogonal modeling techniques extract the variability and dependencies in a different view. Furthermore, we evaluated the methods found during the literature study, based on the proposed criteria. We concluded that the examined techniques alone cannot represent all characteristics needed to support the development of a safety-critical product line, especially the impact of the variability on the safety and vice versa. However, each of them focuses on the presentation of certain aspect of the product line, which can help in building a more complete representation. Thus we focused on the approaches that may be extended and integrated into a complete solution. As a result, we propose a model and graphical notation for variability management in safety-critical product lines, which takes the identified industrial needs into account. The concept is depicted graphically by several model-based diagrams, which represent the different aspects of the product line, on each development level. Special attention is paid to the representation of the safety and variability aspects of the systems. The method is exemplified on an industrial example, in order to show how it achieves the defined goals.

The requirements for software products have increased in recent years. This is both due to more complex technology as well as more requirements from the customers. An approach to solve this issue is by using a software product line (SPL) where reusable assets are developed to produce more tailor-made products with reduced time to market. When creating reusable assets, one also wants to reuse the tests for them. In order to do that, it is important to understand what to test, and where to test. A good test strategy is thereby crucial in order to avoid testing becoming a bottleneck for efficient software development. The purpose of this thesis was to investigate how to create a good testing strategy for products in an SPL. This was done by collecting information about the current testing process in order to understand which requirements that exist and how they are addressed. The core foundation of an SPL is to utilize variation to create new products. To understand the existing variation of the product and the test cases a feature modeling and similarity analysis was done. The result from them made it possible to create a test strategy and categorization of test cases that can be used to ease the reuse of test cases for new variants of the product. The resulting test strategy presented proposes feature modeling as the basis of test creation and categorization as a tool to enable easier reuse of test cases. The results of the study indicate that using SPL theory in testing can introduce a better test strategy and test case creation process which is beneficial for the whole development process. / Kraven på mjukvaruprodukter har ökat de senaste åren. Detta beror delvis på mer komplicerad teknologi, men även på att kunderna ställer högre krav på de produkter de använder. Ett tillvägagångssätt för att lösa detta är att använda en software product line. I en software product line utvecklas återanvändningsbara delar som sedan kan kombineras och därmed skapa skräddarsydda produkter på ett mer effektivt sätt. När man skapar återanvändningsbara mjukvarudelar vill man också återanvända testerna för dem. För att göra det är det viktigt att förstå vad som ska testas och varför. En bra teststrategi är därmed avgörande för att undvika att testning blir en flaskhals för effektiv mjukvaruutveckling. Syftet med detta arbete var att undersöka hur man skapar en bra teststrategi för produkter i en software product line. Detta gjordes genom att samla in information om den nuvarande testprocessen för att förstå vilka krav som finns och hur de hanteras. En huvudaspekt i software product lineteori är att använda variation för att skapa nya produkter. För att förstå variationen i produkten och dess testfall gjordes en funktionsmodellering och likhetsanalys. Resultaten från dem gjorde det möjligt att skapa en teststrategi och en kategorisering av testfall som kan användas för att underlätta återanvändningen av testfall för nya varianter av produkten. Den resulterande teststrategin som presenteras föreslår funktionsmodellering som grund för testskapande och kategorisering som ett verktyg för att möjliggöra enklare återanvändning av testfall. Resultaten av studien tyder på att användning av software product lineteori vid testning kan resultera i en bättre teststrategi och enklare process för skapandet av nya testfall.