In the world of software development, there is an increasing demand for software to keep up with rapid changes in its real-world context. A Resilient Digital Twin of an Organization is a type of software whose purpose is to digitally represent an organization or a component of an organization - as a Digital Twin -, and to keep doing so accurately throughout the real-world organization’s changes - a Resilient Digital Twin. An architectural pattern, called the EA Blueprint Pattern, has recently been proposed as a pattern to use for developing Resilient Digital Twins that can change together with the changes in the organization. However, software architecture is not the only factor that enables continuous change and adaptability in software. For software development teams to be able to deliver software rapidly and reliably, the software development process itself must be adapted to allow for frequent and fast changes. From this need, the Agile methodology and subsequently the set of work practises called DevOps has emerged. DevOps leverages automation and fast feedback as tools to facilitate a shorter system development life cycle and continuous delivery. The usage of DevOps is becoming increasingly popular in the software development field. It stands to reason that there is a need to ensure that the EA Blueprint Pattern is appropriate even in a DevOps context, where different tools and routines may be used than in traditional development. To complete this project, a use case of the EA Blueprint Pattern has been moved from a traditionally developed and deployed setting to a DevOps setting that includes essential DevOps tools such as Infrastructure as Code, a cloud environment, and a CI/CD pipeline that enables automatic deployment and therefore a shorter system development life cycle. By doing this, it can be gauged how well the EA Blueprint Pattern is adapted to a modern software development process which utilises the advantages of DevOps.

Increasingly complex dynamics in the software operations pose formidable software evolution challenges to the software industry. Examples of these dynamics include the globalization of software markets, the massive increase of interconnected devices worldwide with the internet of things, and the digital transformation to large-scale cyber-physical systems. To tackle these challenges, researchers and practitioners have developed impressive bodies of knowledge, including adaptive and autonomic systems, run-time models, continuous software engineering, and the practice of combining software development and operations (i.e., DevOps). Despite the tremendous strides the software engineering community has made toward managing highly dynamic systems, software-intensive industries face major challenges to match the ever-increasing pace. To cope with this rapid rate at which operational contexts for software systems change, organizations are required to automate and expedite software evolution on both the development and operations sides. The aim of our research is to develop continuous and autonomic methods, infrastructures, and tools to realize software evolution holistically. In this dissertation, we shift the prevalent autonomic computing paradigm and provide new perspectives and foci on integrating autonomic computing techniques into continuous software engineering practices, such as DevOps. Our methods and approaches are based on online experimentation and evolutionary optimization. Experimentation allows autonomic managers to make in- formed data-driven and explainable decisions and present evidence to stakeholders. As a result, autonomic managers contribute to the continuous and holistic evolution of design, configuration and deployment artifacts, providing guarantees on the validity, quality and effectiveness of enacted changes. Ultimately, our approach turns autonomic managers into online stakeholders whose contributions are subject to quality control. Our contributions are threefold. We focus on effecting long-lasting software changes through self-management, self-improvement, and self-regulation. First, we propose a framework for continuous software evolution pipelines for bridging offline and online evolution processes. Our framework’s infrastructure captures run-time changes and turns them into configuration and deployment code updates. Our functional validation on cloud infrastructure management demonstrates its feasibility and soundness. It effectively contributes to eliminate technical debt from the Infrastructure-as-Code (IAC) life cycle, allowing development teams to embrace the benefits of IAC without sacrificing existing automation. Second, we provide a comprehensive implementation for the continuous IAC evolution pipeline. Third, we design a feedback loop to conduct experimentation-driven continuous exploration of design, configuration and deployment alternatives. Our experimental validation demonstrates its capacity to enrich the software architecture with additional components, and to optimize the computing cluster’s configuration, both aiming to reduce service latency. Our feedback loop frees DevOps engineers from incremental improvements, and allows them to focus on long-term mission-critical software evolution changes. Fourth, we define a reference architecture to support short-lived and long-lasting evolution actions at run-time. Our architecture incorporates short-term and long-term evolution as alternating autonomic operational modes. This approach keeps internal models relevant over prolonged system operation, thus reducing the need for additional maintenance. We demonstrate the usefulness of our research in case studies that guide the designs of cloud management systems and a Colombian city transportation system with historical data. In summary, this dissertation presents a new approach on how to manage software continuity and continuous software improvement effectively. Our methods, infrastructures, and tools constitute a new platform for short-term and long-term continuous integration and software evolution strategies and processes for large-scale intelligent cyber-physical systems. This research is a significant contribution to the long-standing challenges of easing continuous integration and evolution tasks across the development-time and run-time boundary. Thus, we expand the vision of autonomic computing to support software engineering processes from development to production and back. This dissertation constitutes a new holistic approach to the challenges of continuous integration and evolution that strengthens the causalities in current processes and practices, especially from execution back to planning, design, and development. / Graduate

Online software businesses constantly face new challenges. Businesses are competing to deliver high-quality software solutions to their end users as quickly as possible. The performance of a software team in terms of software delivery needs to be measured to identify bottlenecks and understand what can be improved. This project is a case study of a software organisation that delivers online web solutions for a business. The organisation strives to follow a DevOps mindset and work data-driven by collecting data, learning from it and acting on the learnings. Our method to perform the case study was to study existing data collected by the organisation and conduct interviews with software professionals to get their insights about the software delivery performance of three software teams within the organisation. We focus on two metrics - deployment frequency and lead time for change - which measure the throughput of a software team and how often and fast it can deploy changes to production. Software organisations that adopt a DevOps approach are facing challenges with collecting data about their software delivery performance and learning from that data to improve their throughput. We aim to identify these challenges and discuss various problems that software organisations need to be aware of when measuring software delivery performance. We present the results from the interviews and collected metrics, analyse them and discuss them, as well as give suggestions on future research. We observe that there are multiple factors impacting software delivery performance and various challenges with measuring it accurately. This is related to the way of reporting data reliably and developing models to study and understand the collected data.

DevOps se define como un conjunto prácticas que aplican una cultura de colaboración entre el área de desarrollo y operaciones, para ello se forman equipos multidisciplinarios, cuyo objetivo es aportar valor añadido al producto software en el menor tiempo posible. Además, en DevOps se realizan procesos de desarrollo a partir de metodologías agiles con fases iterativas que permiten una mejor calidad en los procesos de integración y entrega continua denominados CI/CD. Por este motivo nos vemos en la necesidad de enfocarnos en el proceso de construcción de software empleando DevOps. El objetivo del presente trabajo es identificar y clasificar las publicaciones sobre procesos de construcción de software empleando DevOps. Se presenta como resultado del trabajo realizado, que se han encontrado inicialmente 900 artículos de investigación, de los cuales al ser depurados utilizando los criterios de exclusión e inclusión, se han obtenido finalmente 110 artículos de investigación, de esta manera se presentan las estadísticas de artículos por año, país, tipo de publicación, procesos, practicas, herramientas y la calidad sobre procesos de construcción de software empleando DevOps y, por tanto, se puede concluir que el año 2022 se obtuvo la mayor cantidad de artículos sobre el tema en investigación con un porcentaje de 21.8%. Se puede comprobar que Estados Unidos y la India son los países con mayor cantidad de publicaciones con 11.8% y 9.1% respectivamente, seguidos de China y Brasil quienes presentan 8.2% y 7.3% respectivamente.

Submitted by PPG Ci?ncia da Computa??o (ppgcc@pucrs.br) on 2018-07-16T17:26:53Z No. of bitstreams: 1 ELISA COSTA DIEL_DIS.pdf: 2030569 bytes, checksum: 97dac6ad532e10d4b88caec8f69d282e (MD5) / Approved for entry into archive by Sheila Dias (sheila.dias@pucrs.br) on 2018-07-23T11:12:32Z (GMT) No. of bitstreams: 1 ELISA COSTA DIEL_DIS.pdf: 2030569 bytes, checksum: 97dac6ad532e10d4b88caec8f69d282e (MD5) / Made available in DSpace on 2018-07-23T11:31:48Z (GMT). No. of bitstreams: 1 ELISA COSTA DIEL_DIS.pdf: 2030569 bytes, checksum: 97dac6ad532e10d4b88caec8f69d282e (MD5) Previous issue date: 2017-03-16 / Apesar de o ?gil buscar colabora??o com todos as partes envolvidas, a maioria dos projetos ?geis n?o extende essa colabora??o para o pessoal de opera??es. Problemas de comunica??o s?o um problema recorrente em equipes ?geis que tamb?m ? eminente na rela??o entre desenvolvedores e opera??es. Esta pesquisa visa compreender como a comunica??o acontece em DevOps a partir das percep??es dos praticantes. Para alcan?ar nosso objetivo, realizou-se uma Revis?o de Literatura sobre DevOps e Comunica??o, e conduziu-se um Estudo de Campo com dados qualitativos sendo coletados atrav?s de entrevistas. Os resultados indicam que hoje existem pelo menos tr?s configura??es diferentes de DevOps sendo aplicadas na ind?stria: profissionais Devs e Ops alocados na mesma equipe; uma equipe de DevOps com um conjunto de habilidades compartilhadas; e uma equipe separada de Dev e Ops trabalhando juntos. Apesar dessas configura??es, n?o foram encontradas nenhuma particularidade. Em resumo, os resultados indicam que os membros de equipes co-alocadas e multi-funcionais se comunicam melhor; ? importante trabalhar em conjunto e compartilhar conhecimentos t?cnicos; o poder de decis?o variar? de acordo com a situa??o enfrentada; entre outros. Nossas descobertas ajudam a diminuir a lacuna apontada por Erich, Amrit e Daneva entre Dev e Ops, avan?ando para uma melhor compreens?o de como profissionais DevOps colaboram, ajudando eles a melhorar suas pr?ticas de comunica??o em seu trabalho di?rio. / Even though agile actively seeks collaboration with all kinds of stakeholders, most agile projects do not extend toward the operations people. Issues in communication are a recurring issue in agile teams. Such issues are also eminent in the relationship between developers and operations. This study aims to understand how communication happens in DevOps from the perspective of practitioners. To achieve our goal, a Literature Review on DevOps and Communication was performed, and a Field Study was conducted with qualitative data being collected through interviews. Results revealed that today there are at least three different DevOps configurations being applied in the industry, being: Dev and Ops professionals allocated to the same team; a team of DevOps with a shared skill set; and a separate team of Dev and Ops working together. Despite the configurations, we did not find any particularities. In summary, results show that co-allocated and cross functional team members communicate better; it is important to work together as a single team and share technical knowledge; decision power changes based on the situation that is being faced; among others. Our findings help to narrow the gap pointed out by Erich, Amrit, and Daneva between Dev and Ops, moving towards a better understanding of how DevOps team collaborates by helping practitioners to improve their communication practices in their daily work.

This thesis gives an example of how decision analytic methods can be applied to choices in the adoption of cloud computing. The lifecycle of IT systems from planning to retirement is rapidly changing. Making a technology decision that can be justified and explained in terms of outcomes and benefits can be increasingly challenging without a systematic approach underlying the decision making process. It is proposed that better, more informed cloud adoption decisions would be taken if organisations used a structured approach to frame the problem to be solved and then applied trade-offs using an additive utility model. The trade-offs that can be made in the context of cloud adoption decisions are typically complex and rarely intuitively obvious. A structured approach is beneficial in that it enables decision makers to define and seek outcomes that deliver optimum benefits, aligned with their risk profile. The case study demonstrated that proven decision tools are helpful to decision makers faced with a complex cloud adoption decision but are likely to be more suited to the more intractable decision situations.

What is measured can be improved. That's why Red Hat and the PnT DevOps team are calling for a graphical visualization of metrics and key performance identifiers (KPIs) that will be available to customers, engineers, and stakeholders to review the progress of the PnT DevOps team.

In today’s knowledge-based economy, modern organisations understand the importance of technology in their quest to be considered global leaders. South African markets like others worldwide are regularly flooded with the latest technology trends which can complicate the acquisition, use, management and maintenance of software. To achieve a competitive edge, companies tend to leverage agile methods with the best possible combination of innovative supporting tools as a key differentiator. Software technology firms are in this light faced with determining how to leverage technology and efficient development processes for them to consistently deliver quality software projects and solutions to their customer base. Previous studies have discussed the importance of software development processes from a project management perspective. African academia has immensely contributed in terms of software development and project management research which has focused on modern frameworks, methodologies as well as project management techniques. While the current research continues with this tradition by presenting the pertinence of modern agile methodologies, it additionally further describes modern agile development processes tailored in a sub-Saharan context. The study also aims novelty by showing how innovative sometimes disruptive technology tools can contribute to producing African software solutions to African problems. To this end, the thesis contains an experimental case study where a web portal is prototyped to assist firms with the management of agile project management and engineering related activities. Literature review, semi-structure interviews as well as direct observations from the industry use case are used as data sources. Underpinned by an Activity Theory analytical framework, the qualitative data is analysed by leveraging content and thematic oriented techniques. This study aims to contribute to software engineering as well as the information systems body of knowledge in general. The research hence ambitions to propose a practical framework to promote the delivery of quality software projects and products. For this thesis, such a framework was designed around an information system which helps organizations better manage agile project management and engineering related activities. / Information Science / Ph. D. (Information Systems)

No description available.

Denna uppsats studerar förutsättningarna för att implementera mjukvaruutvecklings - metoden Continuous Delivery (CDE). Problemställningen som lade grunden för studien, var att det inte finns någon enhetlig standard för CDE. Studien ämnade att undersöka om detta innebar att metoden har varierande innebörd inom olika företag och om de således, i viss mån tillämpar skilda tillvägagångssätt med metoden. Ytterligare en aspekt var att se vilka utmaningar företagen upplevde vid övergången till CDE. Att undersöka om det var främst organisatoriska eller utvecklingsrelaterade problem som upplevts. Samt hur de hanterade kommunikation och tillit till medarbetarna och arbetet inom verksamheten under förändringen. För att belysa problemen, beskrevs teori med fokus på organisatoriska och tekniska utmaningar med Continuous - metoderna: Continuous Integration (CI), Continuous Delivery (CDE) och Continuous Deployment (CD). Teorikapitlet samt tidigare studier inkluderade även forskning om kringliggande koncept som DevOps och LEAN. Metoder, vilka kan underlätta implementationen av CDE. Datainsamlingen genomfördes med öppna individuella intervjuer med representanter från sex stycken företag, där de delade med sig av deras erfarenheter av och syn på CDE. Studien visar att anledningen till att företag väljer att arbeta med CDE, är att de vill gå från utvecklingsmetoder, vilka kräver många beslut inför varje förändring, till ett mer flexibelt arbetssätt där de funnit fördelar som: bättre kvalitet på det som levereras, snabbare leverans av affärsvärde till kunder samt kortare feedback - loopar. Företag som gör en övergång till CDE väljer dessutom ofta att inte automatisera hela vägen ut till produktion, enligt CD, då de ser utmaningar med att säkra kvalitén. Studien har identifierat ett antal faktorer som viktiga för en framgångsrik implementering av CDE, samt faktorer som kan resultera i en svår övergång. / This thesis studies the conditions needed for implementing the software development method Continuous Delivery (CDE). The problem identified for the study, is that there is no standardized approach for CDE as of today. The intentions of the study were to determine whether this means that the method will have a shifting tenor within different companies, and if so, will these companies implement the method with different approaches. Another aspect was to determine which types of challenges the companies were faced with during the transition towards CDE. To review whether the challenges were foremost organisational or development related. And how the organisations handled the communication and trust towards the co-workers and the development work within the organisation during the change towards the method. To highlight these issues, we presented theories with focus on organisational and technical challenges with the different Continuous practices were made. The practices being: Continuous Integration (CI), Continuous Delivery (CDE) and Continuous Deployment (CD). The theory chapter and former studies also contains research about surrounding concepts such as DevOps and LEAN methods, which can aim to facilitate the implementation of CDE. The empirical data collection was performed using open individual interviews with informants from six different companies, where they shared their experience and views on the method CDE. The study demonstrates that the reason organisations chose to implement CDE, is that they want to transform from software development methods, which requires a lot of decision making for any change, to a more flexible work procedure, in order to experience benefits such as: better quality of what is delivered, faster deliveries of business value to the customers and faster feedback-loops. Organisations that make the transition towards CDE also tend not to automate all the way to production, as in agreement with CD, this because the organisations identify challenges with assuring that the quality is sufficient. The study has identified a number of factors that are essential for a successful implementation of CDE, along with factors that may result in a less successful implementation.