The purpose of this master’s thesis was to research and evaluate how ChatGPT can be used as a tool in software developers’ daily work activities. In order to do this, the thesis was conducted in two phases, the initial exploration phase and the data collection phase. In the initial exploration phase, five senior-level developers were interviewed about their day-to-day work, opinions of generative AI, and the profession of software developers as a whole. From these interviews, a theoretical foundation for software development was formed, categorizing the daily work tasks of a software developer into either coding, communication, or planning. This theoretical foundation was then used as the basis for the tasks and interviews used during the data collection phase. In the data collection phase, seven developers, ranging from students to industry veterans, were asked to complete a set of representative tasks with the help of ChatGPT and afterward participate in an interview. The tasks were based upon the theoretical foundation of software development and aimed to serve as representative tasks that software developers have to do in their day-to-day work. Based on the tasks and interviews it was found that the use of ChatGPT did in fact help make software developers more effective when it came to coding and planning-based tasks, but not without risk since it was shown that junior developers trusted and relied more on the answers given by ChatGPT. Although ChatGPT showed a positive effect, the tooling still needs improvement, since the developers had trouble with the text formatting when completing communication-based tasks, as well as them expressing a desire for the tooling to be more integrated. However, this desire was not unexpected, since all of the developers involved showed interest in working with generative AI tooling for work-related tasks in the future.

The last decade has seen an emergence of various types of cloud services and development frameworks offered by leading companies in the software industry. While each of these services has been used to solve specific tasks, their specifications have changed over time as they have matured. Therefore, integrating these components to solve a whole new task tends to get tricky due to their incompatible and experimental nature. While some technology components might continue to be developed, others might deprecate. In this thesis, using a user-centered design and agile development approach, we have attempted to develop a cloud solution using microservice software architecture by integrating state-of-the-art technology components to solve a totally new task of providing a non-intrusive technology experience during walking meetings. We present our results based on interaction with the research group, user studies as a part of the research study “Movement of the mind”, and expectations of the working prototype within the context of walking meetings. We also present the features of the prototype and our motivation for choosing the tools to develop them. Finally, we discuss the development challenges faced during our attempt and conclude whether it is plausible to integrate various components of bleeding-edge technology to solve complex real-life problems or rather wait for these technologies to mature. / Under det senaste decenniet har marknaden erbjudits en mängd olika typer av molntjänster och utvecklings-ramverk framtagna av ledande företag inom mjukvaruindustrin. Dessa tjänster har ofta använts för att lösa specifika uppgifter. Olika komponenterna som ingår i dessa specifika lösningar har med tiden utvecklats ändrats allteftersom de har mognat. Att integrera dessa komponenter för att lösa en helt ny uppgift tenderar därför att bli svårt på grund av deras instabila, inkompatibla och experimentella karaktär. Medan vissa teknikkomponenter kan fortsätta att utvecklas kan andra avstanna och utgå. Vi har närmat oss detta problemområde genom agil och iterativ utveckling samt användar-centrerad design-metod. En moln-baserad lösning som bland annat integrerat bleeding-edge teknikkomponenter har utvecklats och utvärderats med syfte att ge en icke-påträngande tekniskt support för gå-möten. De resultat som här presenteras och diskuteras baseras på interaktion med forskargruppen inom projektet "Med rörelse i tankarna", användarstudier och användartesteter i fält på olika arbetsplatser där den prototyp som utvecklats sökt motsvara användarnas utryckta förväntningar på tekniskt support för gångmöten. Vi diskuterar också prototypens egenskaper och vår motivation för val av metoder för att utveckla den. Slutligen diskuterar vi de utvecklingsutmaningar vi ställdes inför under vårt försök och om det är rimligt att integrera olika bleeding-edge komponenter för att lösa komplexa verkliga problem eller huruvida man hellre bör vänta på att dessa teknologier nått en stabilare mognadsgrad.

Submitted by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T18:19:05Z No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) / Made available in DSpace on 2017-06-30T18:19:05Z (GMT). No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) Previous issue date: 2016-12-15 / Em fevereiro de 2001, o Manifesto ?gil foi proposto tendo como princ?pio equipes pequenas e co-localizadas. No entanto, ao longo destes 16 anos, a agilidade tamb?m foi posta em pr?tica em outros contextos, como por exemplo: equipes distribu?das e sistemas complexos, utilizando-se o termo "Desenvolvimento ?gil em Larga Escala". N?o h? uma defini??o clara e compreensiva de como a agilidade est? presente neste contexto. Assim, nosso trabalho preenche essa lacuna com o objetivo de caracterizar a agilidade no Desenvolvimento ?gil em Larga Escala. Neste trabalho, realizou-se um estudo organizado em duas fases. Na Fase 1, denominada Base Te?rica, realizamos um estudo do estado-da-arte da ?rea. Na Fase 2, denominado Estudo Emp?rico, n?s realizamos duas investiga??es: um estudo de campo em uma empresa ?gil em larga escala, para identificar o desenvolvimento durante o processo de transforma??o da empresa para esta nova abordagem e, um grupo focal, para identificar como as equipes ?geis em larga escala que v?m utilizando os m?todos ?geis o quanto se percebem em termos de aspectos de maturidade ?gil. Estes resultados contribuem para os pesquisadores e profissionais entenderem melhor como a agilidade e definida e percebida nestes grandes ambientes. O conhecimento e ?til para aqueles que querem entender como o desenvolvimento ?gil se adapta a tais ambientes e para pesquisadores com o objetivo de se aprofundar sobre o tema. / The Agile Manifesto was proposed in February 2001 having in mind small and collocated teams. However, agile has also been put in practice in other settings (e.g. large teams, distributed teams, complex systems) under the term ?Large-Scale Agile Development' (LSAD). There is no clear definition for and understanding of how agility is present in this setting. Thus, our work fills in this gap aiming to characterize agility in LSAD. We conducted a study organized in two phases. In Phase 1, named Theoretical Base, we conducted the state-of-the-art of the area. In Phase 2, named Empirical Study, we conducted two investigations: a field study in a large-scale agile company to identify how agility was developed during the transformation process of the company to this new approach, and a focus group to identify how large-scale agile teams that have been using agile for a certain while perceive themselves in terms of maturity in agile aspects. Findings contribute to researchers and professionals better understand how agility is defined and perceived in large settings. This knowledge is useful for those who want to enter the agile journey in such similar environments and for researchers aiming to further explore the topic.

A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de software / The vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process

Purpose – The purpose of this thesis is to continue the research on Agile teams in large projects and large organizations. Specifically, this thesis seeks to understand what key success factors there are for enabling autonomous Agile teams at large-scale and how they can be prioritized. Method – This thesis is based on a case study at Saab AB, a large Swedish firm within the defense industry. In addition to the case study, interviews with representatives from three separate firms were conducted. The data consist of 13 interviewees with employees at Saab AB and three from the separate firms. A thematic analysis of the data was conducted following a six-step procedure. Results – The results show eight themes with accumulated key success factors from extant literature and empirical findings from this study. The themes are Context, Agile Approach, Other, Dependencies, Planning & Goal Setting, Management Support, Team Stability and Culture, and they are prioritized in that order. Furthermore, a diagnostic questionnaire is established as a tool for managers and teams wanting to enable autonomous Agile teams at large-scale. Theoretical Implications – This thesis contributes to current literature by combining theories of autonomous teams and Agile at large-scale, and by presenting key success factors for this combination to work. It also adds to lacking theory of autonomous team at large organizations. Practical Implications – Autonomy is a central function of Agile teams. Agile methods are becoming increasingly popular at the large-scale. Understanding the key success factors presented in the findings and reviewing the questionnaire, managers can further their enablement of autonomous Agile teams at the large-scale and understand how far they have come. Similarly, teams can understand how they can contribute.

由於現今商業環境時常變動，使得使用者需求在系統開發過程中頻繁改變。傳統系統開發方式無法迅速回應使用者需求變更，強調彈性開發流程的敏捷開發方式逐漸廣為接受。敏捷開發並未探討系統設計議題而系統設計不佳會導致系統品質低落，使用軟體框架可以快速建立良好的分層結構，有助於穩定產品品質並提高軟體再用性。本研究以Scrum為基礎，結合Struts、Spring、Hibernate整合框架，建立一套系統開發方法，包含敏捷開發方式的彈性流程，兼顧系統擴充性及可維護性，研究方法為概念形成法與系統展示法，並以Java Web-Based雛型系統為例，說明相關作業內容。 / Due to the quick variation in the business environment, user requirements change frequently during the system development process. This induces the rising popularity of agile development method which emphasizes the development flexibility during the process. However, agile development method does not address the design issues and poor system design can easily cause poor system quality. Software framework helps to quickly build a good hierarchy structure and thus improve the product quality and software reusability. This study proposes a system development method based on Scrum with the integration of Struts、Spring and Hibernate frameworks. The method is embedded with the development flexibility from the agile method, as well as the system extensibility and maintainability from the software frameworks. The study is conducted with the research method of concept formulation, and would be continued with a Java Web-Based prototype development as an example to illustrate the relevant activities.

This diploma thesis deals with the development of an information system for human resources management. The aim is to describe the process of the development. This thesis is separated into two bigger parts. First, the theoretical part starts with general information about the information society, information systems, an explanation of the ERP information system, the development in general and methodology of development information systems. Second, the practical part describes: how the information system was developed in practice, exactly in the DataCentrum systems & consulting, a.s. company. This thesis describes not only the procedure of programming, but also all related activities such as: the analysis of entry requirements, used development methods, the development team and the tools used during development and testing. As a result, this thesis shows the developed information system and evaluates the whole project with recommendations for improvement.

A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de software / The vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process

Made available in DSpace on 2015-04-22T22:00:48Z (GMT). No. of bitstreams: 1 Eliane Figueiredo Collins.pdf: 2314673 bytes, checksum: 8403bd67cffed913ac9029447401f980 (MD5) Previous issue date: 2013-04-25 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / For some time, the professional software development companies are looking for new technical alternatives in order to optimize their processes, to deliver products to market as soon as possible and to meet customer expectations, increasingly demanding and intolerant of software failures. In this sense, the agile software development is gaining more space and consequently the software testing area which was previously considered a separate phase of development has changed over time to adapt to this new reality. The test automation activity is seen as key of agile development, but many teams still don t know how it should be done, who should take responsibility and run it and the correct procedures for this activity to be successful. Although the literature mentions about the particularities activities and best practices in this scenario, there are few related works and lack of experience reports or case studies that show, in practice, examples of use this from start to finish the automation strategy adopted. This paper aims to contribute to improving the quality of agile processes, and proposes an approach that involves the application of agile manifesto values in the activities of test automation, which can be used regardless of agile methodology adopted. In this study, observations were made on empirical about testing practices in agile projects developed at Nokia Technology Institute (INdT) and an experimental implementation of this approach at the Center for Electronic and Information Technology (CETELI), Federal University of Amazonas (UFAM). Experimental reports are available with different strategies for the automation of software testing and identification of some important issues to deal with difficulties in adapting testers and developers in this new scenario. / Há algum tempo as empresas desenvolvedoras de software profissional vêm buscando novas alternativas técnicas com o objetivo de otimizar seus processos, entregar produtos para o mercado o mais cedo possível e ainda atender as expectativas dos clientes cada vez mais exigentes e intolerantes a falhas de software. Com isso, as metodologias ágeis de desenvolvimento de software estão ganhando mais espaço e consequentemente a área de testes de software que antes era considerada uma fase separada do desenvolvimento vem passando por mudanças para se adaptar a esta nova realidade. A atividade de automação de teste passou a ser vista como peça chave para o desenvolvimento ágil, porém muitas equipes ainda não sabem como ela deve ser feita, quem deve assumir a responsabilidade e execução dela e os procedimentos para que essa atividade seja bem sucedida. Embora a literatura mencione particularidades sobre as atividades realizadas e as melhores práticas nesse cenário, são poucos os trabalhos relacionados e há falta de relatos de estudos de caso ou exemplos de utilização que mostrem, na prática, do início ao fim, a estratégia de automação adotada. Este trabalho tem como objetivo contribuir para a melhoria da qualidade dos processos ágeis, propondo uma abordagem que envolve a aplicação de valores presentes no manifesto ágil nas atividades de automação de teste, que podem ser utilizadas independentemente da metodologia ágil adotada. Nesta pesquisa, foram realizadas observações empíricas sobre as práticas de testes em projetos ágeis desenvolvidos no Instituto Nokia de Tecnologia (INdT) e um experimento de aplicação dessa abordagem no Centro de Tecnologia Eletrônica e da Informação (CETELI), da Universidade Federal do Amazonas (UFAM). São disponibilizados relatos experimentais com diferentes estratégias relativas a automação de teste de software e a identificação de algumas questões importantes para lidar

The use of agile methods continues to increase within software development but the agile processes do not contain the necessary steps to account for the user and realize the usability of the system. It seems it is therefore necessary to integrate the UCD methodology and agile methodology. What this integration should look like is not always apparent as the integration needs to be adapted to the specific context in each organization. Accompanied by a pre-study which identified difficulties with the integration, the current study examines how UCD specialists experience the communication through boundary objects in distributed agile teams. Furthermore the study examines how the understanding of the user is communicated to the developers in the agile teams and the potential of doing so with a design rationale. A case study was therefore performed with interviews of six UCD specialists to try to answers these questions. A content analysis was performed in relation to each research question and identified a number of themes relating to the experiences concerning; (1) communication through boundary objects, (2) how an understanding of the user is communicated, and (3) opinions of using design rationale for this purpose. Some of the conclusions drawn are that boundary objects only aim at communicating the interaction with the system, that they should be viewed as communication aids as they are not stand-alone and making them comprehensive would be even more time consuming. Furthermore, personas are not deemed fitting for communicating the understanding of the user to developers. This should instead be done by allowing developers to participate in user research.