DevOps dashboard

DevOps stands for development and operations. DevOps is a culture that empowers both development and operations teams to reduce time to market, make incremental improvements in response to changing conditions, and create a more efficient development process. Software development and delivery is a very complex practice, and managing it is even harder. Any kind of system or process needs to gather data and metrics to understand how it is performing. Understandably, measuring is essential in creating valuable software. However, measuring software is not easy and has been a problem for several organizations. There is the notion of utilizing a dashboard to ease the way DevOps teams interact and respond to data collected from systems to aid stakholders measure and monitor. The Design Science Research (DSR) methodology was chosen to build an artefact – the DevOps dashboard - and evaluate its value to the DevOps community. Several versions of the artifact were developed as part of an improvement process, with each iteration validated through interviews. It was identified that the dashboards generally accessible in the DevOps community are extremely specialized and lack a broader perspective of the entire ecosystem to help stakeholders in decision-making. The contribution of this research is the developed dashboard that allows more significant monitoring of a DevOps system employing metric categories that follow visualization best practices to improve user experience and impact the user decision process positively.DevOps é uma cultura que combina desenvolvimento e operação e que tem como principais objectivos reduzir o tempo de chegada ao mercado, fazer mudanças incrementais em resposta à mudança das condições, e construir um processo de desenvolvimento mais racionalizado. DevOps é adotado em todo o mundo, e com a adoção em massa, vêm as diferentes implementações e padronizações. Contudo o software responsável por agregar métricas não é de fácil implementação a nível de negócio e tem sido um problema para várias organizações. Com o intuito de medir e monitorizar software, existe a premissa de utilizar um painel de maneira a simplificar a forma como o DevOps pode interagir com as métricas. Esta tese centra-se no desenvolvimento de um painel de DevOps focado nas boas praticas de visualização com o objetivo principal de apoiar as equipas DevOps na tomada de decisões. A fim de continuar a desenvolver o painel, foi escolhida a metodologia Design Science Research (DSR) com o objectivo de construir um artefacto e o avaliar. Foi identificado que os dashboards utilizados na comunidade DevOps carecem de uma perspectiva mais ampla de todo o ecossistema de forma ajudar as partes interessadas na tomada de decisões. A contribuição desta investigação é o painel de DevOps que monitoriza um sistema de DevOps, que segue as melhores praticas de visualização, utilizando categorias de métricas de maneira a mais facilmente navegar e interpretar os dados, a fim de melhorar a experiência do utilizador e tomada de decisão

DevOps for Telehealth Services: Accelerating Deployment and Scalability

The use of telehealth services is increasing rapidly to increase access and delivery of remote medical care. However, there are significant technical barriers to rapid and reliable deployment of these services and their ability to handle high patient volumes. This study looks at how DevOps approaches can benefit telehealth providers and let it to overcome this obstacle. To maximize software development and infrastructure management, DevOps focuses on collaboration between development and IT operations teams. Telehealth platforms can be deployed rapidly while leveraging key DevOps skills such as automation, infrastructure-to-code, monitoring, and continuous integration Studies show that these techniques also improve scalability to meet demand changes. This makes it possible for telehealth providers to deliver digitally enabled care to a larger patient base

Design and Implementation of CI/CD over LoRaWAN : Continuous Integration and Deployment in LoRaWAN Edge Computing Applications

The recent rise of IoT devices in commercial and industrial spaces has created a demand for energy-efficient and reliable communication solutions. Communication solutions used on IoT devices vary depending on the applications. Wireless Low Power Wide Area Network (LPWAN) technologies have proven benefits, including long-range, low power, and low-cost communication alternatives for IoT devices. These benefits come at the cost of limitations, such as lower data rates. At the same time, the demand for faster, cheaper, and more reliable software deployment is becoming more critical than ever before. This thesis aims to find a way of having an automated process where software could be remotely deployed into LoRa nodes and investigate whether it is possible to implement a DevOps pipeline with both Continuous Integration (CI) and Continuous Deployment (CD) over LoRaWAN. For this thesis, an IoT LoRaWAN Edge computing application was chosen to determine how to design and implement a CI/CD pipeline to ensure a dependable and a continuous software deployment to the LoRaWAN nodes. Designing and implementing a Continuous Deployment pipeline for this IoT application was made possible with the integration of DevOps tools like GitHub and a TeamCity automation server. Additionally, a series of scripts have been designed and developed for this case, including automated tests, integration to cloud services, and file fragmentation and defragmentation tools. For software deployment and verification to the LoRaWAN network, a program was designed to communicate with the LoRaWAN network server over the WebSocket communication protocol. The implementation of DevOps in LoRaWAN applications is affected by the limitations of the LoRaWAN protocol. This thesis argues that these limitations can be eliminated using modular software and file fragmentation techniques. The implementation presented in this work can be extended for various time-critical use cases. The solution presented in this thesis also opens the door to combining LoRaWAN with other LPWAN technologies, like NB-IoT, that can be activated on demand

Critical success factors for DevOps adoption in information systems development

Adopting DevOps is challenging since it makes a significant paradigm shift in the Information Systems Development process. DevOps is a trending approach attached to the Agile Software Development Methodology, which facilitates adaptation to the customers' rapidly-changing requirements. It keeps one front step by introducing software operators who support the transmission between software and implementation into the software development team by confirming faster development, quality assurance, and easy maintenance of Information Systems (IS). However, software development companies reported challenges in adopting DevOps. It is critical to control those challenges while getting hold of the benefits by studying Critical Success Factors (CSF) for adopting DevOps. This study aimed to analyze the use of DevOps approach in IS developments by exploring CSFs of DevOps. A systematic literature review was applied to identify CSFs. These factors were confirmed by interviewing DevOps practitioners while identifying more frequent CSFs in the software development industry. Finally, the research presents a conceptual model for CSFs of DevOps, which is a guide to reap the DevOps benefits while reducing the hurdles for enhancing the success of IS. The conceptual model presents CSFs of DevOps by grouping them into four areas: collaborative culture, DevOps practices, proficient DevOps team, and metrics & measurement

Critical success factors for DevOps adoption in information systems development

Adopting DevOps is challenging since it makes a significant paradigm shift in the Information Systems Development process. DevOps is a trending approach attached to the Agile Software Development Methodology, which facilitates adaptation to the customers\u27 rapidly-changing requirements. It keeps one front step by introducing software operators who support the transmission between software and implementation into the software development team by confirming faster development, quality assurance, and easy maintenance of Information Systems. However, software development companies reported challenges in adopting DevOps. It is critical to control those challenges while getting hold of the benefits by studying Critical Success Factors (CSF) for adopting DevOps. This study aimed to analyze the use of DevOps approach in IS developments by exploring CSFs of DevOps. A systematic literature review was applied to identify CSFs. These factors were confirmed by interviewing DevOps practitioners while identifying more frequent CSFs in the software development industry. Finally, the research presents a conceptual model for CSFs of DevOps, which is a guide to reap the DevOps benefits while reducing the hurdles for enhancing the success of Information Systems. The conceptual model presents CSFs of DevOps by grouping them into four areas: collaborative culture, DevOps practices, proficient DevOps team, and Metrics & Measurement

Measuring software delivery performance using the four key metrics of DevOps

The Four Key Metrics of DevOps have become very popular for measuring IT-performance and DevOps adoption. However, the measurement of the four metrics deployment frequency, lead time for change, time to restore service and change failure rate is often done manually and through surveys - with only few data points. In this work we evaluated how the Four Key Metrics can be measured automatically and developed a prototype for the automatic measurement of the Four Key Metrics. We then evaluated if the measurement is valuable for practitioners in a company. The analysis shows that the chosen measurement approach is both suitable and the results valuable for the team with respect to measuring and improving the software delivery performance

TOWARDS UTILIZATION OF LEAN CANVAS IN THE DEVOPS SOFTWARE

The growth of technology made human to depend more on the software applications in his daily life and nowadays software companies focused more on building robust error free software to end customers in very short time. Software development companies facing one side growth of technological complexity and another side build the products fast to win a competition in business. In recent years growth of a DevOps given lot of new growth opportunity for the software companies. DevOps basic principles focused on the collaboration and communication as a key in between software development information technology professional. It is concentrated on the automating the most of the routine tasks such as development, delivery, infrastructure, support, software testing in software development process. DevOps also emphasize on the building, testing and releasing the software more quickly and in a reliable way

DevOps for Digital Leaders

DevOps; continuous delivery; software lifecycle; concurrent parallel testing; service management; ITIL; GRC; PaaS; containerization; API management; lean principles; technical debt; end-to-end automation; automatio

Factors that Contribute to the Success of a Software Organisation's DevOps Environment: A Systematic Review

This research assesses the aspects of software organizations' DevOps environments and identifies the factors contributing to these environments' success. DevOps is a recent concept, and many organizations are moving from old-style software development methods to agile approaches such as DevOps. However, there is no comprehensive information on what factors impact the success of the DevOps environment once organizations adopt it. This research focused on addressing this gap through a systematic literature review. The systematic review consisted of 33 articles from five selected search systems and databases from 2015 to 2021. Based on the included articles, 15 factors were identified and grouped into four categories: Collaborative Culture, Organizational Aspects, Tooling and Technology, and Continuous Practices. In addition, this research proposes a DevOps environment success factors model to potentially contribute to DevOps research and practice. Recommendations are made for additional research on the effectiveness of the proposed model and its success factors.Comment: 15 pages, 3 figures, 1 tabl