Agile Assessment Methods: Current State of the Art

Agility Assessment (AA) comprises tools, assessment techniques, and frameworks that focus on indicating how a company or a team is applying agile techniques and eventually pointing out problems in adopting agile practices at a project-level, organization-level or individual-level. There are many approaches for AA such as agility assessment models, agility checklists, agility surveys, and agility assessment tools. This report presents the state of the art approaches that support agility assessment

STUDI LITERATUR PENGEMBANGAN E-COMMERCE SEKOLAH MENGGUNAKAN PROGRESSIVE WEB APPS (PWA)

E-Commerce adalah platform yang banyak di kembangkana di berbagai sektor perekomonian terdapat perbedaan antara e-commerce dan market place. Kombinasi antara digital ecommerce dengan pendidikan diharapkan minimal mendapat pengalaman pembelajaran pada pengguna dalam berpartisipasi dalam transaksi digital. Dalam pengembangan e-commerce tidak lah mudah pengingat suatu system dengan data produk yang banyak dan model transaksi yang harus aman. Masalah leg dan keadaan internet indonesia jika suatu platform jika termuat banyak data akan menyebabkan respon system yang lama. PWA adalah teknik untuk pengembangan aplikasi agar tetap stabil jika sedang low connection dan sampai offline dengan catatan user pernah berkunjung ke dalam platform. Dengan model programming yang modern metode dengan bahasa pemrograman react.js, react native, vue.js  dan lain sebagainya memanfaatkan fungsi service-worker dan app.js untuk mensupport pengembangan Progressif web apps (PWA). Dari artikel ini didapati beberapa kesimpulan yaitu kecepatan dalam memuat data dari 12 jurnal yang di angkat dalam artikel ini kecepatan penggunaan pwa 11 dari 12 jurnal menunjukkan hasil positif dengan peningkatan kecepatan pada system. menyesuaikan dengan ukuran  berkas dan cache yang digunakan serta frekuensi pengaksessan halaman aplikasi pada ukuran berkas dan cache yang kecil pada pengembangan PWA di bandingkan native tanpa PWA dalam data pada jurnal yang di analisa pada gambar 14 menunjukkan 93,75 dari 100 nilai maksimal dari sisi penyimpanan. sedangkan pada ukuran berkas dan cache yang cukup besar pwa mampu mengungguli. untuk performa terkait pengguanaan memori pwa lebih sedikit karena ada nya tambahan pada pwa service worker sehingga dapat memecah proses dan berkibat meningkatnya kecepatan akses pada sistem web

Software developers reasoning behind adoption and use of software development methods – a systematic literature review

When adopting and using a Software Development Method (SDM), it is important to stay true to the philosophy of the method; otherwise, software developers might execute activities that do not lead to the intended outcomes. Currently, no overview of SDM research addresses software developers’ reasoning behind adopting and using SDMs. Accordingly, this paper aims to survey existing SDM research to scrutinize the current knowledge base on software developers’ type of reasoning behind SDM adoption and use. We executed a systematic literature review and analyzed existing research using two steps. First, we classified papers based on what type of reasoning was addressed regarding SDM adoption and use: rational, irrational, and non-rational. Second, we made a thematic synthesis across these three types of reasoning to provide a more detailed characterization of the existing research. We elicited 28 studies addressing software developers’ reasoning and identified five research themes. Building on these themes, we framed four future research directions with four broad research questions, which can be used as a basis for future research

Detection of microservice smells through static analysis

A arquitetura de microsserviços é um modelo arquitetural promissor na área de software, atraindo desenvolvedores e empresas para os seus princípios convincentes. As suas vantagens residem no potencial para melhorar a escalabilidade, a flexibilidade e a agilidade, alinhando se com as exigências em constante evolução da era digital. No entanto, navegar entre as complexidades dos microsserviços pode ser uma tarefa desafiante, especialmente à medida que este campo continua a evoluir. Um dos principais desafios advém da complexidade inerente aos microsserviços, em que o seu grande número e interdependências podem introduzir novas camadas de complexidade. Além disso, a rápida expansão dos microsserviços, juntamente com a necessidade de aproveitar as suas vantagens de forma eficaz, exige uma compreensão mais profunda das potenciais ameaças e problemas que podem surgir. Para tirar verdadeiramente partido das vantagens dos microsserviços, é essencial enfrentar estes desafios e garantir que o desenvolvimento e a adoção de microsserviços sejam bem-sucedidos. O presente documento pretende explorar a área dos smells da arquitetura de microsserviços que desempenham um papel tão importante na dívida técnica dirigida à área dos microsserviços. Embarca numa exploração de investigação abrangente, explorando o domínio dos smells de microsserviços. Esta investigação serve como base para melhorar um catálogo de smells de microsserviços. Esta investigação abrangente obtém dados de duas fontes primárias: systematic mapping study e um questionário a profissionais da área. Este último envolveu 31 profissionais experientes com uma experiência substancial no domínio dos microsserviços. Além disso, são descritos o desenvolvimento e o aperfeiçoamento de uma ferramenta especificamente concebida para identificar e resolver problemas relacionados com os microsserviços. Esta ferramenta destina-se a melhorar o desempenho dos programadores durante o desenvolvimento e a implementação da arquitetura de microsserviços. Por último, o documento inclui uma avaliação do desempenho da ferramenta. Trata-se de uma análise comparativa efetuada antes e depois das melhorias introduzidas na ferramenta. A eficácia da ferramenta será avaliada utilizando o mesmo benchmarking de microsserviços utilizado anteriormente, para além de outro benchmarking para garantir uma avaliação abrangente.The microservices architecture stands as a beacon of promise in the software landscape, drawing developers and companies towards its compelling principles. Its appeal lies in the potential for improved scalability, flexibility, and agility, aligning with the ever-evolving demands of the digital age. However, navigating the intricacies of microservices can be a challenging task, especially as this field continues to evolve. A key challenge arises from the inherent complexity of microservices, where their sheer number and interdependencies can introduce new layers of intricacy. Furthermore, the rapid expansion of microservices, coupled with the need to harness their advantages effectively, demands a deeper understanding of the potential pitfalls and issues that may emerge. To truly unlock the benefits of microservices, it is essential to address these challenges head-on and ensure a successful journey in the world of microservices development and adoption. The present document intends to explore the area of microservice architecture smells that play such an important role in the technical debt directed to the area of microservices. It embarks on a comprehensive research exploration, delving into the realm of microservice smells. This research serves as the cornerstone for enhancing a microservice smell catalogue. This comprehensive research draws data from two primary sources: a systematic mapping research and an industry survey. The latter involves 31 seasoned professionals with substantial experience in the field of microservices. Moreover, the development and enhancement of a tool specifically designed to identify and address issues related to microservices is described. This tool is aimed at improving developers' performance throughout the development and implementation of microservices architecture. Finally, the document includes an evaluation of the tool's performance. This involves a comparative analysis conducted before and after the tool's enhancements. The tool's effectiveness will be assessed using the same microservice benchmarking as previously employed, in addition to another benchmark to ensure a comprehensive evaluation

Estudio de mapeo sistemático de las herramientas y técnicas para la identificación de los niveles de agilidad del equipo de desarrollo en un proyecto de software

El presente estudio registra los instrumentos, herramientas y técnicas para identificar el nivel de agilidad, se realizó una investigación en base al Método del Mapeo Sistemático (SMS), se investigó en diferentes bibliotecas virtuales. Los instrumentos, herramientas y técnicas permiten identificar los niveles de agilidad tanto en las organizaciones y equipos. Se tiene como finalidad evaluar el conocimiento, además, el nivel de agilidad mediante diferentes escalas, al momento de desarrollar sus proyectos, contribuyen con el mejoramiento continuo.He present study records the instruments, tools and techniques to identify the level of agility, an investigation was carried out based on the Systematic Mapping Method (SMS), it was investigated in different virtual libraries. The instruments, tools and techniques allow to identify the levels of agility in both organizations and teams. The purpose is to evaluate knowledge, in addition, the level of agility through different scales, at the time of developing your projects, they contribute to continuous improvement

Relationship between mature software engineering practices and agility practices

This paper reports on research work on Argentinean software development organizations. The analysis pro-vides insights on the profile of the companies regarding the usage of agile methods and software engineering practices trends, their motivations, and drivers. The conclusions can be used to understand what drivers facilitate the understanding of bonds between both in order to increase their competitiveness in domestic and off-shore markets.Sociedad Argentina de Informática e Investigación Operativ

Market Offer For IKOR GMBH: Development of a business analysis to assess the usefulness of the Scaled Agile Framework for insurance companies

Internship Report presented as the partial requirement for obtaining a Master's degree in Information Management, specialization in Information Systems and Technologies ManagementIt has been known for years that agile methods have a major role to play in project management. Increasingly, frameworks for agile scaling are becoming more popular and widespread. The Scaled Agile Framework is one of them. It enjoys great popularity in many industries. Therefore, IKOR has considered that a market offer is needed that exactly fulfils this need for its customers. These are mainly insurance customers, who are still a few years behind the digital transformation compared to other industries. In order to create a solution for this, IKOR decided that a market offer was needed that assessed whether SAFe was a useful framework for the insurance company to adopt and provided an assessment of how far along the insurance company was in adopting SAFe. This internship report was prepared to fulfil and document this task. During the development of the market offer, SAFe, business analysis, and the implementation of workshops were dealt with from a theoretical as well as a practical point of view. The result was a business analysis in form of a questionnaire, a workshop concept for conducting the workshop with the client and a recommendation made to the client on the current status of his insurance. After the exemplary implementation, the procedure and the results were evaluated and classified by experts. They gave additional advice on how to use and expand the market offer

DevSecOps for web applications: a case study

O paradigma DevOps permite agilizar o processo de entrega de software. Visa reduzir as barreiras existentes entre as equipas responsáveis pelo desenvolvimento e as equipas de operação. Com recurso a estruturas de pipelines o processo de desenvolvimento de software é conduzido através de diversas etapas até à sua entrega. Estas estruturas permitem automatizar várias tarefas de forma a evitar erros humanos, liberta os intervenientes de tarefas morosas e repetitivas. Mais previsível e com maior exatidão o tempo necessário para as entregas de software é encurtado e mais frequente. Dadas estas vantagens o paradigma tem muita adoção por parte da indústria de desenvolvimento, no entanto, o aumento do volume das entregas acarreta desafios, nomeadamente no que diz respeito à segurança das soluções desenvolvidas. Negligenciar os fatores de segurança pode levar a organização a acarretar com custos financeiros e denegrir a sua reputação. A integração entre o paradigma DevOps e segurança originou o paradigma designado por DevSecOps. Este visa a adoção pelo processo de desenvolvimento de ações de segurança, que após inseridas nas diversas fases de entrega, permitirão analisar e validar a solução, de forma a assegurar a sua consistência. A arquitetura das aplicações web é por sua natureza acessível, o que resulta à sua maior exposição. Este projeto apresenta uma lista de problemas de segurança encontrados durante a pesquisa efetuada no domínio das aplicações web, analisa quais as ferramentas para a deteção e resolução destes problemas, quais as suas implicações no tempo de entrega de software e a sua eficiência na deteção de falhas. Concluí com uma implementação de um fluxo de execução utilizando o paradigma DevSecOps, para compreender a sua contribuição no melhoramento da qualidade do software.The DevOps paradigm streamlines the software delivery process, reducing the barriers between the teams involved in development and operations. It relies on pipelines to structure the development process until delivered. These structures enable the automation of many tasks, avoiding human error and freeing the team elements from doing slow and repeated tasks. More predictable and accurate development allows teams to reduce the time required for software deliveries and make them more frequent. Despite the wide adoption of the paradigm, the increase in deliveries cannot compromise the security aspects of the developed solutions. Companies may incur financial costs and tarnish their reputations by neglecting security factors. Joining security and DevOps originate a new paradigm, DevSecOps. It aims to bring more quality compliance and avoid risk by adding security considerations to discover all potential security defects before delivery. Web applications architecture, by their accessibility intent, has a vast exposed area. This project presents a list of common security issues found during the research performed in the web application security domain analyses, what tools are used to detect and solve these problems, which time implications they cause in the overall software delivery and their effectiveness in defect detection. It concludes with implementing a pipeline using the DevSecOps paradigm to establish its viability in improving software quality