scholarly journals DevOps phases across Software Development Lifecycle

2020 ◽  
Author(s):  
Mayank Gokarna
Keyword(s):  
Software Development ◽  
High Velocity ◽  
Quality Of Services ◽  
Development Lifecycle ◽  
Software Development Lifecycle

DevOps is the combination of cultural mindset, practices, and tools that increases a team's ability to release applications and services at high velocity. Transitioning to DevOps requires a change in culture and mindset first. 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. This paper aims to bring different phases of software development lifecycle into DevOps implementation strategy.This paper highlights on DevOps practices which span across different phases of the Software Development Lifecycle (SDLC).

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.

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.

Innovative Approaches in Pair Programming to Enhance the Quality of Software Development

2018 ◽  
Vol 10 (2) ◽  
pp. 42-53
Author(s):  
Naresh E. ◽  
Vijaya Kumar B.P.
Keyword(s):  
Software Development ◽  
Negative Impact ◽  
Extreme Programming ◽  
Pair Programming ◽  
Software Projects ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Efficient Code ◽  
The Impact

The article tries to shed some light on the impact of human psychology on the effective use of pair programming in the modern Software development lifecycle such as SCRUM, Extreme Programming which are in turn used on heterogeneous software projects. This article also tries to identify that if the authors try to pair people keeping their psychology in mind that pair can come up with code with fewer defects, with efficient code, if the paper tries to pair people randomly without any planning or thinking might create a pair which let aside create inefficient code and lead to be unproductive nature, and even it will create a negative impact on the project and the team. This article introduces a few novel approaches in framing the pairs in pair programming's like known and unknown pairs, coder and reviewer pair and coder and tester pair. Applying the described approaches, an industry can improve the quality of the delivered product and improve the efficiency of software engineers.

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>

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.

Creating and Applying Security Goal Indicator Trees in an Industrial Environment

2014 ◽  
pp. 999-1013
Author(s):  
Alessandra Bagnato ◽  
Fabio Raiteri ◽  
Christian Jung ◽  
Frank Elberzhager
Keyword(s):  
Software Development ◽  
Software Systems ◽  
Full Potential ◽  
Security Vulnerabilities ◽  
Industrial Project ◽  
Project Environment ◽  
Development Tools ◽  
Development Lifecycle ◽  
Software Development Lifecycle

Security inspections are increasingly important for bringing security-relevant aspects into software systems, particularly during the early stages of development. Nowadays, such inspections often do not focus specifically on security. With regard to security, the well-known and approved benefits of inspections are not exploited to their full potential. This book chapter focuses on the Security Goal Indicator Tree application for eliminating existing shortcomings, the training that led to their creation in an industrial project environment, their usage, and their reuse by a team in industry. SGITs are a new approach for modeling and checking security-relevant aspects throughout the entire software development lifecycle. This book chapter describes the modeling of such security goal based trees as part of requirements engineering using the GOAT tool dedicated plug-in and the retrieval of these models during the various phases of the software development lifecycle in a project by means of Software Vulnerability Repository Services (SVRS) created in the European project SHIELDS (SHIELDS - Detecting known security vulnerabilities from within design and development tools).

Sign in / Sign up

Export Citation Format

Share Document