Development and Operations (DevOps)

Go up to Terms and Definitions

Development and Operations (DevOps) integrates software-development and operational activities into a coordinated lifecycle.

DevOps reduces organizational and procedural separation between the people, processes, and technologies that develop, build, test, release, deploy, operate, and maintain software and systems.

DevOps commonly uses:

• Shared repositories
• Automated build processes
• Automated testing
• Continuous Integration
• Continuous Delivery
• Continuous Deployment
• Configuration management
• Infrastructure as Code
• Git-based workflows
• GitOps practices
• Automated deployment
• Operational monitoring
• Rapid feedback
• Repeatable workflows

Within Crucible documentation, DevOps provides the broader lifecycle context for integrating repository changes, automated builds, deployments, validation activities, and operational feedback.

DevOps does not by itself establish the security practices required throughout that lifecycle. Development, Security, and Operations (DevSecOps) explicitly integrates security into DevOps activities.

coordinated approach that integrates software-development and operational activities, processes, and responsibilities throughout the software or system lifecycle

Adapted from:

• National Institute of Standards and Technology Special Publication 800-204A
• National Institute of Standards and Technology Special Publication 800-218
• National Institute of Standards and Technology Cybersecurity Practice Guide 1800-44

The term DevOps combines Development and Operations.

DevOps is an organizational and engineering approach rather than a particular tool, product, deployment platform, or CI/CD implementation.

Automation commonly enables DevOps practices, but automation alone does not establish DevOps. DevOps also requires coordination between development and operations and feedback across lifecycle activities.

DevOps differs from Development, Security, and Operations (DevSecOps). DevSecOps integrates security practices and responsibilities throughout the DevOps lifecycle.

A development team commits a configuration change to a Git repository. An automated pipeline builds the affected Artifact, performs tests, deploys it to a target environment, validates the deployment, and provides the resulting status to development and operations personnel.