Ao longo das últimas décadas, um crescente número de autores tem enfatizado a centralidade e a importância estratégica do conhecimento dentro das organizações. Apesar dos esforços significativos de pesquisadores de vários domínios, a tarefa de compreender o conhecimento organizacional permanece controversa. Duas escolas de pensamento contrastantes desempenham funções importantes na formação do discurso dominante, tanto na esfera acadêmica quanto no mundo gerencial: a visão tecno-racional da gestão do conhecimento (knowledge management) e a perspectiva social construtivista do conhecimento na prática (knowing-in-practice). O conceito de knowing-in-practice está situado dentro de dois grandes eixos teóricos: aprendizagem organizacional e teorias baseadas em prática. Meu objetivo nesse estudo foi identificar e compreender o knowing-in-practice dos indivíduos organizacionais pesquisados a partir das práticas de trabalho. Para isso, além de identificar e descrever as práticas de trabalho do grupo, também foi preciso descrever e analisar as relações estabelecidas entre os integrantes da equipe. Para viabilizar a pesquisa, desenvolvi um estudo etnográfico, realizado entre os meses de setembro de 2011 e dezembro de 2012, em uma equipe de desenvolvedores de software, situada em Porto Alegre (RS). De modo complementar, esclareço algumas noções importantes da área de desenvolvimento de software, principalmente em relação às metodologias ágeis. Após descrever o espaço físico e o cotidiano dos profissionais, o movimento de entrada e saída de integrantes da equipe, a comunicação e as práticas dos desenvolvedores, identifico e analiso o knowing-in-practice da equipe, esse situado nos artefatos, na dinâmica das interações, na linguagem e no contexto físico. O knowing-in-practice está diretamente relacionado ao ato de fazer uma ação ou atividade, ele é produzido localmente de forma emergente, situada e ativa. O knowing se caracteriza como um fluxo constante de saberes e fazeres, por isso seu caráter dinâmico, temporário e presente através das práticas. / Over the past decades, a growing number of authors have emphasized the centrality and strategic importance of knowledge within organizations. Despite the significant efforts of researchers from various fields, the task of understanding organizational knowledge remains controversial. Two contrasting schools of thought play important roles in the formation of the dominant discourse, both in the academic and in the managerial world: the techno-rational view of knowledge management and the social constructivist perspective of knowledge in practice (knowing-in-practice.) The concept of knowing-in-practice is located within two major theoretical axes: organizational learning and practice-based theories. My goal in this study was to identify and understand the knowing-in-practice of the organizational individuals surveyed from their working practices. For this, besides to identify and describe the working practices of the group, was also necessary to describe and analyze the relationships established between team members. In order to enable the research, I conducted an ethnographic study, between the months of September 2011 and December 2012, in a team of software developers located in Porto Alegre (RS). In a complementary way, I clarify some important notions in the area of software development, particularly in relation to the agile methodologies. After describing the physical space and the everyday work of the professionals, the movement of incoming and outgoing team members, the communication and the working practices of the developers, I identify and analyze the knowing-in-practice of the team, located in the artifacts, in the dynamics of interactions, in the language and in the physical context. The knowing-in-practice is directly related to the act of making an action or activity; it is locally produced in an emergent, situated and active form. The knowing is characterized as a steady flow of know-hows, so its dynamic, temporary and through the practices nature.

A adoção de métodos ágeis é uma forma eficaz de reduzir o ciclo de entrega no desenvolvimento de software, fornecendo software de qualidade em curto espaço de tempo. Porém, a adoção desta nova abordagem de desenvolvimento de software torna necessário repensar a forma de medir e controlar os projetos. Os métodos ágeis não tratam claramente sobre os assuntos utilização de métricas e adoção de um processo de medição para projetos de softwares desta natureza, faltando estudos que tragam recomendações em como estabelecer métricas para projetos ágeis e como adotar um processo de medição compatível com esta abordagem. Visando contribuir neste sentido esta tese tem como objetivo definir um conjunto de métricas adequadas às necessidades de monitoramento e propor um processo de medição, compatível com a abordagem ágil de desenvolvimento de software. Como método de pesquisa foi realizado um trabalho exploratório através de revisão de literatura e de pesquisa de campo com entrevista em profundidade em empresas de desenvolvimento de software experientes em métodos ágeis. O primeiro resultado do trabalho é a apresentação de um conjunto de métricas consolidados para auxiliar na gestão de projetos ágeis de desenvolvimento de software nas fases de projeto/releases, iteração e diário. As métricas são especificadas detalhadamente contendo as informações necessárias para seu entendimento e aplicação. Posteriormente é proposto um processo de medição compatível com a abordagem ágil de desenvolvimento de software, visando apoiar as empresas que adotam métodos ágeis na definição de métricas adequadas para suas necessidades de medição e no monitoramento. O processo contempla as fases de planejamento de medição, monitoramento da iteração, ações da iteração, monitoramento do projeto/releases, ações sobre o projeto/releases e avaliação final, sendo que em cada fase do processo são apresentadas recomendações para a sua implantação. O processo está estruturado num ciclo de gestão baseado em etapas de planejar, executar, verificar, atuar, refletir e melhorar, respeitando as características dos projetos ágeis de desenvolvimento de software, e na proposição de um quadro visual de monitoramento que permita a gestão do processo de medição de forma visual. Além dos resultados apresentados foram deixadas hipoteses e recomendações para trabalhos futuros. / The adoption of agile methods is effective way to reduce the delivery cycle on software development, providing quality software in a short time. However, the adoption of this new approach to software development is necessary rethink how to measure and control projects. Agile methods not explain about adoption metrics and measurement process for software projects of this approach, lacking studies providing recommendations on how to establish metrics for agile projects and how to adopt a process measurement compatible with this approach. Contributing this thesis goal produce a set of metrics adequate monitoring needs and propose a measurement processcompatible with agile software development. Method of research was exploratory through literature review and field research with depth interviews in experienced software development companies in agile methods. The first result of this work is the presentation of a consolidated metrics set to help the management of agile development at the phases of project/releases, iteration and daily. The metrics are specified detailed containing the information necessary for their understanding and application. Later we propose a measurement process compatible with agile approach to software development, to support businesses that adopt agile methods in defining adequate metrics for your measurement needs and monitoring. The process include the steps of measurement planning, monitoring of the iteration, the iteration actions, monitoring project/releases, actions on the project/releases and final evaluation, in each stage of the process provides recommendations for implementation. The process is structured in a management cycle based on steps to plan, implement, check, act, reflect and improve, respecting the characteristics of agile software development projects and propose a visual tracking board that allows for the management of the measurement process. In addition to the results were allowed hypotheses and recommendations for future work.

Sistemas de software bem modularizados podem trazer diversos benefícios como reu- sabilidade, compreensão, adaptabilidade, manutenibilidade, entre outros. O conceito de separação de interesses está diretamente ligado à ideia de modularização e consiste na capacidade de manter cada interesse em sua própria unidade modular. Um interesse pode estar relacionado tanto a requisitos funcionais como não-funcionais e em diferentes níveis de abstração. Algumas das técnicas que têm sido utilizadas para modularização de interes- ses são a Programação Orientada a Aspectos (POA) e Refatoração. Entretanto, a maioria das propostas de refatoração que envolvem a POA possui limitações para a modularização de interesses transversais: muitas delas são de granularidade fina; algumas são definidas imprecisamente e possuem sobreposição de intenções. A seleção e composição de tais refatorações para a modularização de interesses é uma tarefa difícil e não-trivial, além de variar em cada contexto específico, o que dificulta o reuso. Algumas das propostas de refatorações são voltadas especialmente para interesses transversais, no entanto possuem um nível de abstração pouco elevado e encontram-se acopladas a mecanismos específicos de linguagens de programação OO e OA. Adicionalmente, a aplicação de refatorações deve ser planejada e acompanhada sistematicamente durante o desenvolvimento e manu- tenção de um software, pois envolve alocação de recursos e avaliação de custo/benefício. O objetivo deste trabalho é apresentar um método de refatoração para modularização de interesses transversais, através de refatorações de granularidade alta, baseado em padrões recorrentes de estruturas transversais (chamados de sintomas). Além disso, como parte do método, propõem-se algoritmos para análise de impacto a fim de apoiar desenvolve- dores no processo decisório de aplicação de refatorações candidatas. Inicialmente, dois estudos bibliográficos foram conduzidos: o primeiro sobre propostas de refatorações que envolvem aspectos e o segundo sobre trabalhos de medição de interesses. Dois estudos de caso foram realizados totalizando 22 interesses de dois sistemas alvos. Este trabalho de avaliação possibilitou uma análise quantitativa e qualitativa dos resultados onde foi possível verificar a aplicabilidade do proposta. / Well-modularized software systems can bring several benefits such as reuse, com- prehension, adaptability, maintainability, among others. The concept of separation of concerns refers to the idea of modularisation, which consists on the ability to keep every concern in its own modular unit. A concern can refer to functional and non-functional requirements and can also be in different abstraction levels. Some of the techniques which have been applied for crosscutting concerns modularization are Aspect-Oriented Programming (AOP) and Refactoring. However, most of the aspect-oriented refactor- ings have limitations regarding the modularisation of crosscutting concerns. A number of them presents fine-grained transformations. While some of them are well-documented catalogues, a number of them are defined imprecisely, addressing the same situation and having overlapping intentions. They do not allow the designer to holistically reason about the elements involved in a crosscutting concern. It becomes difficult and non-trivial to choose a set of fine-grained refactorings and organize them in a feasible order to achieve the concern modularisation in a specific context. Some of the refactoring techniques are particularly focused on crosscutting concerns, however they are not placed in a suf- ficient abstraction level. Moreover they are coupled to specific OO and AO language mechanisms. Additionally, the application of refactorings should be planned and realized systematically during software development and maintenance since it involves resource allocation and tradeoff analysis. The goal of this work is to present a refactoring method for crosscutting concerns modularisation, through coarse-grained refactorings based on recurring patterns of crosscutting shapes (called symptoms). Also, as part of the method, algorithms for change-impact analysis are proposed in order to support developers during the decision process of the application of refactoring candidates. Initially, two biblio- graphic studies were made: the first one about refactoring approaches which involve as- pects, and the second one about concern measurement techniques. Two case studies were carried out totalizing 22 concerns of two target systems. This evaluation work allowed a quantitative and qualitative analysis of the results. Thus it was possible to verify the applicability of our approach.

In order for a software development team to be successful, cost effective and perform effectively the team needs to coordinate and communicate sufficiently in order to compensate for the obstacles that a distributed team face. The focus of this report is to observe a distributed team as they try to overcome the obstacles that a distributed team face when it comes to coordination and collaboration. The team is being observed as they try to overcome those obstacles while working on a project for a client in another country. Methods, processes and tools are introduced in order for the team to become a self-organizing distributed team that works agile and effective. With the team being observed throughout the course of the project and the literature review on the subject, this report will analyze the team and the methods used in order to come to a conclusion on what enables a distributed team to become a self-organizing team that works agile and effective in a international market. There are obstacles that a distributed self-organizing team face. With efficient communication methods and tools for coordination the team can become a strong self-organizing team that works agile and productive.

Context. With the popularity of Agile methods, many studies about Agile software development has been done by researchers. Among the phases in Agile software projects, planning is critical because it provides an overview of the project and a guiding of future work. In addition, success factors are also mandatory to the success of Agile software development. The current literature focus on the success factors during the whole lifecycle rather than planning phase, and they don’t make an in-depth analysis on the factors. In this thesis, we perform an empirical study to deeply study the critical success factors at agile planning phase. Objectives. The main aim of our research is to identify the critical success factors at Agile planning phase and challenges associated with each factor. We list four objectives to support our main aim. First is to investigate the factors that are mandatory to the success of Agile software development at planning phase. Second is to investigate the challenges associated with each factor. Third is to find out the ways to address these challenges. The last is to identify the consequence of not ensuring these factors. Methods. We employed two research methods: systematic mapping and survey. Systematic mapping is used to identify the critical success factors of entire lifecycle in current literature. To find critical success factors at agile planning phase and make in-depth analysis, we conducted a survey based on an online questionnaire. The online questionnaire was consisted of open-ended questions and was sent to respondents who have experience on Agile development. Results. Through systematic mapping, we identified 13 papers and 47 critical success factors for Agile software development. We also made a frequency analysis for these factors and they will be the effective evidence to support the results of survey. Through the survey, we identified 13 critical success factors at agile planning and made an in-depth analysis for these 13 factors. These 13 factors are divided into two categories: people factor (individual-level, team-level) and process factor. Through the contrastive analysis of mapping results and survey results, we found that 7 factors of survey results are same or similar with some factors shown in mapping. The other 6 factors of survey are first shown. Conclusions. The factors proposed in this thesis are proved that they are important to the success of the project at planning phase. Failure to consider these critical success factors may lead to inefficient planning and even result in the failure ofthe whole project. The challenges and corresponding solutions can help organizations well manage these critical success factors. In conclusion, these detailed descriptions of critical success factors can be used as a guideline to help people increase the chance of successfully developing software with high quality and low cost in practice.

The objective of this study is to investigate how banks are working with information security by performing a comparative study between banks in Japan and Sweden. Special focus is given to the impact of organizational culture when developing IT-systems. The material analyzed is collected through semi-structured interviews with banks in Japan and Sweden, and additional interviews with professionals within the field of information security. The findings show that banks in both Japan and Sweden take information security seriously, both from a technical and an organizational culture point of view. They have implemented technological countermeasures and try to impose a safety culture by educating their employees. Organizational culture aspects are demonstrated to have a great impact on the development of IT systems from an information security perspective. The development process of IT systems are different between the countries, the Swedish banks have started to use the agile development method, while the Japanese banks still use the more traditional waterfall method. The result also implies that in Sweden there is an open climate and a greater trust between the banks which have lead to collaboration between the major banks and the development of innovative products. In Japan it is more difficult for the banks to create trustworthy relationships and share their information security knowledge to the same extent. The findings strengthen the notion in related research that cultural aspects have influence on how information security is managed.

Context. User Experience has become key to product development in recent years, as manyorganizations have realized its role in maintaining high user acceptance ratings. User ExperienceDevelopment and Agile Software Development are two highly iterative processes and user-centricprocesses. While both methods stack up well theoretically, there are many challenges encountered whenthey are integrated together in real-world development scenarios. Similar to Agile development, UserExperience Development, has many phases: performing user research, gathering UCD (User-CenteredDesign) requirements, iterating design activities, and performing usability evaluation through user tests.Executing both processes in parallel and mapping their corresponding phases is a major issue andapplying these principles in development environment is even more challenging. This integration bearseven more significance in the field of healthcare technology, where user-centered requirements ofpatients and medical practitioners need to handled systematically, as there are a wide range ofspecifications that cater to unique individuals. Hence, a case study was conducted in two majororganizations involved in the development of Interactive Healthcare Technology (IHT) applications. Objectives. Through a case study, the author attempts to investigate the factors that influence theintegration between UX development and Agile methodologies. These factors include the contemporarytools, processes and methods (TPMs) that are being used integration and the challenges that persistwhen it is applied in industry. The study aims to analyze the Agile-UX development approaches of twodistinct organizations, involved in the same domain, to get an understanding of the mentioned factors. Methods. The multiple case study was conducted through interviews, surveys and direct observation.The qualitative data analysis of the surveys was done through thematic analysis. Quantitative dataanalysis was performed on the data gathered from the surveys. A literature review was conducted priorto the case study to gain knowledge on this issue, which also partially answers the research questions.The case study design was kept consistent across both organizations. Results. Through the results of the case study and a literature review, current UX development practicesin the industry have been identified. The challenges encountered at both case organizations have been studied. These results are further validated and contrasted with the results of the literature review.Following, a retrospection of the methods employed at the case environments, a set of recommendationsfor better integration was generated. A detailed comparative analysis of Agile-UX integration at twoorganizations has been documented. At the end a generic framework has been proposed based on theanalysis of results acquired. Conclusions. Numerous conclusions were drawn from the results and data analysis. Several challengeswere identified through the study, in addition to those suggested by relevant literature. Some of thesewere uniquely prevalent in the field of IHT development. It was found that dynamically changing usercenteredrequirements and late integration of usability and UX development with Agile practices werethe most profound challenges. Adoption of UCD techniques such as Design Studio played a positiverole in easing integration. Usability evaluation and user research are also major factors in the integrationprocess. Lack of time to iterate design and issues in scheduling and performing usability testing had abig impact. Involving users in the design and development process from an early stage is essential toensure high usability and good user experience of the product. The framework designed to counter thesechallenges, takes into account, all these aspects to provide a meticulous Agile-UX integrationframework. Some key conclusion drawn from this framework, are that the application of the “One SprintAhead” approach diminishes many challenges, while performing usability testing in parallel withsystem testing can support integration.

Context. A clear software process definition is important because it can help developers to share a common understanding and improve the development effectiveness. However, if the misconceptions or misunderstandings are introduced to the team during the process definition, it will bring numerous uncertain problems to the projects and reduce the productivity. Scrum is one of the most popular Agile development processes. It has been frequently used in software development. But the misunderstanding of usage of the Scrum method always leads to situations where teams cannot achieve the hyper-productivity even failure. Therefore, introducing a reasonable graphical language for describing the Scrum process may help learners to gain a correct and common understanding of the Scrum method. Objectives. In this study, we introduce a graphical Domain Specific Language for modeling the Scrum process and specific Scrum projects. Further, we evaluated the proposed language to figure out if and how this language can help developers learn Scrum method and understand the specific Scrum projects. For the first, we decide to extract the essential elements and their relative relationships of the Scrum process, and based on that, we define and specify the graphical language. After that, we evaluate the proposed graphical language to validate whether this language can be considered as useful to help developers to learn Scrum method and understand the specific Scrum projects. Methods. In order to define the graphical language, we studied and reviewed the literature to extract the essential elements and their relationships for describing the Scrum process. Based on that, we defined and specified the graphical DSL. With the aim of evaluating the proposed graphical language, we performed the experiment and survey method. This experiment was conducted in an educational environment. The subjects were selected from the undergraduate and master students. At the same time, we carried out a survey to capture the developers‘ opinions and suggestions towards the proposed language in order to validate its feasibility. Results. By studying the literature, we listed and specified the essential elements for describing the Scrum process. By executing the experiment, we evaluated the efficiency and effectiveness of learning Scrum in using the proposed language and the natural language. The result indicates that the graphical language is better than the natural language in training Scrum method and understanding specific Scrum projects. The result shows that the proposed language improved the understandability of the Scrum process and specific Scrum projects by more than 30%. We also performed a survey to investigate the potential use of the proposed graphical DSL in industry. The Survey results show that participants think the proposed graphical language can help them to better understand the Scrum method and specific Scrum projects. Moreover, we noticed that the developers who have less Scrum development experience show more interests in this proposed graphical language. Conclusions. To conclude, the obtained results of this study indicate that a graphical DSL can improve the understandability of Scrum method and specific Scrum projects. Especially in managing the specific Scrum project, subjects can easily understand and capture the detailed information of the project described in the proposed language. This study also specified the merits and demerits of using the graphical language and textual language in describing the Scrum process. From the survey, the result indicates that the proposed graphical language is able to help developers to understand Scrum method and specific Scrum projects in industry. Participants of this survey show positive opinion toward the proposed graphical language. However, it is still a rather long way to applying such a graphical language in Scrum projects development because companies have to consider the extra learning effort of the graphical DSL.

Context. Owing to a multitude of factors like rapid changes in technology, market needs, and business competitiveness, software companies these days are facing pressure to deliver software rapidly and on a frequent basis. For frequent and faster delivery, companies should be lean and agile in all phases of the software development life cycle. An approach called DevOps, which is based on agile principles has come into play. DevOps bridges the gap between development and operations teams and facilitates faster product delivery. The DevOps phenomenon has gained a wide popularity in the past few years, and several companies are adopting DevOps to leverage its perceived benefits. However, the organizations may face several challenges while adopting DevOps. There is a need to obtain a clear understanding of how DevOps functions in an organization. Objectives. The main aim of this study is to provide a clear understanding about how DevOps works in an organization to researchers and software practitioners. The objectives of the study are to identify the benefits of implementing DevOps in organizations where agile development is in practice, the challenges faced by organizations during DevOps adoption, to identify the solutions/ mitigation strategies, to overcome the challenges,the DevOps practices, and the problems faced by DevOps teams during continuous integration, deployment and testing. Methods. A mixed methods approach having both qualitative and quantitative research methods is used to accomplish the research objectives.A Systematic Literature Review is conducted to identify the benefits and challenges of DevOps adoption, and the DevOps practices. Interviews are conducted to further validate the SLR findings, and identify the solutions to overcome DevOps adoption challenges, and the DevOps practices. The SLR and interview results are mapped, and a survey questionnaire is designed.The survey is conducted to validate the qualitative data, and to identify the other benefits and challenges of DevOps adoption, solutions to overcome the challenges, DevOps practices, and the problems faced by DevOps teams during continuous integration, deployment and testing. Results. 31 primary studies relevant to the research are identified for conducting the SLR. After analysing the primary studies, an initial list of the benefits and challenges of DevOps adoption, and the DevOps practices is obtained. Based on the SLR findings, a semi-structured interview questionnaire is designed, and interviews are conducted. The interview data is thematically coded, and a list of the benefits, challenges of DevOps adoption and solutions to overcome them, DevOps practices, and problems faced by DevOps teams is obtained. The survey responses are statistically analysed, and a final list of the benefits of adopting DevOps, the adoption challenges and solutions to overcome them, DevOps practices and problems faced by DevOps teams is obtained. Conclusions. Using the mixed methods approach, a final list of the benefits of adopting DevOps, DevOps adoption challenges, solutions to overcome the challenges, practices of DevOps, and the problems faced by DevOps teams during continuous integration, deployment and testing is obtained. The list is clearly elucidated in the document. The final list can aid researchers and software practitioners in obtaining a better understanding regarding the functioning and adoption of DevOps. Also, it has been observed that there is a need for more empirical research in this domain.

Denna kombinerade magisteruppsats i matematik och datalogi handlar om en metod för att hitta ett lokalt minimum för en unimodal funktion inom ett intervall genom användning av ett femtegradspolynom. Femtegradspolynomet skapas med hjälp av interpolation baserad på funktionsvärdena samt första och andra derivatans värden i intervallets ändpunkter. I rapporten härleds matematiskt att metoden konvergerar, följt av ett bevis för att metoden konvergerar med en konvergenshastighet av tre. Slutligen testas metoden mot två referensmetoder för att se användningsbarheten. För detta beskrivs vissa mjukvaruutvecklingsmetoder och några teststrategier. Testen utförs med sex olika funktioner och med tre olika versioner av metoden. Slutsatserna från testen visar att metoden inte är bättre att använda än referensmetoderna även om den har högre konvergenshastighet samt att metoden måste ta hänsyn till när den bara hittar nya approximationer på ena sidan av intervallet. Vi kunde även se från testerna att ingen av metoderna var bra på att ge en korrekt approximation, utan det finns behov av säkrare metoder för detta. Det är därför föreslaget i uppsatsen att man borde försöka att hitta ett annat interpolations-polynom för att förbättra metoden. Man borde även testa mot en metod som har högre konvergenshastighet. För att kunna göra det behöver man titta på andra sätt att representera numeriska värden och det skulle kunna vara intressant för att se om man då skulle få ett annat resultat. / This combined master thesis in Mathematics and in Computer Science deals with a method for finding the local minimum of a unimodal function inside a given interval by using a fifth degree polynomial. This fifth degree polynomial is created from the function value and the first and second derivative values in the end-points of the interval. In this report the presented method is derived mathematically to converge and it is then proven that the method has a convergence rate of three. Last is the method tested against two reference methods to see the usefullness of the method. To do this some software development methods are described in the report and some test strategies are given. The tests are done with six different functions and with three different implementations of the method. The conclusions from the tests are that it is often better to use one of the referencemethods instead of the presented method, even if the presented method has a better convergence rate, and that the method needs to handle when the found approximation always is on one side of the interval. We could also see from the tests that none of the methods were good on finding a correct approximation. Therefore, there exist needs for more secure methods. It is therefore suggested in the report that a search for other interpolating functions ought to be carried out in order to improve the method. Also, it could be interesting to test against another method with even higher convergence rate. To do that, another numerical representation is needed and it would be interesting to see if that changes the outcome