End to End Automation on Cloud with Build Pipeline: The Case for DevOps in Insurance Industry, Continuous Integration, Continuous Testing, and Continuous Delivery

2015 ◽  
Author(s):  
Mitesh Soni
Keyword(s):  
Insurance Industry ◽  
Continuous Integration ◽  
Continuous Testing ◽  
Continuous Delivery ◽  
End To End

scholarly journals Design Methods and Processes for ML/DL models

2021 ◽  
Author(s):  
◽  
Meenu Mary John
Keyword(s):  
Embedded Systems ◽  
Design Methods ◽  
Key Factors ◽  
High Performing ◽  
Structured Design ◽  
Continuous Delivery ◽  
End To End ◽  
Access To Data ◽  
Structured Design Methods ◽  
Decentralized Architecture

Context: With the advent of Machine Learning (ML) and especially Deep Learning (DL) technology, companies are increasingly using Artificial Intelligence (AI) in systems, along with electronics and software. Nevertheless, the end-to-end process of developing, deploying and evolving ML and DL models in companies brings some challenges related to the design and scaling of these models. For example, access to and availability of data is often challenging, and activities such as collecting, cleaning, preprocessing, and storing data, as well as training, deploying and monitoring the model(s) are complex. Regardless of the level of expertise and/or access to data scientists, companies in all embedded systems domain struggle to build high-performing models due to a lack of established and systematic design methods and processes. Objective: The overall objective is to establish systematic and structured design methods and processes for the end-to-end process of developing, deploying and successfully evolving ML/DL models. Method: To achieve the objective, we conducted our research in close collaboration with companies in the embedded systems domain using different empirical research methods such as case study, action research and literature review. Results and Conclusions: This research provides six main results: First, it identifies the activities that companies undertake in parallel to develop, deploy and evolve ML/DL models, and the challenges associated with them. Second, it presents a conceptual framework for the continuous delivery of ML/DL models to accelerate AI-driven business in companies. Third, it presents a framework based on current literature to accelerate the end-to-end deployment process and advance knowledge on how to integrate, deploy and operationalize ML/DL models. Fourth, it develops a generic framework with five architectural alternatives for deploying ML/DL models at the edge. These architectural alternatives range from a centralized architecture that prioritizes (re)training in the cloud to a decentralized architecture that prioritizes (re)training at the edge. Fifth, it identifies key factors to help companies decide which architecture to choose for deploying ML/DL models. Finally, it explores how MLOps, as a practice that brings together data scientist teams and operations, ensures the continuous delivery and evolution of models.

scholarly journals A review on Continuous Integration, Delivery and Deployment using Jenkins

2021 ◽  
Vol 23 (06) ◽  
pp. 919-922
Author(s):  
Arpita S.K ◽  
◽  
Amrathesh Amrathesh ◽  
Dr. Govinda Raju M ◽  
◽  
...  
Keyword(s):  
Software Development ◽  
Software Tools ◽  
Integration Process ◽  
Continuous Integration ◽  
Software Deployment ◽  
Development Cycle ◽  
Continuous Delivery ◽  
Standard Practices ◽  
Development Methods ◽  
The Given

Continuous Integration (CI) is the technique of integrating small changes made to the code more often rather than waiting till the end of the development cycle for integration. The software practice wherein the software deployment can be done anytime to the market is called Continuous Delivery (CD). With continuous integration and continuous delivery, the problem of taking time to find and resolve the bug can be reduced to a large extent. As the time to find the bugs and fix them gets reduced, many releases adhering to the given timeline can be made by an organization. Various software tools have been developed for the continuous integration process which includes Jenkins, Bitbucket, TeamCity. In this paper, a review on the standard practices, approaches, challenges faced while using the continuous integration/delivery in the software development, methods of solving them, and using Jenkins for the implantation of continuous integration/delivery is done.

scholarly journals Quality Maintenance and Monitoring using Azure CI pipeline and .Net Technologies

2020 ◽  
pp. 642-648
Author(s):  
Ishwarya S ◽  
S. Kuzhalvaimozhi
Keyword(s):  
High Performance ◽  
Test Driven Development ◽  
Quality Maintenance ◽  
Continuous Integration ◽  
Agile Methodology ◽  
Annual Basis ◽  
Continuous Delivery ◽  
And Performance ◽  
Software Development Practices

<p>The paper is about how the application is maintained and monitored using Azure CI pipeline. Maintaining and monitoring the quality of the software plays an important role in company’s growth and performance. This is achieved using DevOps. Few years back agile methodology was playing a major role in the industry, software were deployed in monthly, quarterly or annual basis, which is time consuming. However, now industries are moving towards DevOps methodology where in the software deployed multiple times a day. This methodology provides the organization to constantly and reliably add new features and automatically deploy them across various platforms or environment in order to gain high performance and quality assurance products. Continuous integration and Continuous delivery/ Continuous deployment are the pillars of DevOps. Continuous integration, Continuous delivery and Continuous deployment are the continuous software development practices of industry. By automating the build, test and deployment of software, CI/CD bridges the space between development and operation teams. This paper also concentrates on how the Test Driven Development features of .Net technologies supports the quality maintenance and monitoring of the application.</p>

scholarly journals Implementation of Docker and Continuous Integration / Continuous Delivery for Management Information System Development

2021 ◽  
Vol 3 (2) ◽  
pp. 20-24
Author(s):  
AKBAR DHANY
Keyword(s):  
Information System ◽  
Management Information System ◽  
System Development ◽  
Academic Community ◽  
University Management ◽  
Management Information ◽  
Continuous Integration ◽  
Continuous Delivery ◽  
Distribution Process ◽  
System Developer

A series of Development and Operations (DevOps) in the process of making the Narotama University Management Information System have not been implemented properly by previous developers. There are improvements or additional features of the Management Information System that are in accordance with the functionality and the increasing development needs that will be used by the academic community, so that the Management Information System developer has a little difficulty in integrating documents and distributing applications with different packages to the Production Server. In this study, a new system design is proposed by applying the practice of Continuous Integration / Continuous Delivery as a document integration process and can simplify the application distribution process, as well as implementing the Docker Container Platform as an application container with different packages that can be run on production server together. The results of implementing the practice of Continuous Integration / Continuous Delivery and the implementation of the Docker Container Platform are able to help integrate documents between developers and be able to release fixes and add features packaged in different containers automatically and periodically without long delays. which only takes an average of 17.9 seconds in the process of sending the application to the Production Server.

scholarly journals IMPLEMENTASI CONTIONOUS INTEGRATION DAN CONTINOUS DEPLOYMENT PADA APLIKASI LEARNING MANAGEMENT SYSTEM DI PT. MILLENNIA SOLUSI INFORMATIKA

2021 ◽  
Vol 8 (1) ◽  
pp. 183-186
Author(s):  
Ari Purno Wahyu ◽  
Indra Guna Noviantama
Keyword(s):  
Management System ◽  
Learning Management System ◽  
Continuous Integration ◽  
Continuous Delivery ◽  
Learning Management

Aplikasi Learning Management System atau LMS merupakan produk aplikasi yang dikembangkan oleh PT. Millennia Solusi Informatika. Aplikasi LMS ini telah digunakan oleh salah satu jaringan sekolah swasta. Dalam pengembangannya, aplikasi ini menggunakan metode scrum dimana pendekatan metode ini bersifat agile dan dapat menyesuaikan kebutuhan dengan cepat. Berangkat dari hal tersebut maka dalam proses delivery perangkat lunak ini maka perlu menggunakan konsep continuous integration dan continuous deployment guna memenuhi alur pengembangan yang bersifat agile dan dapat berulang. Continous Integration (CI) adalah pengintegrasian kode ke dalam repositori kode kemudian menjalankan penggunaan secara otomatis, cepat dan sering. Sementara Continuous Deployment atau Continuous Delivery (CD) adalah praktik yang dilakukan setelah proses CI selesai dan seluruh kode berhasil terintegrasi, sehingga aplikasi bisa dibangun dan dirilis secara otomatis. Dengan menggunakan metode CI/CD diharapkan dalam proses penyampaian aplikasi dapat terus berlangsung otomatis, cepat dan sering walaupun aplikasi tersebut sudah digunakan oleh pengguna.

scholarly journals A Comparison on Continuous Integration and Continuous Deployment (CI/CD) on Cloud Based on Various Deployment and Testing Strategies

2021 ◽  
Vol 9 (VI) ◽  
pp. 4968-4977
Author(s):  
Avishek Singh
Keyword(s):  
Software Development ◽  
Development Process ◽  
Continuous Integration ◽  
Testing Strategies ◽  
Rapid Release ◽  
Development Lifecycle ◽  
Continuous Delivery ◽  
Software Development Lifecycle ◽  
Continuous Interaction ◽  
Continuous Feedback

Continuous Integration/Continuous Delivery/Deployment (CI/CD) emphasizes the rapid release of small, incremental changes and the use of automation throughout the development process. CI/CD technique is central to DevOps and key to its success. Consumers expect to have continuous interaction with DevOps team so that they can provide their continuous feedback. DevOps is blending of two terms: development and operations which aims to provide conjoin approach to industry’s software development and operation team job in software development lifecycle. Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. Shows the comparison on deployments. With the increasing interest in literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices.

Continuous Integration/Continuous Delivery with Azure DevOps

2020 ◽  
pp. 493-519
Author(s):  
Julian Soh ◽  
Marshall Copeland ◽  
Anthony Puca ◽  
Micheleen Harris
Keyword(s):  
Continuous Integration ◽  
Continuous Delivery
Sign in / Sign up

Export Citation Format

Share Document