Made available in DSpace on 2019-04-05T23:01:07Z (GMT). No. of bitstreams: 0 Previous issue date: 2002-06-14 / The software quality has had an increasing importance as a crucial factor to keep the competitive level of the organizations. The evaluation is an indispensable activity in the quality obtainment and guarantee, both in a development process and in a final product. It is the main way to know how to plan, to execute and to achieve quality improvement. In this work, the AdeQuaS tool is modeled and implements the stages defined on the Fuzzy Model to Software Quality Evaluation, supplying automated support to quality metrics application, evaluation procedure definition and quality level attainment of evaluated object. Two applications are presented as study cases. The first is the evaluation of Software Requirements Specifications quality. The second is the evaluation of e-commerce websites quality. / A qualidade de software tem tido uma importância crescente como fator crucial de competitividade nas organizações. A avaliação é uma atividade imprescindível na obtenção e garantia da qualidade tanto no processo de desenvolvimento de software, quanto no produto final. É o principal meio de se saber como planejar, executar e alcançar a melhoria. Neste trabalho, a ferramenta AdeQuaS é modelada e implementa as etapas definidas no Modelo Fuzzy de Avaliação de Qualidade de Software, oferecendo suporte automático para aplicação de métricas de qualidade, definição do procedimento de avaliação e obtenção do nível de qualidade do objeto avaliado. Duas aplicações são apresentadas como estudo de casos. A primeira é a avaliação da qualidade de Especificações de Requisitos de Software; a segunda é a avaliação da qualidade de websites de comércio eletrônico.

Made available in DSpace on 2019-04-05T23:01:18Z (GMT). No. of bitstreams: 0 Previous issue date: 2002-12-17 / The quality of software components is important for the quality of componentbased applications and for attaining the main objectives of Component-based Development (CBD), low cost and high productivity and quality. The quality characteristics, according to ISO/IEC 9126 standard, can be used as goals to be reached in the development, in the selection and in the acquisition of components and, also, as factors in the prediction of properties of final applications. This work identifies and organizes the main quality characteristics for software components and, also, defines quality dimensions that influence in the degree of importance of those characteristics. The survey of the characteristics was based on the specialized literature. Research was undertaken, with CBD practitioners, to rank the quality characteristics and the results were obtained from a software quality evaluation model. / A qualidade de componentes de software é importante para a qualidade de aplicações baseadas em componentes e para obtenção dos principais objetivos do Desenvolvimento Baseado em Componentes (DBC), baixo custo e alta produtividade e qualidade. As características de qualidade, segundo a norma ISO/IEC 9126, podem ser utilizadas como metas a serem atingidas no desenvolvimento, na seleção e na aquisição de componentes e, também, como fatores na predição de propriedades de aplicações finais. Este trabalho identifica e organiza as características de qualidade de maior relevância para componentes de software e define dimensões de qualidade que influenciam no grau de importância das mesmas. O levantamento dessas características foi baseado em literatura especializada. Realizou-se, ainda, uma pesquisa de campo, com especialistas em DBC, visando a hierarquização dessas características de qualidade, cujos resultados foram obtidos através de um modelo de avaliação da qualidade de software.

Made available in DSpace on 2019-04-05T23:01:04Z (GMT). No. of bitstreams: 0 Previous issue date: 2002-06-14 / Function Point Analysis (FPA) is a largely used technique to estimate the size of development projects, enhancement projects or applications already installed. This work proposes the use of concepts and properties from fuzzy set theory to extend FPA into FFPA (Fuzzy Function Point Analysis). Fuzzy theory seeks to build a formal quantitative structure capable of emulating the imprecision of human knowledge. With the function points generated by FFPA, the functionality of the project was better represented than it was through FPA. Thus, derived values such as costs and terms of development can be determined with more precision than the values generated from the data supplied by FPA. / A técnica de Análise de Pontos por Função (FPA) é largamente utilizada para se estimar tamanho de projetos de desenvolvimento, de manutenção ou aplicações de software já implantadas. Este trabalho propõe a utilização de conceitos e propriedades da teoria dos conjuntos fuzzy, para estender a FPA em FFPA (Análise de Pontos por Função Fuzzy). A teoria fuzzy busca construir uma estrutura formal quantitativa, capaz de capturar as imprecisões do conhecimento humano. Com os pontos por função produzidos através da FFPA, a funcionalidade do projeto ficou melhor representada. Conseqüentemente, valores derivados como prazo e custo de desenvolvimento podem ser obtidos com maior precisão do que os gerados através dos valores fornecidos pela FPA.

Made available in DSpace on 2019-04-05T23:04:59Z (GMT). No. of bitstreams: 0 Previous issue date: 2005-08-05 / The software engineering argues the implantation of activities of size estimates, effort, period and cost, as forms of improving the software projects planning and tracking. In spite of there being several techniques of estimates, the use of the same ones in software companies is not still such a common practice. The technique UCP (Use Case Points), for instance, it is adherent to object-oriented software products and based on use cases. However, they have been finding some situations where there are difficulties of obtaining resulted fully satisfactory when using the UCP. This work presents an extension of the technique UCP that is TUCP (Technical Use Case Points) being looked for a calculation more refined for the projects effort. Besides, TUCP allows a more detailed vision of estimates in the main stages of the software cycle life, making possible the accomplishment of refinements of those estimates for an accompaniment more effective of the project. / A engenharia de software recomenda a implantação de atividades de estimativas de tamanho, esforço, prazo e custo, como formas de melhorar o planejamento e o acompanhamento de projetos de software. Apesar de haver várias técnicas de estimativas, a utilização das mesmas em empresas de software ainda não é uma prática tão comum. A técnica UCP (Pontos de Caso de Uso), por exemplo, é aderente a produtos de software orientados a objetos e baseados em casos de uso. No entanto, têm-se encontrado algumas situações, onde há dificuldades de se obter resultados plenamente satisfatórios ao se utilizar a UCP. Este trabalho apresenta uma extensão da técnica UCP a TUCP (Pontos de Caso de Uso Técnico) buscando-se um cálculo mais acurado para o esforço de projetos. Além disso, a TUCP permite uma visão mais detalhada de estimativas nas principais etapas do ciclo de vida do software, possibilitando a realização de refinamentos dessas estimativas para um acompanhamento mais efetivo do projeto.

Made available in DSpace on 2019-04-05T23:05:42Z (GMT). No. of bitstreams: 0 Previous issue date: 2006-09-12 / One of the main objectives of the requirements engineering is to construct software requirement as easy to understand as possible and that they are consistent to both customers and to the developments. To assist in the agreement of these requirements between the involved parts, this work propose an ontology for the software requirement engineering, that aims to facilitate the understanding of its concepts, and to improve the communication between developers and customers. This will prevent future problems in the software life cycle. The ontology proposed in this work has been applied to three different systems, two in the financial application systems domain and one on commercial area. / Um dos principais objetivos da engenharia de requisitos é construir requisitos de software de fácil entendimento e que sejam consistentes tanto para os clientes, quanto para os desenvolvedores. Para auxiliar no entendimento desses requisitos entre as partes envolvidas, este trabalho propõe uma ontologia para a engenharia de requisitos de software, com o objetivo de facilitar a compreensão de seus conceitos, e propiciar a melhoria da comunicação entre desenvolvedores e clientes, diminuindo assim problemas posteriores ao longo do ciclo de vida do software. A ontologia proposta neste trabalho foi aplicada a três sistemas, dois de domínio de aplicação financeira e um da área comercial.

Orientador: Eliane Martins / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-09-11T21:22:23Z (GMT). No. of bitstreams: 1 Almeida_ErikaReginaCamposde_M.pdf: 2024977 bytes, checksum: 283c040eb38feebecb81300c009c2567 (MD5) Previous issue date: 2012 / Resumo: A automação da geração e da execução de casos de teste está de acordo com o grande desafio na área de desenvolvimento de software que é fazer mais com menos recursos. Entretanto, para unir estes dois processos, ainda é necessário fazer a ponte entre o nível de especificação do Sistema em Teste (SeT) e sua respectiva implementação. O processo de geração de casos de teste usualmente requer uma representação formal do SeT (baseada nos documentos de especificação do SeT) e gera casos de teste abstratos, no sentido que eles estão no mesmo nível de detalhamento das especificações. Já a execução automática de casos de teste necessita de casos de teste executáveis, ou seja, aqueles que contêm detalhes de implementação do SeT para serem executados sem intervenção manual. Para usar automação desde a fase de projeto de teste até a fase de execução, é necessário preencher a lacuna entre o caso de teste abstrato (artefato de saída da geração automática de casos de teste) e o executável (artefato de entrada da execução automática de teste), pois eles estão em níveis de abstração diferentes. Usualmente, alguém com habilidades de programação realiza o processo de transformação do nível abstrato para o de implementação, despendendo muito esforço e tempo. Neste trabalho, avaliamos as propostas para mapeamento automático de casos de teste abstratos em executáveis existentes na literatura que estão de acordo com Teste Dirigido por Modelo (MDT), abordagem cujo intuito é gerar automaticamente artefatos de teste de software em diferentes níveis de abstração aplicando regras de transformação. Além de avaliar as propostas, escolhemos uma delas para instanciar para aplicações Web (as aplicações que mais cresceram nos últimos anos, tanto em uso, como em nível de complexidade), mostrando quais são os passos necessários para transformar os casos de teste abstratos em executáveis, levando em conta que existem bibliotecas especializadas no suporte à escrita deste último. Para avaliar a aplicabilidade da solução em aplicações Web reais, realizamos o estudo de caso usando aplicações Web de grande porte, duas delas de uso nacional e outra disseminada em escala mundial. Além disso, foi realizado o processo completo de teste (geração dos casos de teste abstratos; uso da proposta de instanciação, para aplicações Web, do método para transformar os casos de teste abstratos em executáveis; e execução dos testes), ilustrando a factibilidade da solução / Abstract: Automating the generation and execution of test cases meets the major challenge in software development that is doing more with fewer resources. However, to bring together these two processes, it is still necessary to bridge the gap between the specification level of the System under Test (SUT) and its respective implementation. The process of generating test cases usually requires a formal representation of the SUT (based on its specifications) and generates abstract test cases, in the sense that they are on the same detailing level of the specifications. On the other hand, the automatic execution of test cases needs executable test cases, i.e., those that contain implementation details of the SUT to run without manual intervention. So, to use automation from the test design phase to the test execution one, it is necessary to fill the gap between the abstract test case (output artifact of the automatic generation of test cases) and executable one (input artifact for the automatic test execution), once they are at different abstraction levels. Usually, someone with programming skills makes the process of transforming the abstract level to the implementation one, spending much effort and time. In this work, we evaluate the existing literature proposals for automatic mapping of abstract test cases into executable ones that were designed according to Model Driven Testing (MDT), one approach whose aim is to automatically generate software testing artifacts in different levels of abstraction by applying transformation rules. In addition to evaluating the proposals, we chose one to instantiate for Web applications (the kind of applications that have grown most in recent years, either in use as level of complexity), showing what are the steps needed to transform the abstract test cases into executable ones, taking into account that there are specialized libraries to support the writing of the latter one. To evaluate the solution applicability in real Web applications, we conducted case studies using large Web applications (two national ones and another which is worldwide used). In addition, we performed the whole test process (generation of abstract test cases; use of the proposed instantiation for web applications of a method to transform the abstract test cases into executable ones; and running the tests), illustrating the solution feasibility / Mestrado / Ciência da Computação / Mestra em Ciência da Computação

In recent years many tools and techniques have been proposed and even implemented which support maintenance programmers to gain an understanding of existing source code. However, studies have found that some tools are of marginal benefit and not appropriate for all maintenance tasks. This may be due to tools having been designed with little regard to the common behavioural practices that occur during software maintenance tasks because the current state of knowledge of such practices is quite limited. The aim of this study is to alleviate the above situation by performing a detailed behavioural analysis of software maintenance tasks undertaken under laboratory experiment conditions. To support this aim an experiment was conducted in which twenty-nine student subjects experienced in C programming independently undertook one of two maintenance tasks on the same C program in a university environment. The data produced from the experiment included subjects??? interactions with documents and code and their responses to program comprehension questions at the end of the task. The results indicate that maintenance task success is associated with a heightened concentration on high-level procedures that control the execution of lower level procedures. Among subjects, IT industry experience was linked to efficient comprehension of program and task documentation and the performance of more code searches. In general, code searches mainly involved searches for procedure name references. Compared to subjects undertaking the enhancement task, subjects performing the complex corrective task utilised program documentation more but also obtained a greater understanding of the elementary operations and control-flow of the program. In addition, this study illustrates a method to identify common information usage strategies from the recorded maintenance behaviour of subjects. Largely unsuccessful attempts were also made to sequentially analyse maintenance behaviour. This lack of success is possibly attributable to the as-needed comprehension approach adopted by subjects. The results of this research suggest that cost-effective maintenance of software is best supported using tools implementing facilities for feature location and visualisation of the control-flow of a program. The former facility would be most helpful to maintainers undertaking corrections, whereas the latter would particularly assist maintainers undertaking enhancements.

<p>This thesis deals with the creation of a library that can be used in the construction of</p><p>network protocols. The library provides functions that are useful for organizing protocols as</p><p>stacks of layers and for processing packets. The thesis implements the main concepts of the</p><p>special purpose language, Morpheus [2]. Morpheus was designed by Mark Bert Abbott at</p><p>the University of Arizona in 1994 but has not yet been implemented. We have implemented</p><p>the main concepts of Morpheus by using a concurrent programming language called MPD</p><p>(Multithreaded, Parallel and Distributed) [5] and a programming discipline known as</p><p>reactive objects. Morpheus is based on the concept of protocol shapes. A protocol shape is</p><p>a template for implementing protocols with certain functions. Three main protocol shapes</p><p>are router, sequencer and multiplexor. The protocol implementer constructs protocols by</p><p>extending these shapes. Our library implements these shapes as objects. Each of these</p><p>shapes in turn extends from a base protocol object called Protocol. We have used reactive</p><p>objects for allowing communication between protocols.</p>

<p>Testing in Agile development frameworks has engaged the concentration of software developers throughout the world. The research regarding this testing is however limited. This paper comprises a literature survey study, which intends to categorize and examine the current existing testing frameworks in agile methodology. The comparative study is done with the Test Driven Development (TDD) and Agile Model Driven Development (AMDD) techniques. The results show the benefits and drawbacks of the current existing testing frameworks in agile methodology in general. However many techniques still make every effort to get the general solutions. Basing on our results general ideas are suggested regarding the testing frameworks in agile methodology.</p>

<p>This research paper discusses the software engineering field. In which many problems exist because the software engineering field consists of different nodes and each node in turn contains a unique field. The paper also explores problems within the software engineering field as well as the market situation and the reasons behind the software engineering field in Academia are lagging behind. Here some guidelines are presented for Academia as well as industry for the improvement/help of the software engineers. The implication of an increasingly geographically mobile workforce mean that students educated in Asian regions, in particular, are facing problems due to differences in their education and culture from those in the West. In addition we present several issues concerning online studies vs. traditional studies and analyze the findings</p>