yes / Welcome to the 16th edition of the Advances in Model-Based Testing Workshop (A-MOST 2020) held on March 23rd, 2020 in Porto as part of ICST 2020, the IEEE International Conference on Software Testing, Verification and Validation.

Orientador: Cecilia Mary Fischer Rubira / Dissertação (mestrado) - Universidade Estadual de Campinas,Instituto de Computação / Made available in DSpace on 2018-08-08T19:35:35Z (GMT). No. of bitstreams: 1 Tizzei_LeonardoPondian_M.pdf: 1173368 bytes, checksum: dd09b9de9a47db9f4f82b8f63dcf35a7 (MD5) Previous issue date: 2007 / Resumo: No contexto do Desenvolvimento Baseado em Componentes(DBC), o elo de ligação entre desenvolvedores e consumidores de componentes de software são os repositórios de componentes, onde eles são adicionados por seus desenvolvedores e recuperados pelos integradores de sistemas. Considerando um cenário de evolução, onde componentes são modificados, são imprescindíveis modelos de evolução de componentes para definir uma abordagem sistemática de mudanças. Elas podem ocorrer, por exemplo, na especificação ou implementação de um componente e o repositório de componentes deve dar apoio à evolução uma vez que ela é parte inerente do processo de desenvolvimento de software. Contudo, assim como o software, modelos de evolução são modificados para acompanhar o desenvolvimento tecnológico e as necessidades de seus usuários. Além disso, diferentes produtores de componentes podem possuir modelos distintos. Este trabalho apresenta uma infra-estrutura de suporte à evolução em um repositório de componentes, para apoiar serviços de DBC, como a conversão de componentes para outros modelos de implementação, extração de metainformação de código-fonte de componentes, evolução de componentes e verificação de modelos de implementação de componentes. No caso particular desta dissertação, o repositório de componentes escolhido é o Rigel, que foi estendido para dar suporte à evolução de componentes. O repositório Rigel oferece as condições necessárias para adoção de um modelo de evolução de componentes, através da utilização de um padrão de metadados de componentes chamado RAS. Ferramentas de software ajudam a aumentar a produtividade de desenvolvedores e evitar tarefas repetitivas. Além disso, atividades de modificação são sujeitas a erros humanos. Portanto, foram desenvolvidas quatro ferramentas para dar suporte ao modelo de evolução SACE e ao modelo de implementação de componentes COSMOS. As ferramentas foram construÍdas com base em um framework de componentes baseado em regras que usa um motor de inferência chamado Drools. Este framework de componentes externaliza as regras da aplicação, garatindo uma maior modificabilidade, característica que é essencial para que as ferramentas possam evoluir em conformidade com os modelos apóiam / Abstract: In the Component-Based Development (CBD), the link between software component developers and consumers are component repositories where software components are checkedin by their developers and checked-out by their systems integrators. Considering an evolution scenario, when components are modified, it is essential component evolution models in order to define a systematic approach to component changes. These modifications can occur, for instance, in the component specification and implementation, and component repositories should support these kind of evolutions. However, component evolution models themselves can be modified to follow technological development and different user's needs. Furthermore, different component producers may also have distinct models. This work presents an infrastructure to support evolution in component repositories, to support various CBD services, such as component conversion to other implementation models, extraction of metainformation from the source code of components, component evolution and check implementation models. Particularly, in this work, the component reposítory chosen was Rigel (developed at IC-UNICAMP), which was extended to support component evolution. The Rigel repository provides necessary conditions to adopt a component evolution model, by using an extensibIe component metadata pattern called RAS specification. Software tools heIp to increase developer's productivity and to avoid repetitive tasks. Furthermore, human modification activities are error prone. Therefore, we have developed four tools to support the SACE evolution model and the COSMOS component implementation model. These tools were developed using a rule-based framework which is based on an inference engine called Drools. This component framework is important to externalize the application rules, to guarante a greater modifiability, which is essential for the evolution of the tools in conformity with the models they support / Mestrado / Mestre em Ciência da Computação

Orientador: Cecilia Mary Fischer Rubira / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-15T07:02:41Z (GMT). No. of bitstreams: 1 Assis_WendelMaltade_M.pdf: 3475428 bytes, checksum: a93eaa26b089299962c102e6c3a037c5 (MD5) Previous issue date: 2009 / Resumo: O uso de Linhas de Produto de Software é uma prática comum entre as empresas de software, tendo como objetivo promover o desenvolvimento de um conjunto de produtos de software relacionados através da reutilização de um núcleo comum de ativos de software. Dentre estas empresas, podemos mencionar a Motorola, cujo ambiente de desenvolvimento em que múltiplas linhas de produto são mantidas em paralelo serviu de motivação para este trabalho. Na prática, a complexidade de alguns tipos de negócios apoiados por linhas de produto implica em mudanças na forma como a adoção da abordagem é sugerida pela literatura. Em particular na Motorola, as linhas de produto são baseadas em componentes e a arquitetura da linha de produto possui diversos pontos de variação, onde variantes de componentes representando diversas alternativas de projeto podem ser escolhidas. Além disso, várias linhas de produto são mantidas em paralelo e os componentes e suas variantes podem ser compartilhados entre elas. Neste contexto, a evolução de componentes é uma tarefa complexa, pois a inclusão de novas características nas variantes dos componentes pode impactar não somente a arquitetura e os ativos de uma única linha de produto, mas também das diversas linhas que as utilizam. A principal contribuição deste trabalho é a documentação de uma família de padrões de evolução de componentes compartilhados por múltiplas linhas de produto de software. Além desta família de padrões, também é apresentado um processo para auxiliar na análise do padrão de evolução a ser adotado para implementar uma determinada requisição de mudança / Abstract: The Software Product Line approach is becoming widely used by software companies, whose goal is to promote the development of a set of related software products through the reuse of a common core of software assets. Among these companies, we can mention Motorola, whose development environment where multiple software product lines are maintained in parallel served as the motivation for this work. In practice, the complexity of some types of businesses supported by product lines involves changes in how the adoption of the approach is suggested by the literature. At Motorola, the product lines are based on components and the product line architecture has many variation points, where variants of components representing various design alternatives can be chosen. In addition, several product lines are maintained in parallel and the components and their variants can be shared among them. In this context, the evolution of components is a complex task, because the inclusion of new features in variants of the components can impact not only the architecture and assets in a single product line but also on many products lines that are using them. The main contribution of this work is the documentation of a family of component evolution patterns that are shared between multiple software product lines. Besides that, a process to assist in analyzing the evolution pattern to be taken to implement a specific change request is presented / Mestrado / Engenharia de Software / Mestre em Ciência da Computação

Orientador: Mario Jino / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de Computação / Made available in DSpace on 2018-07-23T05:23:57Z (GMT). No. of bitstreams: 1 Granja_Ivan_M.pdf: 9510547 bytes, checksum: 4248dfe94031c5719e837aa99627acca (MD5) Previous issue date: 1997 / Resumo: Este trabalho apresenta as principais características de uma ferramenta de apoio ao teste de regressão estrutural baseado na família de Critérios Potenciais-Usos e uma estratégia para sua aplicação. A ferramenta, denominada RePoKe- Tool (Regression Testing support for Potencial-Uses Criteria Tool), pode ser aplicada em unidades (e.g., funções, procedimentos) que foram testadas através da ferramenta de teste POKE-TOOL e sofreram manutenção corretiva (teste de regressão corretivo) ou então adaptativa ou perfectiva (teste de regressão progressivo), utiliza estratégia seletiva para identificar apenas os elementos requeridos para o teste estrutural (caminhos e associações) que foram inseridos ou modificados após essa manutenção e sugere um subconjunto dos casos de teste originais que, potencialmente, cobre esses elementos. Além disso, configura e atualiza os arquivos necessários para que a POKE-TOOL possa realizar o teste de regressão. o trabalho apresenta também estudos de casos que mostram a viabilidade da aplicação de uma estratégia de seleção de casos de testes de regressão baseada em conceitos de teste funcional, com objetivo de atingir um bom índice de cobertura de elementos requeridos selecionados para o teste de regressão estrutural. Os resultados obtidos através desses estudos de casos contribuíram para a definição de um Guia de Referência para Programadores de Manutenção, cujo objetivo é diminuir os altos custos envolvidos com o Teste de Regressão, sem relevar para segundo plano o principal objetivo de qualquer atividade de teste: a revelação de defeitos no software / Abstract: This work presents the most relevant concepts and characteristics of a regression testing tool, based upon Potential Uses Criteria and a strategy to be applied. RePoKe- Tool (Regression Testing support for Potential-Uses Criteria Tool) can be used in units (e.g., functions and procedures). These units, previously tested by POKE-TOOL testing tool, have been modified either by means of a corrective maintenance (which implies in corrective regression testing) or by means of an adaptive or perfective maintenance (which implies in progressive regression testing). This regression testing toei uses a selective strategy to identify modified and new required elements for white-box testing (paths and associations) and select a subset of original test cases (used in original testing procedures) which potentialiy may cover these elements. Furthermore, the POKE-TOOL environment is reconfigured to avoid regression testing procedures. This work presents, additionaliy, a study of cases that show a selection strategy based upon black-box testing concepts that obtain an expressive cover of white-box required elements. The results help the definition of a guideline to support maintenance programming activities, whose objectives are to save cost and, above all, to reveal faults in modified software / Mestrado / Mestre em Engenharia Elétrica

Estágio realizado na Critical Software, S. A / Tese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 2009

Software defect detection research typically focuses on individual inspection and testing techniques. However, to be effective in applying defect detection techniques, it is important to recognize when to use inspection techniques and when to use testing techniques. In addition, it is important to know when to deliver a product and use maintenance activities, such as trouble shooting and bug fixing, to address the remaining defects in the software.<p>To be more effective detecting software defects, not only should defect detection techniques be studied and compared, but the entire software defect detection process should be studied to give us a better idea of how it can be conducted, controlled, evaluated and improved.<p>This thesis presents a self-evolving software defect detection process (SEDD) that provides a systematic approach to software defect detection and guides us as to when inspection, testing or maintenance activities are best performed. The approach is self-evolving in that it is continuously improved by assessing the outcome of the defect detection techniques in comparison with historical data.<p>A software architecture and prototype implementation of the approach is also presented along with a case study that was conducted to validate the approach. Initial results of using the self-evolving defect detection approach are promising.

Software defect detection research typically focuses on individual inspection and testing techniques. However, to be effective in applying defect detection techniques, it is important to recognize when to use inspection techniques and when to use testing techniques. In addition, it is important to know when to deliver a product and use maintenance activities, such as trouble shooting and bug fixing, to address the remaining defects in the software.<p>To be more effective detecting software defects, not only should defect detection techniques be studied and compared, but the entire software defect detection process should be studied to give us a better idea of how it can be conducted, controlled, evaluated and improved.<p>This thesis presents a self-evolving software defect detection process (SEDD) that provides a systematic approach to software defect detection and guides us as to when inspection, testing or maintenance activities are best performed. The approach is self-evolving in that it is continuously improved by assessing the outcome of the defect detection techniques in comparison with historical data.<p>A software architecture and prototype implementation of the approach is also presented along with a case study that was conducted to validate the approach. Initial results of using the self-evolving defect detection approach are promising.

Thesis (doctoral)--University of Oulu, 2000. / Includes bibliographical references. Also available on the World Wide Web.

Thesis (M.S.)--Worcester Polytechnic Institute. / Keywords: formal analysis; active interfaces; Z notations; EJ. Includes bibliographical references (p. 97-99).

The case of the software industry in Ireland is particularly interesting as it is a unique example of a government led innovation in attracting and fostering the development of a knowledge based industry. Using a previous work of Eileen Drew (1994) as a starting point it tracks the growth of the industry in the 1990’s and into the 21st century during a boom period in the Irish economy known as the Celtic Tiger. Growth is measured by macro-economic factors such as employment and exports. In this 15 year period Ireland increased employment in the software industry from 8,000 to over 30,000 people and its software exports from 1 to 15 billion euro. The government’s influence is examined through the National Development Plans, The Strategy for Science Technology and Innovation 2006-2013 and by investigating the roles of the state sponsored bodies. Combining various secondary sources it gives a breakdown of the modern software industry in the areas of export, specialization, firm size and type. Ireland’s competitiveness and productivity environment is inspected. The thesis highlights industry problems including: 1. Lack of software graduates, 2. Over dependence upon foreign investment, 3. Inability of indigenous software companies to grow, 4. Loss of competitive advantage. While influencing factors such as geography and demographics, which contributed to the software industry’s success story are impossible to replicate, there are lessons to be learned of how a government led, innovative, consistent and educational based policies combined, with a business friendly environment, can be used to transform a struggling economy into a modern knowledge based one. / cjm1020s@gmail.com