A área de pesquisa de Arquitetura de Software tem recebido cada vez mais atenção dentro da Engenharia de Software, visto que arquiteturas de software têm tido papel determinante para a qualidade de sistemas de software. Nesse contexto, arquiteturas de referência surgiram como um tipo especial de arquitetura que provê diretrizes para construção de arquiteturas de software de uma dada classe de sistemas, promovendo também o reúso do conhecimento sobre um dado domínio de aplicação. Considerando sua relevância, arquiteturas de referência têm sido propostas e utilizadas com sucesso em diferentes domínios. Em outra perspectiva, a indústria de software tem cada vez mais adotado métodos ágeis de desenvolvimento de software, visando, entre outros aspectos, diminuir o tempo de entrega de seus produtos. De um modo geral, esses métodos têm como característica comum ciclos curtos de produção e entrega no desenvolvimento de software. Consequentemente, minimizam a quantidade de documentação gerada no processo. Dessa forma, parece ser conflitante a adoção de arquiteturas de referência no contexto de métodos ágeis. No entanto, iniciativas já podem ser encontradas, apesar de haver uma carência de trabalhos que propõem a utilização de ambas de forma integrada. Dessa forma, o principal objetivo desse projeto de mestrado foi o estabelecimento um processo ágil de desenvolvimento de software, denominado AGIRA, que explora as vantagens do uso de arquiteturas de referência. A avaliação de tal processo foi realizada em duas frentes. A primeira foi por meio da condução de um action case com alunos de uma disciplina de Arquitetura de Software da Universidade de Bolzano. A segunda frente foi conduzida através de um questionário com especialistas da indústria. Resultados alcançados mostram que o AGIRA tem potencial para ser utilizado pela indústria e que, dessa forma, arquiteturas de referência podem ser aplicadas juntamente com métodos ágeis / Software architectures and reference architectures have been playing a significant role in determining the success of software systems. In particular, reference architectures have emerged, achieving well-recognized understanding of specific domains, promoting reuse of design expertise and facilitating the development of systems. In another perspective, agile methods have been widely adopted as a promising iterative, incremental and collaborative software development process, including by the software industry. However, it is observed that reference architectures have not been widely used together with agile methods. Therefore, the main advantage of reference architectures, i.e., the reuse of knowledge contained in such architectures, has not been combined with the agility promoted by these methods. In this sense, the main objective of this master´s project was to establish an agile software development process, named AGIRA, that aims at exploring the advantages of the use of reference architectures. The evaluation of the process was done in two parts. The first one was through the conduction of an action case with students of a Software Architecture course in the University of Bolzano. The second part of the evaluation was done in the industry context, through the conduction of a survey with experts in software architecture and agile methods. Results point out that AGIRA has potential to be used by the industry and, consequently, reference architectures can be used in the context of agile methods

A atividade de teste é essencial para a garantia de qualidade do software e deveria ser empregada durante todo o processo de desenvolvimento. Entretanto, o esforço para a sua aplicação e o alto custo envolvido, comprometem sua utilização de maneira adequada. Durante o processo de desenvolvimento ágil, onde o tempo é um fator crítico, otimizar a atividade de testes sem afetar a qualidade é uma tarefa desafiadora. Apesar do crescente interesse em pesquisas sobre testes no contexto de métodos ágeis, poucas evidências são encontradas sobre avaliação do esforço para elaboração, evolução e manutenção dos testes nesse contexto. Este trabalho propõe uma abordagem para predição de defeitos desenvolvida para o contexto do desenvolvimento ágil e, portanto, considerando as características deste processo de desenvolvimento. Essa abordagem pode ser aplicada quando se considera ou não o desenvolvimento dirigido a testes. A abordagem permite priorizar a execução dos testes com base em uma lista de arquivos que apresentam maior probabilidade de apresentarem defeitos. A abordagem proposta foi avaliada por meio de um estudo de caso conduzido em um ambiente real de desenvolvimento. Como resultado obtido, observou-se que a abordagem melhorou a qualidade do projeto desenvolvido, sem aumentar o esforço durante a atividade de teste de software. / The testing activity is essential to ensure the software quality and should be applied during all steps of the developing process. However the required effort to do this and the high cost involved, compromises its proper usage. During the agile development process, in which time is a critical factor, optimizing the testing activity without affecting quality is a challenge. Despite the growing interest in research based agile method testing, few works are found on the evaluation of the effort to prepare, develop and maintain test cases in this context. This paper proposes an approach for fault prediction in the context of agile development and therefore considering the characteristics of this development process. This approach can be applied both when considering test-driven development or not. It allows prioritizing the execution of tests based on a list containing files most likely to fail. The proposed approach was evaluated by a case study conducted in a real development environment. The results indicate that the approach can improve the quality of the projects without increasing the effort during the testing activity.

Um Data Warehouse (DW) é um banco de dados centralizado, orientado por assunto, integrado, não volátil e histórico, criado com o objetivo de dar apoio ao processo de tomada de decisão e que estrutura os dados em uma arquitetura analítica bastante distinta da arquitetura relacional utilizada nos bancos de dados transacionais. Construir um DW é um projeto de engenharia bastante complexo pois envolve muitas tecnologias e muitas pessoas, de diferentes equipes, em um grande esforço conjunto para construir esta base central de informações corporativas. O processo tradicional de construção de um DW não utiliza conceitos ágeis e, pelo escopo de desenvolvimento ser grande, pode levar muito tempo até que funcionalidades sejam entregues aos clientes. Os métodos ágeis de engenharia de software são muito usados como uma alternativa aos métodos tradicionais de desenvolvimento e têm diferenciais que trazem muito valor a projetos grandes pois, além de buscar desenvolver versões funcionais em prazos curtos, defendem que todos os sistemas têm a constante necessidade de se adaptar a mudanças. Neste trabalho são aplicadas práticas ágeis no processo tradicional de engenharia de DW para que o desenvolvimento seja realizado em ciclos iterativos curtos, tornando possível o desenvolvimento rápido e evolutivo de um DW com entregas constantes de novas funcionalidades. A contínua evolução deste complexo ambiente analítico é apoiada por conceitos de banco de dados evolutivos e também por fundamentos de métodos ágeis. / A data warehouse (DW) is a central database, subject-oriented, integrated, nonvolatile, and time-variant collection of data in support of management\'s decision making process and that summarize the data in an analytic architecture quite different from the relational one, used in transactional databases. Building a DW is a complex engineering project because it involves many technologies and many people, from different teams, in a huge corporative effort to build a central database with corporative data. The traditional engineering process to build a DW does not use agile concepts and, as its scope is quite big, it might takes a long time until the customer can use its features. Agile methods of software engineering are commonly used as an alternative to the traditional methods and they have some differentials that lead a lot of value to big projects, as the continuous attempt to develop short releases in short periods of time, or the belief that every system needs to be continuously adapted to the changes on its environment. This work applies agile practices in the traditional DW engineering method, so that the development can be done in short iterative cycles, making possible a fast and evolutive DW project, with frequent delivering of new functionalities. The continuous evolution of this complex analytical environment is supported by evolutive database concepts and also for agile methods foundations.

A modelagem evolutiva de bancos de dados é necessária devido às frequentes mudanças de requisitos das aplicações. O desafio é ainda maior quando o banco de dados tem de atender simultaneamente a várias aplicações. A solução proposta por Scott Ambler para evolução utiliza refatorações e define um período de transição, durante o qual tanto o esquema antigo quanto o novo coexistem e os dados são replicados por meio de um processo síncrono que apresenta várias dificuldades, como a interferência no funcionamento normal das aplicações. Para minimizar essas dificuldades, esta tese propõe um processo assíncrono para manter atualizados esses esquemas e apresenta um protótipo de uma ferramenta para auxiliar as evoluções dos bancos de dados. A proposta foi validada por meio de um experimento em laboratório que comparou a solução aqui apresentada com a proposta por Ambler. / Evolutionary database modeling is necessary due to the frequent changes in application requirements. The challenge is greater when the database must support multiple applications simultaneously. The solution for evolution proposed by Scott Ambler is refactoring with a transition period, during which both the old and the new database schemas coexist and data is replicated via a synchronous process, what brings several difficulties, such as interference with the normal operation of applications. To minimize these difficulties, this thesis proposes an asynchronous process to keep these schemas updated and presents a prototype tool to evolve databases. The proposal was validated by a laboratory experiment in which the solution presented here was compared with the one proposed by Ambler.

El presente trabajo tiene como objetivo principal proponer un modelo para desarrollo de habilidades blandas y valores de métodos ágiles, para una organización que desee adoptar los métodos ágiles para el desarrollo de proyectos aplicando los Estándares Globales del PMI. Muchas organizaciones pretenden implementar métodos ágiles, como por ejemplo Scrum, presumiendo que todos los miembros de la organización están dispuestos y listos para comprender lo que implica trabajar con métodos ágiles. Esta presunción suele ser un error en la gran mayoría de casos, lo que lleva al fracaso al momento de implementar métodos ágiles como solución a una baja productividad o como un intento de mejora de la organización. Este trabajo de basa, principalmente, en la Guía Práctica de Ágil (Project Management Institute, 2017), la Guía del PMBOK® 6ta Edición (Project Management Institute, 2017) y la Improv Encyclopedia (improvencyclopedia.org, 2018), de donde se han tomado conceptos, técnicas y herramientas para poder proponer un modelo que sea compatible con cualquier organización que los adopte. Cabe destacar que este modelo se ha ido mejorando durante varias ejecuciones prácticas en organizaciones que, por motivo de confidencialidad, tendrán nombres cambiados pero que nos ayudarán a ilustrar mejor los objetivos que se obtienen con la aplicación de este modelo. Todo este modelo se ha trabajado bajo el nombre comercial de XENDA FREERUN, a cuál en adelante denominaremos FREERUN. Este modelo cubre el análisis y diagnóstico por medio de entrevistas realizadas a los miembros de una organización, la programación de un plan de trabajo y, finalmente, la ejecución de este y la evaluación final. / The main objective of this paper is to propose a model for the development of soft skills and values of agile methods for an organization wishing to adopt agile methods for the development of projects applying the Global Standards of the PMI. Many organizations intend to implement agile methods, such as Scrum, if all members of the organization are willing and ready to understand what it means to work with agile methods. This assumption is often a mistake in most cases, leading to failure to implement agile methods as a solution to low productivity or as an attempt to improve the organization. This work is mainly based on the Agile Practice Guide (Project Management Institute, 2017) the PMBOK® 6th Edition Guide (Project Management Institute, 2017) and the Improv Encyclopedia (Improv Encyclopedia, 2018), from which concepts, techniques and tools have been taken to propose a model that is compatible with any organization that adopts them. It should be noted that this model has been improved during several practical executions in organizations that, for reasons of confidentiality, will have changed names but that will help us to better illustrate the objectives obtained with the application of this model. All this model has been worked under the commercial name of XENDA FREERUN, which in future we will call FREERUN. This model covers the analysis and diagnosis by means of interviews made to the members of an organization, the programming of a working plan and, finally, the execution of this and the final evaluation. / Trabajo de investigación

As the product-release cycle in the tech industry speeds up, there is more pressure on manufacturers to bring new products to market faster than ever. This puts a great deal of pressure on the suppliers of capital equipment used to manufacture these tech products. The supply chain agility of these suppliers is increasingly important. The purpose of this study is three-fold (1) to develop a methodology that can be used by any firm for measuring and ranking the agility of suppliers and finding the root causes of supplier agility, (2) to develop the first-ever fully quantitative measure of supply chain agility, and (3) to test if the supply chain management practices that are associated with agility in the academic literature are truly correlated with supply chain agility. Using the outlined methodology in this paper, the data suggest that the customer's current system and processes adequately met the need for short-notice, expedited build times. However, many processes and communications between the suppliers and customer have a lot of room for improvement that may positively impact the supply chain agility of suppliers. Since most every firm captures this same data, such as PO create dates and supplier ship dates, any firm can and should replicate this analysis to discover their suppliers' unique drivers of supply chain agility. Each supplier's historical agility was measured and ranked using historical order performance data. This agility score is the first of its kind to measure agility without the use of qualitative factors or self-reported measures of agility. Only three of the supply chain survey questions developed from or borrowed from the academic literature were correlated with supply chain agility in this study. Survey responses regarding the frequency of communication and information sharing are two examples of variables that were not associated with supplier supply chain agility. The only survey question response that was found to be positively correlated with supply chain agility involves the agile practice of delayed product differentiation. Contrary to the literature, two questions involving supplier-customer communication and the linking of order management system were found to be negatively correlated with supply chain agility. In regards to the non-survey, historical data, the independent variables that were correlated with agility highlighted the need for improved systems and processes between the suppliers and customer. Two examples of processes and systems that need improvement are expedited build time requests and PO swaps.

En el presente trabajo de investigación se hace un estudio de la problemática de una empresa del rubro químico, la cual cuenta con un proceso básico y empírico de mantenimiento, en el que no se aplica planificación . Este proceso es muy importante ya que es un proceso de apoyo al proceso central. Debido a ello se propone la implementación de un sistema de gestión de mantenim iento, utilizando la filosofía del TPM (mantenimiento productivo total). En el primer capítulo se realiza un marco teórico, en el cual se desarrollan conceptos concisos de sistemas de gestión de mantenimiento, e strategias en la cual se desarrollan los conceptos de los tipos de mantenimientos, ciclos de vida de los equipos y fallas. Asimismo, indica que se hace énfasis en conceptos desarrollos e implementación del TPM, basados en libros, publicac iones de revisitas, papers, etc. En el segundo capítulo se describe el estado actual de la empresa en la cual se desarrolla la investigación, observando la misión, visión y valores de la misma. Asimismo, de acuerdo a herramientas de ingeniería, cómo histogramas, diagramas causa – efecto, Pareto se pueden encontrar las posi bles causas del problema final. En el capítulo 3 se desarrolla la metodología de solución al problema encontrado en el capítulo previo, definiendo el panorama de la tesis según la metodología a trabajar, el desarrollo de las actividades, teniendo presente los recursos y definir como optimizar los mismos utilizando aspectos de tecnología e innovación, con el fin de ser más productivos en el proyecto en curso. Asimismo, se revisarán los resultados de los análisis, actividades, recursos propuestos, para validar el desarrollo de la tesis se deben simular los resultados haciendo las comparaciones del antes y el después de la mejora, utilizando un software simulador; lo cual se deberá reflejar la mejora propuesta en costos, es decir impacto económico. Por último, se realizarán las recomendaciones y conclusiones del estudio realizado, de acuerdo los objetivos planteados. / In this thesis a study is made of the problem of a company in the chemical field, in which they only have an empirical basic maintenance area, in which optimal maintenance controls are not carried out, which is reflected in costs and low productivity. Due to this, the implementation of a maintenance management system is proposed, using the philosophy of TPM (total productive maintenance). In the first chapter a theoretical framework is made, in which concise concepts of maintenance management systems are developed, strategies in which the concepts of maintenance types, equipment life cycles and failures are developed. It also indicates that emphasis is placed on concepts of development and implementation of the TPM, based on books, magazine publications, papers, etc. The second chapter describes the current state of the company in which the research is carried out, observing its mission, vision and values. Also, according to engineering tools, how histograms, cause - effect diagrams, Pareto can find the possible causes of the final problem. In chapter 3 the methodology for solving the problem found in the previous chapter is developed, defining the thesis panorama according to the methodology to be worked, the development of the activities, taking into account the resources and defining how to optimize them using aspects of technology and innovation, in order to be more productive in the ongoing project. Likewise, the results of the analysis, activities, proposed resources will be reviewed, to validate the development of the thesis, the results must be simulated by making comparisons of the before and after the improvement, using a simulator software; This should reflect the proposed improvement in costs, that is, economic impact. Finally, the recommendations and conclusions of the study will be carried out, according to the objectives set. / Trabajo de Suficiencia Profesional

The diploma thesis deals with the proposal of agile project management methodology for the company engaged in the development of custom-made applications. This thesis will be based on an analysis of the current state, which describes the current state of approach to project management. The subject of the thesis is to improve processes and streamline project management using agile methods.

The master thesis focuses on more efficient application of Scrum methodology in a development team within specific company. The thesis takes an advantage from the SW-CMM philosophy applied in agile environment in order to achieve better effectivity. Theorethical base is utilized for a comparison with current state in the company described in analytical part. Proposals for a solution of current situation are based on drawback detection. Proposals are subject for risk analysis followed by precaution. Costs of proposals implementation with included precautions are evaluated in economic evaluation part. This part also contains benefits of proposals.

This diploma thesis deals with the issue of project management tools in the management of IT projects. The basic theoretical concepts are described in the first part of the thesis. The analytical part is devoted to the analysis of the current situation in the company. The proposal for changes in the project focusing on the development of a new functionality of the information system for the customer is based on this analysis and its efficiency is improved using the Scrum agile methodology.