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.

A Simulation Model for Application Development in Data Warehouses

2022 ◽  
pp. 819-834
Author(s):  
Nayem Rahman
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Simulation Model ◽  
Data Warehouse ◽  
Development Process ◽  
Application Development ◽  
Cost Overruns ◽  
Development Lifecycle ◽  
Development Life Cycle ◽  
Software Development Lifecycle

Software development projects have been blamed for being behind schedule, cost overruns, and the delivery of poor quality product. This paper presents a simulation model of a data warehouse to evaluate the feasibility of different software development controls and measures to better manage a software development lifecycle, and improve the performance of the launched software. This paper attempts to address the practical issue of code defects in each stage of data warehouse application development. The author has compared the defect removal rate of their previous project to the newly proposed enhanced project development life cycle that uses code inspection and code scorecard along with other phases of software development life cycle. Simulation results show that the code inspection and code score-carding have achieved a significant code defect reduction. This has also significantly improved the software development process and allowed for a flawless production execution. The author proposes this simulation model to a data warehouse application development process to enable developers to improve their current process.

scholarly journals Teknik Representasi Kebutuhan Pengguna Menggunakan User Persona (Studi Kasus: Relasi antara Presensi dengan Kemampuan Kompetensi)

2021 ◽  
Vol 8 (2) ◽  
pp. 245
Author(s):  
Wahyu Andhika ◽  
Muhammad Iqbal ◽  
Munifah Nur ◽  
Rizkhi Dwi Nugroho
Keyword(s):  
Problem Solving ◽  
Software Development ◽  
Development Process ◽  
User Involvement ◽  
Software Development Process ◽  
Basic Requirement ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
System User

<p class="Abstrak">Elisitasi kebutuhan dalam proses pengembangan perangkat lunak adalah fase yang sangat penting dalam <em>Software Development Lifecycle</em>. Karena dalam tahap ini ditentukan dengan tepat mengenai apa yang akan dibuat. Sebuah sistem baiknya memenuhi kebutuhan dari pengguna. Oleh karena itu, melibatkan pengguna dalam elisitasi kebutuhan menjadi salah satu fase yang sangat berguna dalam menentukan kualitas <em>persona</em><em> experience</em> dalam suatu sistem. Keterlibatan pengguna membuat pengembang harus memahami dengan baik apa saja yang akan menjadi kebutuhan pengguna. Pendekatan yang efektif dibutuhkan untuk mengenali pengguna dan merangkum kebutuhannya dengan baik dengan segala keunikan pada setiap individu yang mungkin terjadi. Menggunakan metode <em>persona</em>, penelitian ini akan menyelesaikan permasalahan berupa informasi dari pengguna yang tidak menggambarkan kebutuhan secara lengkap. Metode ini akan membantu menggambarkan seorang pengguna secara mendalam mulai dari kepribadian, kemampuan hingga perilaku pengguna terhadap suatu masalah. Dokumen mengenai pengguna secara detail kemudian disimpulkan agar didapatkan sebuah kebutuhan dasar untuk diimplementasikan menjadi sebuah sistem. Selain menggunakan metode <em>persona</em><em> </em>dalam meningkatkan elisitasi kebutuhan, penelitian ini juga berfokus pada nilai kualitatif informasi tersebut dengan menambahkan implementasi teori iteratif. Teori ini digunakan untuk meningkatkan akurasi penyelesaian masalah, yang mana pada setiap tahapnya akan menghasilkan informasi yang akan memudahkan pengembang dalam mendesain perangkat lunak yang berorientasi pada pengguna.</p><p class="Abstrak"> </p><p class="Abstrak"><em><strong>Abstract</strong></em></p><div><p><em>Elicitation of needs in the software development process is a very important phase in the Software Development Lifecycle. Because in this stage it is precisely determined what will be made. A good system meets the needs of personas. Therefore, involving personas in the elicitation of needs is one phase that is very useful in determining the quality of persona experience in a system. User involvement makes the developer must understand well what will be the persona's needs. An effective approach is needed to recognize the persona and summarize his needs well with all the uniqueness in each individual that might occur. By using the persona method, this research will solve problems in the form of information from personas who do not describe the needs in full. This method will help describe a persona in depth ranging from personality, ability to persona behavior towards a problem. The detailed persona document is then concluded in order to obtain a basic requirement to be implemented into a system. In addition to using the persona method in increasing the elicitation of needs, this research also focuses on the qualitative value of the information by adding iterative theory implementation. This theory is used to improve the accuracy of problem solving, which at each stage will produce information that will facilitate developers in designing persona-oriented software.</em></p></div><p class="Abstrak"><em><strong><br /></strong></em></p>

User Interface Development Throughout the System Development Lifecycle

2011 ◽  
pp. 11-28 ◽  
Author(s):  
Scott Ambler
Keyword(s):  
User Interface ◽  
Software Development ◽  
Development Process ◽  
System Development ◽  
Software Process ◽  
Software Development Process ◽  
Application Development ◽  
Development Lifecycle ◽  
Software Development Lifecycle

A fundamental reality of application development is that the user interface is the system to the users. Software development process should reflect this fact. When you ask how user interface development should be reflected within an software development lifecycle (SDLC), you quickly discover that it affects all aspects of software development from requirements through to system delivery. This chapter discusses how user interface development should be reflected in a mature software process and overviews a collection of techniques for each phase of software development, showing how user interface development can easily be integrated into the overall software process.

scholarly journals SOLF - A SOFTWARE DEVELOPMENT LIFECYCLE BASED ON GOLF

2020 ◽  
Author(s):  
CRS Kumar
Keyword(s):  
Software Development ◽  
Development Project ◽  
Difficulty Level ◽  
Golf Course ◽  
Skill Levels ◽  
Development Lifecycle ◽  
Proposed Model ◽  
Development Life Cycle ◽  
Software Development Lifecycle ◽  
Engineering Models

In the game of Golf, a player is challenged to take the minimum strokes to complete a round of 18 holes under varying playing conditions. Players use different clubs depending on their skill levels to achieve the desired distance while taking shots at the golf ball from the start (tee off) to the hole (pin). Unlike other games which have a standardized playing area, the terrain in a golf course comprises of various natural and manmade features viz. fairways, bunkers, trees, water bodies etc, which increase the difficulty level of the game and keep the players challenged.The game of golf has a fascinating similarity to a software development life cycle. If the holes on a golf course are considered akin to milestones in a development project then most of the Software Engineering models focus on software development in groups. Thus, we propose SOLF i.e Software Development Lifecycle model based on Golf, as a SDLC ideal for individuals or a small group of 2-3 developers. The proposed model is easy to comprehend, flexible and optimally adjustable in a dynamic environment.SOLF divides the project into 18 stages wherein each stage of the project will have 3 to 6 tasks which are required to be completed within a fixed timeline. The stages are managed by creating checklists at the start akin to the pre-shot routines in golf and the customer feedback is received on reaching each of the milestones similar to applause in the game of golf. Terrain of the golf course is reflected as risk list which are varying for each of the stages.SOLF achieves 10x speedup in software development and research projects as it creates an environment of challenges and drives the developer towards self excellence. It also inculcates a spirit of competition and sportsmanship by challenging the developers on various 'terrains' of development.

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 DevOps phases across Software Development Lifecycle

2021 ◽  
Author(s):  
Mayank Gokarna
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Implementation Strategy ◽  
Quality Of Services ◽  
Comprehensive Collection ◽  
Development Lifecycle ◽  
Development Life Cycle ◽  
Software Development Lifecycle ◽  
Software Development Life Cycle

DevOps is the combination of cultural mindset, practices, and tools that increases a team's ability to release applications and services at high velocity. The development and operations teams always have a conflict around the scope of responsibility. With these differences the quality and speed of delivery across software Development Life Cycle is negatively impacted. DevOps is about removing the barriers between two traditionally delimited teams, development and operations. With DevOps, these two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the quality of services they provide. They take full ownership for their services, often beyond where their stated roles or titles have traditionally been scoped. Transitioning to DevOps requires a change in culture and mindset first. It is quite difficult to persuade a whole company to change its culture at once. This paper aims to bring different phases of software development lifecycle into DevOps implementation strategy and presents a comprehensive collection of leading tools used across Software Development life Cycle to automate and integrate different stages of software delivery. This paper also highlights on DevOps practices which span across different phases of the Software Development Lifecycle and how those can be implemented with different tools available.

Sign in / Sign up

Export Citation Format

Share Document