Zur einfacheren Entwicklung von technischen Systemen werden heutzutage vielfach funktionsblockorientierte Modellierungssprachen wie MATLAB/Simulink verwendet, die ein System als Netzwerk von miteinander verbundenen Funktionsblöcken darstellen. Aufgrund wechselnder Anforderungen entstehen dabei viele Modellvarianten, die nicht mehr effizient verwaltet werden können. Eine Lösung hierfür ist der Einsatz von Produktlinien, bei dem alle Varianten zusammengefasst und in wiederverwendbare Bestandteile zerlegt werden. Die Einzelvarianten werden dabei nur noch bei Bedarf aus diesen Bestandteilen zusammengesetzt. Die Erstellung dieser Produktlinien ist jedoch mit hohem manuellen Aufwand verbunden, besonders wenn vorhandene Modelle wiederverwendet werden sollen. Dies verhindert oft die Einführung dieses Paradigmas. Das Ziel der Dissertation war es deshalb, diese Migration vorhandener Modellvarianten und damit die Erstellung der Produktlinien zu automatisieren. Hierzu wurde eine Migrationsschrittfolge vorgeschlagen: Mithilfe eines Model-Matching-Ansatzes werden zuerst Gemeinsamkeiten und Unterschiede zwischen den Modellen identifiziert und daraus ein zusammengefasstes Modell und sogenannte Features abgeleitet. Mithilfe der Formalen Begriffsanalyse werden daraufhin die Abhängigkeiten zwischen diesen Features extrahiert und daraus ein Feature-Modell erstellt. Feature-Modell und zusammengefasstes Modell bilden dabei eine Produktlinie, die exakt die vorgegebenen Modellvarianten beschreibt.

The major problem addressed in this thesis is the definition of a new SPLE methodology that covers both phases of the SPLE process and focuses on the derivation of behavioral models of SPL products. In Chapter 2 three research areas scope context of this thesis: Software Product Lines, Business Processes, and Model-Driven Engineering. Throughout Chapter 3, we propose a new SPLE methodology that focuses on the derivation of product behavior. We first describe the main flow of the methodology, and then detail the individual steps. In chapter 4 we propose a new domain specific language called CBPF created for modeling composable business process fragments. A model driven approach is followed for creating CBPF: definition of the abstract syntax, graphical concrete syntax and translational semantics. In Chapter 5 we propose several types of verifications that can be applied to business processfragments to determine their "correctness". For structural verification we definine a set of fragment consistency rules that should be valid for every business process fragment created with CBPF. To check behavioral correctness we first transform the business process fragment into an equivalent HCPN. We can then check generic properties but also define aset of fragment specific properties. In chapter 6 we exemplify the proposed SPL methodology by applying it to a case study from the crisis management system domain. We also propose a tool suite that supports our methodology. Chapter 7 describes possible improvements and extensions to the contributions of this thesis. We conclude the thesis in Chapter 8 and draw some conclusions.

Mobile applications are developed to run on fast-evolving platforms, such as Android or iOS. Respective mobile devices are heterogeneous concerning hardware (e.g., sensors, displays, communication interfaces) and software, especially operating system functions. Software vendors cope with platform evolution and various hardware configurations by abstracting from these variable assets. However, they cannot be sure about their assumptions on the inner conformance of all device parts and that the application runs reliably on each of them—in consequence, comprehensive testing is required. Thereby, in testing, variability becomes tedious due to the large number of test cases required to validate behavior on all possible device configurations. In this paper, we provide remedy to this problem by combining model-based testing with variability concepts from Software Product Line engineering. For this purpose, we use feature-based test modeling to generate test cases from variable operational models for individual application configurations and versions. Furthermore, we illustrate our concepts using the commercial mobile application “runtastic” as example application.

Domain feature models concisely express commonality and variability among variants of a software product line. For separation of concerns, e.g., due to legal restrictions, technical considerations, and business requirements, multi-view approaches restrict the configuration choices on feature models for different stakeholders. However, recent approaches lack a formalization for precise, yet flexible specifications of views that ensure every derivable configuration perspective to obey feature model semantics. Here, we introduce a novel approach for clustering feature models to create multi-perspectives. Such customized perspectives result from composition of multiple concern-relevant views. A structured view model is used to organize feature groups, whereat a feature can be contained in multiple views. We provide formalizations for view composition and guaranteed consistency of the resulting perspectives w.r.t. feature model semantics. Thereupon, an efficient algorithm to verify consistency for entire clusterings is provided. We present an implementation and evaluate our concepts on two case studies.

Made available in DSpace on 2014-12-17T15:47:57Z (GMT). No. of bitstreams: 1 AnaLSO_DISSERT.pdf: 3044702 bytes, checksum: 7d5dc3b7e2aab3803ef82bbde3db6f6a (MD5) Previous issue date: 2011-05-31 / Software Product Line (SPL) consists of a software development paradigm, whose main focus is to identify features common and variability among applications in a specific domain. An LPS is designed to attend all products requirements from its product family. These requirements and LPS may have changes over time due to several factors, such as evolution of product requirements, evolution of the market, evolution of SLP process, evolution of the technologies used to develop the products. To handle these changes, LPS should be modified and evolve in order to not become obsolete, and adapt itself to new requirements. The Changes Impact Analysis is an activity that understand and identify what consequences these changes are cause on LPS. Impact Analysis on LPS may be supported by traceability relationships, which identify relationships between artefacts created during all phases of software development. Despite the solutions of change impact analysis based on traceability for software, there is a lack of solutions for assessing the change impact analysis based on traceability for LPS, since existing solutions do not include estimates specific to the artefacts of LPS. Thus, this paper proposes a process of change impact analysis and an tool for assessing the change impact through traceability of artefacts in LPS. For this purpose, we specified a process of change impact analysis that considers artifacts produced during the development of LPS. We have also implemented a tool which allows estimating and identifying artefacts and products of LPS affected from changes in other products, changes in class, changes in features, changes between releases of LPS and artefacts related to changes in core assets and variability. Finally, the results were evaluated through metrics / Linhas de Produto de Software (LPS) consistem em um paradigma de desenvolvimento de software, cujo foco principal encontra-se na identifica??o das caracter?sticas (features) comuns e vari?veis entre as aplica??es de um segmento de dom?nio espec?fico. Uma LPS ? projetada para atender todos os requisitos dos produtos de sua fam?lia de produtos. Esses requisitos e a pr?pria LPS podem sofrer mudan?as ao longo do tempo em decorr?ncia de v?rios fatores, como por exemplo, evolu??o nos requisitos dos produtos, evolu??o no dom?nio de mercado para o qual os produtos foram projetados, evolu??o no processo de constru??o da LPS, evolu??o das tecnologias usadas para desenvolver os produtos. Para lidar com essas mudan?as, a LPS deve ser modificada e evoluir, visando n?o ficar obsoleta, e se adequar aos novos requisitos que surgem. A an?lise de impacto de mudan?as consiste em uma atividade que visa compreender e identificar quais conseq??ncias essas mudan?as causam ou causar?o na LPS. A an?lise de impacto na LPS pode ser apoiada por meio de rela??es de rastreabilidade, as quais identificam relacionamentos entre artefatos criados durante todas as fases do desenvolvimento de software. Apesar de existirem solu??es de an?lise de impacto baseadas em rastreabilidade para softwares e de rastreabilidade para LPS, h? uma car?ncia de solu??es de an?lise de impacto de mudan?as baseadas em rastreabilidade para LPS, pois as solu??es existentes n?o contemplam estimativas espec?ficas para o dom?nio da LPS. Assim, este trabalho prop?e um processo de an?lise de impacto e uma ferramenta associada para an?lise de impacto de mudan?as baseada em rastreabilidade de artefatos em uma LPS. Para tal, foi especificado um processo de an?lise de impacto de mudan?as que considera artefatos produzidos durante o desenvolvimento da LPS. Foi tamb?m implementada uma ferramenta a qual permite identificar artefatos e produtos da LPS afetados a partir de mudan?as em outros produtos, mudan?as em classes, mudan?as em features, mudan?as entre vers?es (releases) da LPS e mudan?as nos artefatos relacionados ? arquitetura base e ?s variabilidades. Por ?ltimo, os resultados obtidos foram avaliados atrav?s de m?tricas

Made available in DSpace on 2014-12-17T15:48:02Z (GMT). No. of bitstreams: 1 MatheusAS_DISSERT.pdf: 2078765 bytes, checksum: 519489af2ea8e5db40a4abaa98e99b28 (MD5) Previous issue date: 2010-11-18 / With the increase of processing ability, storage and several kinds of communication existing such as Bluetooth, infrared, wireless networks, etc.., mobile devices are no longer only devices with specific function and have become tools with various functionalities. In the business field, the benefits that these kinds of devices can offer are considerable, because the portability allows tasks that previously could only be performed within the work environment, can be performed anywhere. In the context of oil exploration companies, mobile applications allow quick actions could be taken by petroleum engineers and technicians, using their mobile devices to avoid potential catastrophes like an unexpected stop or break of important equipment. In general, the configuration of equipment for oil extraction is performed on the work environment using computer systems in desktop platforms. After the obtained configuration, an employee goes to equipment to be configured and perform the modifications obtained on the use desktop system. This management process equipment for oil extraction takes long time and does not guarantee the maintenance in time to avoid problems. With the use of mobile devices, management and maintenance of equipment for oil extraction can be performed in a more agile time once it enables the engineer or technician oil can perform this configuration at the time and place where the request comes for example, near in the oil well where the equipment is located. The wide variety of mobile devices creates a big difficulty in developing mobile applications, since for one application can function in several types of devices, the application must be changed for each specific type of device, which makes the development quite costly. This paper defines and implements a software product line for designing sucker-rod pumping systems on mobile devices. This product line of software, called BMMobile, aims to produce products that are capable of performing calculations to determine the possible configurations for the equipment in the design suckerrod pumping, and managing the variabilities of the various products that can be generated. Besides, this work performs two evaluations. The first evaluation will verify the consistency of the products produced by the software product line. The second evaluation will verify the reuse of some products generated by SPL developed / Com o aumento da capacidade de processamento, armazenamento e a variedade de tipos de comunica??o existentes, como Bluetooth, infravermelho, redes sem fio, etc., os dispositivos m?veis deixaram de ser apenas dispositivos com fun??o especifica e passaram a ser ferramentas com diversos tipos de funcionalidade. No campo empresarial os benef?cios que estes tipos de dispositivos oferecem s?o consider?veis, uma vez que a portabilidade permite que tarefas que antes s? poderiam ser executadas dentro do ambiente de trabalho, possam ser realizadas em qualquer lugar. No contexto de empresas de explora??o de petr?leo, aplica??es m?veis permitem que a??es r?pidas possam ser tomadas por engenheiros e t?cnicos de petr?leo, usando seus dispositivos m?veis, de forma a evitar poss?veis cat?strofes como a parada de um po?o ou quebra de um equipamento importante. Em geral, a configura??o de equipamentos para extra??o de petr?leo ? realizada no ambiente de trabalho usando sistemas computacionais em plataformas desktop. Ap?s a configura??o ser determinada, algum funcion?rio deve ir ao equipamento a ser configurado e executar as modifica??es obtidas na utiliza??o do sistema desktop. Este processo de gerenciamento de equipamentos para a extra??o de petr?leo demanda muito tempo e n?o garante a manuten??o em tempo h?bil de forma a evitar maiores problemas. Com a utiliza??o de dispositivos m?veis, o gerenciamento e manuten??o de equipamentos para extra??o de petr?leo pode ser realizada de forma mais ?gil, uma vez que permite que o engenheiro ou t?cnico de petr?leo possa realizar essa configura??o no momento e local aonde chega a solicita??o, por exemplo, pr?ximo ao po?o onde est? localizado o equipamento. A grande variedade de tipos de dispositivos m?veis gera uma grande dificuldade no desenvolvimento de aplica??es m?veis, uma vez que para que uma aplica??o possa funcionar em diversos tipos de dispositivos, a aplica??o deve sofrer altera??es para cada tipo especifico de aparelho, o que torna o desenvolvimento bastante custoso. Este trabalho define e implementa uma linha de produto de software para dimensionamento de bombeio mec?nico em dispositivos m?veis. Esta linha de produto de software, denominada BMMobile, tem como objetivo gerar produtos que sejam capazes de realizar c?lculos para determinar as configura??es poss?veis para os equipamentos no dimensionamento de bombeio mec?nico, al?m de gerenciar as variabilidades dos diversos produtos que podem ser gerados. Al?m disso, esse trabalho realiza duas avalia??es. A primeira avalia??o permite verificar a consist?ncia dos produtos produzidos pela linha de produto de software. A segunda avalia??o permite avaliar o reuso em alguns produtos gerados pela LPS desenvolvida

Made available in DSpace on 2014-12-17T15:48:02Z (GMT). No. of bitstreams: 1 HugoFM_DISSERT.pdf: 1847783 bytes, checksum: 58d9312a629dabdd3fe4b15c8dc44101 (MD5) Previous issue date: 2012-07-26 / The Exception Handling (EH) is a widely used mechanism for building robust systems. In Software Product Line (SPL) context it is not different. As EH mechanisms are embedded in most of mainstream programming languages (like Java, C# and C++), we can find exception signalers and handlers spread over code assets associated to common and variable SPL features. When exception signalers and handlers are added to an SPL in an unplanned way, one of the possible consequences is the generation of faulty family instances (i.e., instances on which common or variable features signal exceptions that are mistakenly caught inside the system). In this context, some questions arise: How exceptions flow between the optional and alternative features an LPS? Aiming at providing answers to these questions, this master thesis conducted an exploratory study, based on code inspection and static analysis code, whose goal was to categorize the main ways which exceptions flow in LPSs. To support the study, we developed an static analysis tool called PLEA (Product Line Exception Analyzer) that calculates the exceptional flows of LPSs, and categorize these flows according to the features associated with handlers and signalers. Preliminary results showed that some types of exceptional flows have more potential to yield failures in exceptional behavior of SLPs / O mecanismo de tratamento de exce??es ? amplamente utilizado para a constru??o de sistemas robustos. No contexto de Linhas de Produto de Software (LPSs) n?o ? diferente. Uma vez que mecanismos de tratamento de exce??es est?o embutidos nas principais linguagens de programa??o da atualidade (como Java, C# e C++), podemos encontrar sinalizadores e tratadores de exce??es espalhados entre os artefatos de c?digo associados a caracter?sticas (do ingl?s: features) opcionais e obrigat?rias de uma LPS. Quando tratadores ou sinalizadores de exce??es s?o adicionados a uma LPS de forma n?o planejada, uma das poss?veis conseq??ncias ? a gera??o de produtos falhos (i.e., produtos em que exce??es lan?adas por features vari?veis ou obrigat?rias s?o erroneamente tratadas). Neste contexto, surge a pergunta: Quais as consequ?ncias de se usar o mecanismo de tratamento de exce??es em LPSs? Com o objetivo de responder a esta pergunta, este trabalho conduz um estudo explorat?rio, baseado em inspe??o de c?digo e an?lise est?tica de c?digo, cujo objetivo foi caracterizar as principais formas em que exce??es fluem em LPSs. Para apoiar a realiza??o deste estudo desenvolvemos a PLEA (Product Line Exception Analyzer), uma ferramenta baseada em analise est?tica de c?digo que calcula os fluxos excepcionais de uma LPS e os classifica de acordo com as features associadas aos seus tratadores e sinalizadores. Resultados preliminares mostraram que alguns tipos de fluxos excepcionais tem mais potencial para originarem falhas no comportamento excepcional das LPSs

The education in Brazil shows a deficiency in the quality of teaching, so that many teachers and businessmen realize that students that complete the basic education are not ready to assume their role in society yet. One of the factors contributing to the low quality of education, according Papert, can be seen in the break of the incentive to search for new knowledge, which usually occurred when the student starts to go to school. A strategy adopted to motivate the student to search for new knowledge occurs through of constructionism, in which to learn about a particular content, the student needs to create some concrete material. The development of these concrete material may become easier through the use of computers and games that provide a virtual world in which the player has all the tools necessary to create an artifact about the subject studied. To facilitate the development of these games, which often fail to be completed due to the effort invested, the developers can use a Software Product Line, which is a software intensive production system for a particular domain. This paper presents an approach and the JIndie Software Product Line that aims to be a Software Product Line for developing constructionist games. To validate Software Product Line proposed in this work, a case study was carried out with the production of four games to assess the feasibility to implement constructionist games using JIndie, as well as to evaluate the performance and tools used in the process. The case study reveals a satisfactory result in game development capabilities, as well as a production with low complexity and effort by the game developer. / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / A educação no Brasil apresenta uma deficiência na qualidade de ensino, de forma que muitos professores e empresários sentem que os estudantes, ao se formarem ainda não estão prontos para assumir seu papel na sociedade. Um dos fatores que contribuem para a baixa qualidade do ensino, segundo Papert, pode ser observado na quebra do incentivo a busca de novos conhecimentos, ocorrida quando o estudante entra no colégio. Uma estratégia adotada para motivar o estudante buscar a novos conhecimentos ocorre através do construcionismo, no qual, o estudante para aprender sobre um determinado conteúdo por completo, necessita criar conteúdo concreto sobre o assunto estudado. O desenvolvimento desses conteúdos concretos pode se tornar mais fácil através do uso do computador e com jogos que permitem representar um mundo virtual no qual o jogador tenha todas as ferramentas necessárias para ter a liberdade de criar de sua forma um artefato concreto sobre o assunto estudado. Para facilitar o desenvolvimento desses jogos, que muitas vezes não chegam a ser concluídos devido ao esforço investido, pode-se optar pelo uso de uma Linha de Produto de Software, que se trata de um sistema de produção intensivo de softwares de um determinado domínio. Este trabalho apresenta uma abordagem e produção de uma Linha de Produto de Software, JIndie, que tem como objetivo ser uma Linha de Produto de Software para produção de jogos construcionistas. Para a avaliação da Linha de Produto proposta no trabalho, um estudo de caso foi realizado com a produção de quatro jogos com a finalidade de avaliar a viabilidade de desenvolver jogos construcionistas através do JIndie, como também avaliar o desempenho e as ferramentas utilizadas no processo. Os resultados do estudo de caso revelaram um feito satisfatório na capacidade de desenvolvimento dos jogos, como também uma produção com baixa complexidade e esforço por parte do desenvolvedor dos jogos.

The software development continues to become more competitive and demanding, placing pressure on developers. Changes in the international political climate have resulted in shrinking military budgets, putting developers of defence software under further pressure. At present, systematic reuse is probably the most realistic way of addressing this pressure by improving software development productivity and quality. Software product line (SPL) engineering provides a comprehensive approach to systematic software reuse and is becoming widely accepted. The focus of this interpretive case study was ground station software development in a small multidisciplinary project-centric company which produces avionics systems for military aircraft. The purpose of the study was to investigate the potential implementation of systematic software reuse in the company. The study consisted of three phases, a literature study, a contextualisation and a set of field interviews, and used elements of the Carnegie-Mellon Software Engineering Institute (SEI) Product Line Practice Framework to examine the suitability of SPL engineering for the company. The findings of the study highlight the potential challenges that SPL engineering poses for the company, and emphasise how the company's project-centric structure could impede its implementation of systematic software reuse. / Computing / M.Sc. (Information Systems)

Made available in DSpace on 2016-06-02T19:05:38Z (GMT). No. of bitstreams: 1 2623.pdf: 2743696 bytes, checksum: cc0c40ac7065c499f2cd408b70711f1d (MD5) Previous issue date: 2009-07-03 / Financiadora de Estudos e Projetos / This thesis presents an approach to Development based on Model-Driven Architecture, of Ubiquitous Applications Domain Software Product Lines. The approach uses Model-Driven Architecture to facilitate the modeling reuse of the same application in different architectures of the Ubiquitous Computing. With focus in the problem domain, the Software Product Lines core is developed and it is reused in the products construction. One of the assets that composed the Software Product Lines is the Ubiquitous Computing Framework, developed to attend the non functional requirements of Ubiquitous Computing. The CASE tool, called MVCASE, makes automatic part of the activities in the proposed approach. / Essa dissertação apresenta uma Abordagem para Desenvolvimento baseado em Model-Driven Architecture, de Linha de Produto de Software orientada a domínios de Aplicações Ubíquas. A abordagem utiliza a Model-Driven Architecture para melhor atender as diversidades de arquiteturas da Computação Ubíqua e facilitar o reuso. Com foco no domínio do problema, desenvolve-se o Core Asset, núcleo da Linha de Produto de Software, que é reutilizado na construção dos produtos derivados da linha. Um dos artefatos do Core Asset é Ubiquitous Computing Framework construído para atender os requisitos não funcionais da Computação Ubíqua. Uma ferramenta CASE, denominada MVCASE, automatiza grande parte do processo da Model-Driven Architecture, desde a modelagem até a geração parcial de código.