See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/368845600

DevOps -software development methodology

Research Proposal · February 2023

DOI: 10.13140/RG.2.2.11626.80327

CITATION READS

1 1,837

1 author:

Velibor Božić

553 PUBLICATIONS 96 CITATIONS

SEE PROFILE

All content following this page was uploaded by Velibor Božić on 28 February 2023.

The user has requested enhancement of the downloaded file.

VELIBOR BOŽIĆ Research proposal

DevOps - software development methodology

Introduction

DevOps is a software development methodology that focuses on collaboration,

communication, and integration between software development teams and IT operations
teams. The goal of DevOps is to streamline the software development process, reduce time-
to-market, and increase the reliability and quality of software releases.

DevOps involves a set of practices and tools that enable developers to automate the
software development process, including code building, testing, deployment, and
monitoring. DevOps also involves a cultural shift that emphasizes continuous collaboration
and communication between developers and operations teams, as well as a focus on
delivering value to customers.

Some key practices in DevOps include continuous integration and delivery,

infrastructure as code, automated testing, and monitoring and logging. By adopting these
practices, organizations can achieve faster and more frequent software releases with fewer
errors and less downtime, leading to greater customer satisfaction and increased revenue.

History

DevOps as a concept is the result of a collaborative effort between members of the

development and operations communities. The term "DevOps" is widely attributed to
Patrick Debois, a Belgian IT consultant, who first used it in 2009 to describe a series of events
he organized to bring together developers and IT operations professionals.

However, the roots of DevOps can be traced back to the Agile software development
movement, which emphasized collaboration and iterative development. Other important
influences include the Lean manufacturing philosophy, which emphasizes continuous
improvement and waste reduction, and the IT service management (ITSM) framework
known as ITIL (Information Technology Infrastructure Library), which provides guidelines for
managing IT services.

Over time, DevOps has evolved into a distinct discipline with its own principles,
practices, and tools, driven by a community of practitioners who continue to refine and
VELIBOR BOŽIĆ Research proposal

improve the methodology. Today, DevOps is widely used in software development and IT
operations, and has become an essential part of modern software development processes.

Principles, practices and tools od DevOps

DevOps is based on a set of principles, practices, and tools that are designed to
improve collaboration and communication between development and operations teams,
automate the software development and deployment process, and drive continuous
improvement. Some of the key principles, practices, and tools of DevOps include:

Principles

1. Culture: DevOps emphasizes a culture of collaboration, communication, and shared

responsibility between development and operations teams.

2. Automation: DevOps relies heavily on automation to streamline the software

development and deployment process and reduce the risk of errors and
inconsistencies.

3. Continuous improvement: DevOps encourages a culture of continuous improvement,

with regular feedback loops and data-driven analysis to identify opportunities for
improvement.

4. Measurement: DevOps emphasizes the importance of measuring and analyzing

performance metrics to track progress and identify areas for improvement.

Practices

1. Continuous Integration (CI): The practice of automatically building and testing

software changes as soon as they are submitted, to catch errors early and prevent
integration issues.

2. Continuous Delivery (CD): The practice of automating the software release process to
enable frequent, reliable, and low-risk releases.

3. Infrastructure as Code (IaC): The practice of managing infrastructure as code, using

tools like Ansible, Chef, or Puppet, to automate the provisioning, configuration, and
management of infrastructure.
VELIBOR BOŽIĆ Research proposal

4. Automated Testing: This practice involves automating the testing of software

applications to ensure that they meet quality standards. This is done using tools like
Selenium, JUnit, and TestNG.

5. Monitoring and Logging: This practice involves monitoring applications in production

and logging issues for analysis. This is done using tools like Prometheus, Nagios, and
ELK Stack.

6. Containerization: This practice involves packaging an application and its

dependencies into a container, making it easier to deploy and run the application
consistently across different environments. This is done using tools like Docker and
Kubernetes.

7. Collaboration and Communication: DevOps culture emphasizes collaboration and

communication between developers, operations teams, and other stakeholders. This
is supported by tools like Slack, Microsoft Teams, and Zoom.

8. Configuration Management: The practice of managing software configurations and

dependencies in a centralized way, to ensure consistency and reduce errors.

Tools

1. Source Control Management (SCM) tools, such as Git or SVN, to manage version
control and collaboration between developers.

2. Continuous Integration and Continuous Delivery (CI/CD) tools, such as Jenkins, Travis
CI, or CircleCI, to automate the software build, test, and deployment process.

3. Infrastructure as Code (IaC) tools, such as Ansible, Chef, or Puppet, to automate the
provisioning, configuration, and management of infrastructure.

4. Monitoring and Alerting tools, such as Nagios, New Relic, or Datadog, to track system
performance and detect issues.

By adopting these principles, practices, and tools, organizations can create a more
efficient, reliable, and scalable software development and deployment process, leading to
higher quality software and better outcomes for users and stakeholders.
VELIBOR BOŽIĆ Research proposal

The process od DevOps in software developing

The DevOps process in software development typically involves the following steps:

1. Plan: The planning stage involves defining the scope of the project, setting goals and
objectives, and determining the resources required to achieve those goals. This stage
also involves identifying potential risks and developing contingency plans to mitigate
those risks.

2. Develop: In the development stage, the actual coding and software development
takes place. This stage involves collaboration between development and operations
teams to ensure that code is optimized for deployment and operations.

3. Test: The testing stage involves evaluating the software for defects and bugs, and
ensuring that it meets the requirements and specifications defined in the planning
stage. This stage includes automated testing, manual testing, and user acceptance
testing.

4. Deploy: The deployment stage involves preparing the software for release, including
configuring and optimizing the environment for deployment, ensuring that all
dependencies are met, and automating the deployment process as much as possible.

5. Operate: The operate stage involves managing the software in production, including
monitoring performance, detecting and responding to issues, and ensuring that the
software is running smoothly and meeting user needs.

6. Monitor: The monitoring stage involves collecting data on the performance of the
software in production, analyzing that data to identify opportunities for
improvement, and making adjustments as necessary to improve the performance
and functionality of the software.

7. Iterate: The iteration stage involves repeating the process from the beginning,
incorporating feedback from users and stakeholders to continually improve the
software and the DevOps process itself.

Throughout the DevOps process, collaboration and communication between

development and operations teams is critical to ensuring that software is optimized for
VELIBOR BOŽIĆ Research proposal

deployment and operations, and that it meets the needs of users and stakeholders. The use
of automation, continuous testing and integration, and other DevOps practices can help
ensure that software is released quickly, efficiently, and with high quality.

Preconditions for using DevOps

There are several preconditions that an organization must meet to effectively use
DevOps. Here are some of the key preconditions:

1. Agile Development: DevOps is built on Agile principles, so an organization must have

a well-established Agile development process to fully leverage DevOps.

2. Continuous Integration (CI): An organization must be able to integrate code changes

into a single codebase multiple times a day to effectively use DevOps. This requires a
reliable version control system and a strong CI pipeline.

3. Automation: DevOps is all about automation, so an organization must be willing to

automate as many parts of the software development process as possible. This
requires investment in tools and resources.

4. Collaborative Culture: DevOps requires close collaboration and communication

between development and operations teams, so an organization must have a
collaborative culture to make DevOps work effectively.

5. Test Automation: To fully leverage DevOps, an organization must have a well-

established and automated testing process to ensure that new code changes do not
introduce errors or bugs.

6. Infrastructure as Code: An organization must be able to manage infrastructure using

code rather than manual processes to effectively use DevOps. This requires
investment in tools and resources.

7. Continuous Deployment: To truly reap the benefits of DevOps, an organization must

be able to continuously deploy code changes to production. This requires a well-
established deployment process and a reliable infrastructure.

By meeting these preconditions, an organization can fully leverage DevOps to

improve the speed, quality, and reliability of their software development process.
VELIBOR BOŽIĆ Research proposal

Optimal using of DevOps

DevOps is optimal for organizations that want to:

1. Deliver software faster: DevOps helps organizations deliver software faster by

streamlining the software development process and automating many tasks. This
reduces the time to market for new features and enables organizations to respond to
market demands more quickly.

2. Improve software quality: DevOps emphasizes continuous testing and monitoring,

which helps organizations detect and fix errors early in the development process.
This results in higher-quality software that is more reliable and less prone to errors
and downtime.

3. Increase collaboration and communication: DevOps promotes collaboration and

communication between development and operations teams, which helps to break
down silos and improve alignment across the organization. This leads to better
teamwork and more effective decision-making.

4. Reduce costs: DevOps helps organizations reduce costs by automating many tasks
and optimizing the software development process. This reduces the need for manual
intervention and improves efficiency, which can result in cost savings.

5. Scale applications: DevOps helps organizations scale applications more easily by using
technologies like containers and microservices. This enables organizations to quickly
deploy new instances of applications and scale them up or down based on demand.

DevOps is optimal for organizations that want to improve the speed, quality, and
reliability of their software development process while promoting collaboration and
communication across the organization.
VELIBOR BOŽIĆ Research proposal

Dfferences and similarity among model driven architecture, agile programming and
DevOps

Model-driven architecture (MDA), agile programming, and DevOps are all approaches
to software development, but they differ in their focus, principles, and practices.

MDA is a software development approach that emphasizes the use of models to design and
build software systems. The goal of MDA is to increase software development productivity,
reduce development costs, and improve software quality. MDA emphasizes the use of
standards-based modeling languages and tools, such as UML, to create models that describe
the system's structure, behavior, and functionality. The models are then transformed into
code using code generation tools, which automates much of the software development
process.

Agile programming is a software development approach that emphasizes

collaboration, flexibility, and iterative development. Agile focuses on delivering working
software quickly and responding to change quickly. Agile methodologies, such as Scrum and
Kanban, rely on short iterations, continuous feedback, and close collaboration between
developers, product owners, and customers. Agile principles include responding to change,
delivering working software frequently, and promoting sustainable development practices.

DevOps is a software development approach that emphasizes collaboration,

automation, and continuous delivery. DevOps aims to improve communication and
collaboration between developers and operations teams to reduce cycle times, increase
software quality, and accelerate time-to-market. DevOps principles include collaboration,
automation, monitoring, and continuous improvement. DevOps practices include continuous
integration and delivery, infrastructure as code, and automated testing and deployment.

While MDA, agile programming, and DevOps share some similarities, such as a focus
on collaboration and automation, they differ in their primary goals and practices. MDA is
primarily concerned with improving software development productivity and quality through
the use of models, while agile programming and DevOps are focused on delivering working
software quickly and responding to change. Agile programming emphasizes collaboration
and iterative development, while DevOps focuses on collaboration and continuous delivery.
VELIBOR BOŽIĆ Research proposal

Ultimately, the choice of which approach to use depends on the specific needs and goals of
the software development team and the organization.

Diference between DevOps and agile programmming

DevOps and Agile programming are both software development methodologies,

share some similarities, such as a focus on collaboration and automation but they have some
key differences. Here are some of the main differences:

1. Focus: Agile programming focuses on iterative and incremental development, with a

focus on delivering working software at the end of each iteration. DevOps, on the
other hand, focuses on streamlining the software development process and reducing
the time it takes to get software from development to production.

2. Team Structure: Agile programming typically involves cross-functional teams that

include developers, testers, and other stakeholders. DevOps, on the other hand, is a
collaborative approach that involves both development and operations teams
working together to streamline the software development process.

3. Scope: Agile programming focuses on the development process, while DevOps

extends this focus to include the entire software delivery pipeline, including
deployment, monitoring, and maintenance.

4. Automation: While both methodologies emphasize automation, DevOps places a

greater emphasis on automating the software delivery process, including testing,
deployment, and monitoring.

5. Culture: Agile programming emphasizes a culture of collaboration and

communication, while DevOps takes this culture to the next level by breaking down
the barriers between development and operations teams and creating a culture of
shared responsibility for software delivery.

While both methodologies share some similarities, they have different areas of focus
and different team structures. Agile programming is focused on iterative and incremental
development, while DevOps is focused on streamlining the software delivery process by
promoting collaboration and automation between development and operations teams.
VELIBOR BOŽIĆ Research proposal

Skills which are important for DevOps

DevOps is a cross-functional approach to software development that requires a range

of technical and non-technical skills. Here are some of the key skills that are important for
DevOps:

1. Automation: DevOps emphasizes automation at every stage of the software

development process, so it's important to have strong automation skills. This includes
skills in scripting, configuration management tools, and continuous
integration/continuous deployment (CI/CD) pipelines.

2. Cloud Computing: Most DevOps environments rely on cloud computing platforms, so

it's important to have skills in cloud computing technologies such as Amazon Web
Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP).

3. Infrastructure as Code: DevOps relies heavily on Infrastructure as Code (IaC) tools like
Terraform, Ansible, or Puppet, so it's important to have skills in IaC technologies and
concepts.

4. Collaboration and Communication: DevOps emphasizes collaboration and

communication between development and operations teams, so it's important to
have strong communication and collaboration skills. This includes skills in project
management, agile methodologies, and effective communication techniques.

5. Continuous Improvement: DevOps is all about continuous improvement, so it's

important to have a mindset that embraces experimentation and a willingness to
learn and adapt. This includes skills in problem-solving, critical thinking, and data
analysis.

6. Security: Security is an increasingly important consideration in DevOps, so it's

important to have skills in security technologies and practices. This includes skills in
security testing, vulnerability management, and compliance.

DevOps requires a combination of technical and soft skills, including automation,

cloud computing, collaboration, continuous improvement, and security. The most effective
DevOps professionals are those who can balance these skills and adapt to changing
technology and business needs.
VELIBOR BOŽIĆ Research proposal

Using DevOps in building integrated hospital information system

DevOps can be a valuable approach for building an integrated hospital information

system, as it can help ensure that the system is delivered quickly, reliably, and securely. Here
are some ways that DevOps can be applied in this context:

1. Automation: Automation is an important aspect of DevOps, and can be used to

automate many aspects of the hospital information system, including deployment,
testing, and monitoring. This can help ensure that the system is delivered quickly and
reliably.

2. Collaboration: DevOps emphasizes collaboration between development and

operations teams, which is important when building a complex system like a hospital
information system. Collaboration can help ensure that the system is designed and
built to meet the needs of all stakeholders, including doctors, nurses, and other
healthcare professionals.

3. Continuous Integration/Continuous Deployment: Continuous Integration/Continuous

Deployment (CI/CD) is an important part of DevOps, and can be used to ensure that
the hospital information system is tested and deployed quickly and reliably. This can
help ensure that the system is always up-to-date and that any bugs or issues are
addressed quickly.

4. Security: Security is a critical consideration when building a hospital information

system, as it contains sensitive patient information. DevOps can help ensure that the
system is secure by incorporating security testing and monitoring into the
development process.

5. Scalability: Hospital information systems need to be scalable to accommodate the

growing number of patients and healthcare providers. DevOps can help ensure that
the system is designed and built with scalability in mind, using technologies like
containers and microservices.

Using DevOps to build an integrated hospital information system can help ensure
that the system is delivered quickly, reliably, and securely, while meeting the needs of all
VELIBOR BOŽIĆ Research proposal

stakeholders. It can also help ensure that the system is scalable and able to adapt to
changing needs and requirements over time.

Advantages and disadvantages of DevOps approach

Advantages

1. Faster time to market: DevOps can help organizations to release software more
quickly and efficiently by automating many of the processes involved in software
development and deployment.

2. Improved collaboration: DevOps emphasizes collaboration and communication

between development and operations teams, which can help break down silos and
improve team cohesion.

3. Better quality software: By incorporating automated testing and continuous

integration/continuous deployment (CI/CD) pipelines, DevOps can help ensure that
software is tested thoroughly and released with fewer defects.

4. Improved reliability and stability: DevOps can help improve the reliability and
stability of software systems by automating many of the processes involved in
deployment, monitoring, and maintenance.

5. Increased agility and flexibility: DevOps can help organizations to respond more
quickly to changing business needs and market conditions by allowing them to
release software more quickly and efficiently.

Disadvantages

1. Steep learning curve: DevOps involves many new tools, technologies, and practices,
which can be challenging for organizations that are new to the approach.

2. Cultural resistance: DevOps requires a cultural shift in organizations, which can be

difficult to achieve. It requires a willingness to embrace change and to break down
silos between development and operations teams.

3. Complexity: DevOps can be complex, especially for organizations with large and
complex software systems. It requires careful planning and execution to ensure that
VELIBOR BOŽIĆ Research proposal

all aspects of the software development and deployment process are automated and
integrated.

4. Security risks: DevOps can increase security risks if not implemented properly. It
requires careful attention to security testing and monitoring to ensure that software
systems are secure and compliant with relevant regulations and standards.

5. Cost: Implementing DevOps can be expensive, especially for organizations that are
new to the approach. It requires investment in new tools, technologies, and training,
as well as changes to organizational structures and processes.

Risks in DevOps approach and mitigate the risks

There are several risks associated with DevOps approach, some of them are:

1. Security risks: DevOps involves continuous integration and deployment of code,

which can pose security risks if not properly managed. These risks can include data
breaches, cyber attacks, and vulnerabilities in software.

Mitigation: Security should be integrated into the DevOps process from the beginning. This
includes conducting regular security testing and vulnerability assessments, implementing
security controls such as firewalls and encryption, and establishing clear security policies and
procedures.

2. Cultural resistance: DevOps requires a cultural shift that can be difficult to achieve.
Resistance to change can lead to friction between teams and a lack of buy-in for
DevOps practices.

Mitigation: Communication and collaboration are critical to overcoming cultural resistance.

Encouraging open communication between teams, providing training and education on
DevOps practices, and involving teams in the process of implementing DevOps can help build
trust and reduce resistance.

3. Lack of standardization: DevOps can result in a lack of standardization across teams,

which can lead to inconsistencies in code quality, configuration management, and
deployment practices.
VELIBOR BOŽIĆ Research proposal

Mitigation: Establishing clear DevOps standards and best practices can help ensure
consistency across teams. This includes defining coding and deployment standards,
establishing clear documentation and communication practices, and implementing quality
control measures such as code reviews and automated testing.

4. Tool and technology risks: DevOps involves the use of a variety of tools and
technologies, which can pose risks such as compatibility issues, system failures, and
vendor lock-in.

Mitigation: Careful planning and evaluation of tools and technologies is essential to mitigate
these risks. Organizations should evaluate tools and technologies based on factors such as
ease of use, compatibility with existing systems, and vendor support. Implementing a
strategy for tool selection and management can help ensure that tools are used effectively
and efficiently.

5. Lack of scalability: DevOps can pose scalability risks if not properly managed. As
applications and systems grow, it can become increasingly difficult to manage and
maintain DevOps processes and practices.

Mitigation: Planning for scalability from the beginning is essential to mitigate this risk. This
includes implementing a scalable infrastructure that can support growth, establishing clear
scaling policies and procedures, and ensuring that teams are trained and equipped to
manage the scaling process effectively.

Conclusion

In conclusion, DevOps is a software development methodology that emphasizes

collaboration, automation, and continuous improvement to deliver high-quality software
quickly and efficiently. DevOps involves a cultural shift that emphasizes communication and
collaboration between development and operations teams, as well as the use of tools and
technologies to automate the software development and deployment process.

DevOps practices and tools can help organizations to reduce time to market, improve
software quality, and increase efficiency and productivity. However, there are also risks
associated with DevOps, including security risks, cultural resistance, lack of standardization,
tool and technology risks, and lack of scalability.
VELIBOR BOŽIĆ Research proposal

To mitigate these risks, organizations should implement clear DevOps policies and
procedures, establish standards and best practices, communicate and collaborate effectively
between teams, and carefully evaluate tools and technologies to ensure they meet
organizational needs. By embracing the DevOps methodology and implementing best
practices, organizations can improve the quality and efficiency of their software
development processes, leading to better outcomes for both the organization and its users.

Literature review

1. "The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security
in Technology Organizations" by Gene Kim, Jez Humble, Patrick Debois, and John
Willis (2016).

2. "Accelerate: The Science of Lean Software and DevOps: Building and Scaling High
Performing Technology Organizations" by Nicole Forsgren PhD, Jez Humble, and
Gene Kim (2018).

3. "Continuous Delivery: Reliable Software Releases through Build, Test, and

Deployment Automation" by Jez Humble and David Farley (2010).

4. "Site Reliability Engineering: How Google Runs Production Systems" edited by Betsy
Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy (2016).

5. "Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale"

by Jennifer Davis and Katherine Daniels (2016).

6. "The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win" by
Gene Kim, Kevin Behr, and George Spafford (2013).

7. "DevOps for Dummies" by Emily Freeman (2019).

8. "DevOps on the Microsoft Stack" by Wouter de Kort (2016).

9. "The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with
Containerized Microservices" by Viktor Farcic (2016).

10. "Continuous Testing: with Ruby, Rails, and JavaScript" by Ben Rady and Rod Coffin
(2011).
 VELIBOR BOŽIĆ Research proposal

11. "DevOps Automation Cookbook" by Michael Duffy (2015).

12. "Mastering Kubernetes: Master the art of container management with Kubernetes"
by Gigi Sayfan (2017).

13. "Continuous Delivery with Docker and Jenkins: Delivering software at scale" by Rafal
Leszko (2017).

14. "The DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT

Enterprise" by Sanjeev Sharma (2017).

15. "Jenkins 2: Up and Running: Evolve Your Deployment Pipeline for Next Generation
Automation" by Brent Laster (2018).

16. "DevOps for Networking" by Steven Armstrong and Scott Lowe (2019).

17. "Test-Driven Infrastructure with Chef: Bring Behavior-Driven Development to

Infrastructure as Code" by Stephen Nelson-Smith (2011).

18. "Infrastructure as Code: Managing Servers in the Cloud" by Kief Morris (2016).

19. "The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring
services inside Docker Swarm clusters" by Viktor Farcic (2017).

20. "Ansible: Up and Running: Automating Configuration Management and Deployment

the Easy Way" by Lorin Hochstein and René Moser (2020).

These references cover a wide range of topics related to DevOps, including principles,
practices, tools, automation, continuous delivery, containerization, and more. They provide
valuable insights and guidance for organizations looking to implement DevOps
methodologies and improve their software development and deployment processes.

View publication stats