The study of the software development process is a relatively new research area but it is growing rapidly. This development process, also called 'the software life cycle' or 'the software process', is the methodology used throughout the industry for the planning, design, implementation, testing and maintenance that takes place during the creation of a software product. Over the years a variety of different process models have been developed. From the numerous process models now available, project managers need validation of the choice he/she has made for a software development model that he/she believes will provide the best results. Yet the quality software so sought after by software project managers can be enhanced by improving the development process through which it is delivered. Well tested, reliable evidence is needed to assist these project managers in choosing and planning a superior software process as well as for improving the adopted software process. While some guidelines for software process validation and improvement have been provided, such as CMMI, quantitative evidence is, in fact, scarce. The quantitative evidence sometimes may not be able to be obtained from high level processes that refer to a planned process model, such as a waterfall model. Furthermore, there has been little analysis of low level processes. These low level processes refer to the actions of how a development team follow a high level software process model to develop a software product. We describe these low level processes as project enactment. Normally there is a gap between the high level software process and the project enactment. In order to improve this software development process, this gap needs to be identified, measured and analyzed. In this dissertation, we propose an approach that examines the deviation between a planned process model and the project enactment of that plan. We measure the discrepancy from two aspects: consistency and inconsistency. The analytical results of the proposed approach, which include both qualitative and quantitative data, provide powerful and precise evidence for tailoring, planning and selecting any software process model. The entire approach is composed of four major phases: 1) re-presentation of the planned process model, 2) pre-processing the low level process data, 3) process mining, and 4) analysis and comparison of the recovered process model and planned process model. We evaluate the proposed approach in three case studies: a small, a medium, and a large-sized project obtained from an industrial software development organization. The appropriate data on low level processes is collected and our approach is then applied to these projects individually. From each case study we then performed a detailed analysis of the inconsistencies that had surfaced as well as the consistencies between the plan and the enactment models. An analysis of the inconsistencies revealed that several 'agile' practices were introduced during the project's development even though the planned process model was initially based on 'ISO-12207' instead of the 'agile' method. In addition, our analysis identifies the patterns in the process that are frequently repeated. The outcome of the case studies shows that our approach is applicable to a range of software projects. The conclusions derived from these case studies confirmed that our approach could be used to enhance the entire software development process, including tailoring and assessment.

Med detta kandidatarbete strävar vi efter att utveckla en förståelse och ett intresse för ljuddesignens berättande funktion. Detta strävar vi efter genom att tillämpa ett rhizomatiskt perspektiv i vår designprocess samt försök till att närma oss en icke-linjär designmetodik. Det rhizomatiska perspektivet används som en källa för inspiration, en väg till att finna nya lösningar och verktyg till berättandet. Vårt prövande av ljuddesignen gjordes i en filmproduktion där vi som ljuddesigners gjorde försök till att väva in ljuddesign under hela projektets gång och arbeta proaktivt för att skapa utrymme för vår design. / With this bachelor thesis we seek to expand the understanding and interest of the narrative potential in sound design. We aim to do this by applying a rhizomatic perspective to our design process and attempt to approach a non-linear design method. The rhizomatic perspective is used as a source of inspiration, a way of finding new narrative tools and solutions. The testing of sound design was made in a film production where we, as sound designers, made attempts to weave sound design into the whole course of the project and work proactively to create space for our design.

TORRES FILHO, Ari do Amaral, Análise da utilização de métodos ágeis no desenvolvimento de ambientes virtuais de aprendizagem: um estudo de caso do Solar 2.0. 2014. 158 f. : Dissertação (mestrado) - Universidade Federal do Ceará, Centro de Ciências, Departamento de Computação, Fortaleza-CE, 2014. / Submitted by guaracy araujo (guaraa3355@gmail.com) on 2016-05-31T19:51:19Z No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Approved for entry into archive by guaracy araujo (guaraa3355@gmail.com) on 2016-05-31T19:51:40Z (GMT) No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) / Made available in DSpace on 2016-05-31T19:51:40Z (GMT). No. of bitstreams: 1 2014_dis_aatorresfilho.pdf: 5052662 bytes, checksum: bbc494f5731e2ba4a447896641ee5d11 (MD5) Previous issue date: 2014 / In the last two decades there has been considerable progress in the use of Information Technologies and Digital Communication in the process of teaching and learning, both in the form of classroom education as distance. In this context, the use of Virtual Learning Environments - software designed to support the courses via the Internet - is growing and access becoming increasingly diverse, ranging from desktop computers to mobile smartphones. Thus, the complexity of creating these environments becomes increasingly technical and requires Software Engineering and Project Management always better to ensure product quality and customer satisfaction generated. Given such a scenario, this paper proposes the use of Agile methodologies in the development and project management of virtual environments as a more interesting way than traditional software delivery based only on product quality, forgetting often , customer satisfaction and motivation of developers. This paper reports the adoption of agile methodologies in the development of the SOLAR AVA 2.0, showing that it is possible to succeed in both the technical level and at the organizational and personally with the adoption of agile practices in the development of AVAs that can be proven through experiments done with the satisfaction surveys with users and project developers. / Nas duas últimas décadas houve um considerável avanço no uso de Tecnologias da Informação e Comunicação Digitais no processo de ensino e aprendizagem, tanto na modalidade de Educação presencial quanto a distância. Neste contexto, o uso de Ambientes Virtuais de Aprendizagem - softwares criados para o suporte a cursos através da Internet - vêm crescendo e seu acesso se tornando cada vez mais diversificado, indo de computadores desktop a celulares smartphones. Desta forma, a complexidade de criação destes ambientes se torna cada vez maior e exige técnicas de Engenharia de Software e Gestão de Projetos cada vez melhores para garantir a qualidade do produto gerado e a satisfação do cliente. Tendo em vista tal cenário, o presente trabalho propõe o uso de Metodologias Ágeis tanto no desenvolvimento quanto na gestão de projetos de ambientes virtuais como uma solução mais interessante que a tradicional forma de criação de softwares baseada somente na qualidade do produto, esquecendo, muitas vezes, a satisfação do cliente e a motivação dos desenvolvedores

[pt] Métodos Ágeis são estratégias recentes na Engenharia de Software (começaram a se popularizar em 2001), que surgiram com a promessa de serem flexíveis e adaptáveis - características muito importantes para lidar com constantes mudanças de requisitos em projetos. O Scrum, método ágil estudado neste trabalho, necessita de uma infraestrutura adequada para gerar benefícios ao time que o utiliza. Neste estudo, implementou-se o Scrum, com o auxílio de uma infraestrutura adequada de ferramentas e processos, em uma organização que não utilizava qualquer tipo de gerenciamento de projetos. A partir do estabelecimento de algumas metas com o apoio do modelo GQM, buscou-se a melhoria nas métricas relacionadas e os resultados estão detalhados neste presente trabalho. / [en] Agile methodology is a recent Software Engineering strategy (it became popular in 2001) that was created to be flexible and adaptable enough - characteristic very import to deal with constant requirements changes during a project lifecycle. Scrum, the agile methodology used during this study, requires an adequate infrastructure in order to offer its benefits. This study implemented Scrum and an adequate infrastructure of processes and tools to support it, inside a organization that didn’t use any kind of project management before. With the establishment of some goals using the GQM model, some improvements were expected and the results are detailed in this study.

Linhas de produtos de software (LPS) são coleções de sistemas que compartilham características comuns, desenvolvidas de forma sistemática a partir de um conjunto comum de ativos centrais. Dentre as técnicas propostas por vários autores para o desenvolvimento de LPS, dois padrões podem ser observados: o processo de desenvolvimento geralmente é sequencial e o foco do projeto (design) costuma estar em interesses técnicos, como alocação de componentes e separação em subsistemas, e não em um modelo de domínio. Embora essas práticas sejam reportadas como bem-sucedidas, um outro paradigma de desenvolvimento, baseado em métodos ágeis e em um conjunto de princípios de projeto conhecido como domain-driven design, é apresentado neste trabalho e pode produzir resultados mais satisfatórios, comparados aos métodos tradicionais. Essa hipótese é sustentada por comparações entre padrões de modelagem e por um estudo de caso feito neste trabalho / Software product lines (SPL) are collections of systems that have common features. Those systems are systematically developed from a common set of core assets. Two patterns outstand among the various techniques proposed by several authors for developing software product lines: the development process is generally sequential and the primary design concerns deal with technical issues, such as component allocation and system partitioning (into subsystems). The importance of a domain model is often neglected. Although such practices have been reported as successful, this work proposes another paradigm, which can yield more satisfactory results. This paradigm is based on agile methods and a set of design principles known as domain-driven design. This hypothesis is supported by comparing different modeling patterns and by developing a case study

Submitted by Franciele Moreira (francielemoreyra@gmail.com) on 2017-09-11T13:42:06Z No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Approved for entry into archive by Luciana Ferreira (lucgeral@gmail.com) on 2017-09-15T15:43:54Z (GMT) No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Made available in DSpace on 2017-09-15T15:43:54Z (GMT). No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) Previous issue date: 2017-08-11 / The Information Technology (I.T) market is growing. In the age of information, world economies have been investing more and more in the services market. Within this competitive scenario, software testing is an important component for raising the quality of software developed in Brazil and in the global competitiveness cenario. However, Small and medium-sized enterprises (SMEs) have limited resources for investments in software testing maturity processes, tools and models in their business. Faced with this, this work has as main proposal to produce an apparatus to improve the process of software testing for SMEs. Objective: As the main objectives, this study proposed a more update version of the FreeTest 1.0 process, as well as practical instructions on how to implement the activities suggested in the process, all this formatted in a new process and a wizard respectively. Methodology: In order to fulfill the objectives of this work, the FreeTest 2.0 process was created as an improvement of the FreeTest Method process, focused mainly on Agile techniques, DevOps and aligned with the SMEs ecosystem. And the FreeTest Wizard, which consists of a deployment guide that supports the implementation of the process in a didactic, dynamic and flexible way. Another contribution of this work was the creation of support tools to disseminate this knowledge and content management, in this case the creation of a web platform, distributed free of charge and in the format "as a Service". Finally, the results and conclusions can be seen in the final chapter of this work. / O mercado de Tecnologia da Informação (T.I.) é crescente. Na era da informação, as economias mundiais investem cada vez mais no mercado de Serviços. Dentro deste cenário competitivo, o teste de software é um importante componente para elevação da qualidade do software desenvolvido no Brasil e sua competitividade mundial. Contudo, as Micro e Pequenas Empresas (MPEs) possuem recursos limitados para investimentos em processos, ferramentas e modelos de maturidade de teste de software em seus negócios. Diante disto, este trabalho tem como proposta principal produzir um aparato para melhoria do processo de teste de software para MPEs. Objetivo: Como objetivos principais, este estudo propôs uma versão mais atualizada do processo FreeTest 1.0, bem como instruções práticas de como implantar as atividades sugeridas no processo, tudo isso formatado em um novo processo e um guia de implantação, respectivamente. Metodologia: Com o propósito de cumprir os objetivos almejados neste trabalho foram criados: 1) o processo FreeTest 2.0 como uma melhoria do processo do FreeTest 1.0, focado principalmente em técnicas Ágeis, DevOps e alinhado ao ecossistema das MPEs; e 2) o FreeTest Wizard, que consiste em um guia de implantação que apoia a implantação do processo de forma didática, dinâmica e flexível. Outra contribuição deste trabalho foi a criação de ferramentas de apoio para disseminação deste conhecimento e gestão dos conteúdos, neste caso, a criação de uma plataforma web distribuída de forma gratuita e no formato "as a Service". Por fim, os resultados e conclusões serão vistos no capítulo final deste trabalho.

This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions. A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software. In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed. / Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.

Métodos ágeis são técnicas adequadas para o desenvolvimento de software sujeito a mudanças constantes. Essas mudanças não devem afetar o cronograma, orçamento do projeto e devem assegurar o atendimento às necessidades do cliente. Diversos valores, princípios e boas práticas de desenvolvimento e de condução de projeto são aplicados em projetos ágeis com esse objetivo. Algumas dessas práticas são relacionadas a atividade de teste de software. Este trabalho teve como objetivo caracterizar a atividade de teste de software aplicada dentro de métodos de desenvolvimento ágil, buscando eliminar aspectos de teste não produtivos, identificando boas práticas e, principalmente, criando formas de acompanhar e melhorar continuamente a condução da atividade de teste. A partir da caracterização da atividade foi proposta a adoção de um conjunto de métricas para facilitar o seu acompanhamento e melhoria constante da mesma. Algumas dessas métricas de acompanhamento de testes foram implementadas na ferramenta Agile Testing Metrics Management (ATMM). O objetivo principal da ferramenta é gerenciar as iterações de desenvolvimento do projeto ágil e, também, exibir a evolução das métricas relacionadas ao código que está sendo testado e aos casos de teste desenvolvidos utilizando a ferramenta JUnit. Para validar a ferramenta e as métricas foram conduzidos estudos de casos com dois projetos de software de domínios diferentes que utilizaram métodos ágeis e testes de unidade / Agile methods are appropriate techniques for software development subject to constant changes. These changes should not affect the project schedule, budget and must ensure meeting the clients needs. Several values, principles and practices of project development and driving are applied in agile projects with this goal. Some of these practices are related to software testing activity. This study aimed at characterizing the software testing activity applied to agile development methods, trying to eliminate unproductive testing aspects, identifying good practices and especially creating ways of tracking and continuously improve the test activity. From this activity characterization, it was proposed an adoption of metrics set to facilitate the monitoring and constant improvement of the activity. Some of these testing tracking metrics were implemented in the Agile Testing Metrics Management Tool (ATMM). The main goal of this tool is to manage the iterations of agile project development and, also show the metrics evolutions regarding the code that have been tested and the test cases developed using JUnit. The tool and metrics were validated by case studies that were conducted with two software projects of different domains which used agile methods and unit testing

The content of this diploma thesis is an analysis of the current state of management of international projects in a multinational IT company, which should lead to the selection and implementation of an appropriate project management tool supporting planning and project management using agile methods Scrum and Kanban. The focus of this thesis is the actual implementation of the selected tool and its setting.

Purpose of this thesis is to design system to support agile software development in virtual teams. Agile development methodology and some available tools to support it are listed here in this thesis, in order to use the system in a wide range of devices, theoretical analysis of multi-platform application development options are listed. The following sections describe the design and implementation witch using web technologies. At the end the system is demonstrated on model situation and extension its designed.