Effect of Using Continuous Integration (CI) and Continuous Delivery (CD) Deployment in DevOps to reduce the Gap between Developer and Operation

Mowad, Abrar Mohammad; Fawareh, Hamed; Hassan, Mohammad

doi:10.1109/acit57182.2022.9994139

Cited by 5 publications

(3 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These sessions provide stakeholders with opportunities to express their preferences, identify issues, and suggest improvements to the system. Continuous integration and delivery (CI/CD) practices enable software development teams to deliver incremental changes to the system frequently and reliably (Mowad et al, 2022). By automating the build, testing, and deployment processes, CI/CD pipelines streamline the delivery of new features and updates to stakeholders in a timely manner.…”

Section: Emphasizing Iterative Refinement and Validationmentioning

confidence: 99%

Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model

Oladapo Adeboye Popoola,

Henry Ejiga Adama,

Chukwuekem David Okeke

et al. 2024

World J. Adv. Res. Rev.

View full text Add to dashboard Cite

Requirements elicitation is a crucial phase in the software development lifecycle, ensuring that stakeholders' needs are understood and translated into system specifications. Traditional methods often face challenges such as ambiguity, inconsistency, and evolving requirements, leading to project delays and cost overruns. This review proposes a conceptual model that integrates advancements and innovations in requirements elicitation to address these challenges comprehensively. The proposed model leverages various techniques, including but not limited to, natural language processing (NLP), machine learning (ML), and human-computer interaction (HCI), to enhance the accuracy and efficiency of requirements elicitation. NLP techniques enable automated analysis of textual requirements documents, extracting key information and identifying implicit requirements. ML algorithms facilitate the prediction of potential changes in requirements based on historical data and project context, enabling proactive management of evolving requirements. Moreover, the integration of HCI principles in the requirements elicitation process enhances stakeholder engagement and collaboration. Interactive interfaces and visualization tools enable stakeholders to provide feedback in real-time, fostering a more iterative and participatory approach to requirement gathering. Additionally, techniques such as prototyping and simulation facilitate early validation of requirements, reducing the risk of misinterpretation and ensuring alignment with stakeholders' expectations. Furthermore, the proposed model emphasizes the importance of context-awareness in requirements elicitation. By considering the organizational, cultural, and environmental context of a project, the model adapts its elicitation strategies and techniques to suit specific needs and constraints. Context-awareness also enables the identification of implicit requirements that may not be explicitly stated but are crucial for the success of the system. The model also addresses the challenge of managing conflicting requirements by introducing a systematic approach to requirements prioritization and negotiation. By employing multi-criteria decision-making techniques, stakeholders can collaboratively prioritize requirements based on their importance, feasibility, and impact on project objectives. Conflict resolution mechanisms facilitate consensus-building and trade-off analysis, ensuring that the final set of requirements reflects the collective interests of all stakeholders. Additionally, the proposed model emphasizes the iterative nature of requirements elicitation, advocating for continuous refinement and validation of requirements throughout the development lifecycle. Feedback loops enable stakeholders to review and revise requirements based on evolving needs and changing circumstances, thereby enhancing the adaptability and resilience of the system. The conceptual model presented in this review represents a holistic approach to requirements elicitation, leveraging advancements and innovations in technology, human interaction, and context-awareness. By integrating these elements, the model aims to enhance the accuracy, efficiency, and stakeholder satisfaction in the requirements elicitation process, ultimately contributing to the successful delivery of high-quality software systems.

show abstract

Section: Emphasizing Iterative Refinement and Validationmentioning

confidence: 99%

Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model

Oladapo Adeboye Popoola,

Henry Ejiga Adama,

Chukwuekem David Okeke

et al. 2024

World J. Adv. Res. Rev.

View full text Add to dashboard Cite

show abstract

“…These benefits include i) reduced deployment time; ii) early detection of errors (resulting in better code quality); and iii) the creation of an efficient, sometimes reusable infrastructure that leads to tighter feedback loops. While these benefits are also a direct result of agile development methods, they are realized through the VOLUME 4, 2016 implementation of a CI/CD pipeline [48].…”

Section: ) Pipelinesmentioning

confidence: 99%

Open Source Solutions for Vulnerability Assessment: A Comparative Analysis

Cruz,

Almeida,

Oliveira

2023

IEEE Access

View full text Add to dashboard Cite

As software applications continue to become more complex and attractive to cyber-attackers, enhancing resilience against cyber threats becomes essential. Aiming to provide more robust solutions, different approaches were proposed for vulnerability detection in different stages of the application lifecycle. This article explores three main approaches to application security: Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA). The analysis conducted in this work is focused on open-source solutions while considering commercial solutions to show contrast in the approaches taken and to better illustrate the different options available. It proposes a baseline comparison model to help evaluate and select the best solutions, using comparison criteria that are based on community standards. This work also identifies future opportunities for application security, highlighting some of the key challenges that still need to be addressed in order to fully protect against emerging threats, and proposes a workflow that combines the identified tools to be used for vulnerability assessments.

show abstract

“…It typically includes stages such as coding, building, testing, deployment, monitoring, and feedback. The goal of the DevOps pipeline is to streamline and accelerate the delivery of high-quality software by breaking down silos between development and operations teams and promoting continuous integration and continuous delivery (CI/CD) practices (Mowad et al, 2022). Traditionally, security has been treated as a separate phase in the software development lifecycle, often added as an afterthought or handled by a separate security team (Khan et al, 2022).…”

Section: Introductionmentioning

confidence: 99%

The emergence and importance of DevSecOps: Integrating and reviewing security practices within the DevOps pipeline

Oluwatosin Oluwatimileyin Abiona,

Oluwatayo Jacob Oladapo,

Oluwole Temidayo Modupe

et al. 2024

World J. Adv. Eng. Technol. Sci.

View full text Add to dashboard Cite

The emergence of DevSecOps marks a significant paradigm shift in software development, focusing on integrating security practices seamlessly into the DevOps pipeline. This paper explores the evolution, principles, and importance of DevSecOps in contemporary software engineering. DevSecOps arises from the recognition that traditional security measures often lag behind the rapid pace of DevOps development cycles, leading to vulnerabilities and breaches. By integrating security early and continuously throughout the software development lifecycle, DevSecOps aims to proactively identify and mitigate risks without impeding the agility and speed of DevOps practices. This paper delves into the core principles of DevSecOps, emphasizing automation, collaboration, and cultural transformation. Automation streamlines security processes, enabling the automated testing and validation of code for vulnerabilities. Collaboration fosters communication and shared responsibility among developers, operations, and security teams, breaking down silos and promoting a collective approach to security. Cultural transformation involves cultivating a security-first mindset across the organization, where security is not an afterthought but an inherent part of the development process. The importance of DevSecOps cannot be overstated in today's digital landscape, where cyber threats are omnipresent and the cost of security breaches is staggering. By integrating security into every stage of the DevOps pipeline, organizations can enhance their resilience to cyber attacks, comply with regulatory requirements, and build trust with customers. DevSecOps represents a holistic approach to software development that prioritizes security without compromising speed or innovation. Embracing DevSecOps principles is imperative for organizations seeking to stay ahead in an increasingly complex and hostile digital environment.

show abstract

Effect of Using Continuous Integration (CI) and Continuous Delivery (CD) Deployment in DevOps to reduce the Gap between Developer and Operation

Cited by 5 publications

References 12 publications

Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model

Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model

Open Source Solutions for Vulnerability Assessment: A Comparative Analysis

The emergence and importance of DevSecOps: Integrating and reviewing security practices within the DevOps pipeline

Contact Info

Product

Resources

About