- Published
- 8 October 2026
- Last reviewed
- 8 October 2026
How to use this glossary
Use this reference when reviewing a small software change or discussing a cloud service. Tool implementations differ. Examples explain concepts and do not instruct readers to modify a production system.
Browse the alphabetical term index below. Select a term to jump to its definition, example and common mistake. Use the return link after each entry to browse again. You can also use your browser’s Find command to locate a word on this page. Definitions are original RDE plain-language explanations. All examples are fictional teaching scenarios.
Term index
12 terms, listed alphabetically.
- API
- Branch
- Cloud computing
- Commit
- Continuous delivery
- Continuous deployment
- Continuous integration (CI)
- Deployment
- DevOps
- Monitoring
- Rollback
- Test case
Definitions and practical examples
API
Meaning: An interface through which software components request information or operations from one another.
Example: A booking service requests course availability from another system through an API.
Common mistake to avoid: Document permissions, inputs and failure behaviour; an interface is not unrestricted access.
Branch
Meaning: A separate line of work within a version-controlled repository.
Example: A developer makes a small form change on a branch before requesting review.
Common mistake to avoid: A branch does not automatically isolate every external system or shared database.
Cloud computing
Meaning: On-demand access to shared computing resources delivered as a service.
Example: A provider uses hosted storage rather than maintaining its own storage hardware.
Common mistake to avoid: Service responsibilities still need agreement; cloud hosting does not remove customer obligations.
Commit
Meaning: A recorded set of changes in a version-control history.
Example: A developer commits one reviewed fix with a message explaining its purpose.
Common mistake to avoid: Committing work does not mean that it has been tested, merged or deployed.
Continuous delivery
Meaning: A practice that keeps tested changes ready for release when authorised.
Example: A pipeline prepares a release candidate that waits for a production approval.
Common mistake to avoid: It does not necessarily mean every passing change is released automatically.
Continuous deployment
Meaning: Automatic release of qualifying changes to production through a delivery process.
Example: A passing change moves to the live service without a separate manual release decision.
Common mistake to avoid: Automation still needs safeguards, monitoring and an appropriate recovery approach.
Continuous integration (CI)
Meaning: Frequently integrating changes and checking the combined result, commonly with automated builds and tests.
Example: A proposed change triggers build and test checks before integration.
Common mistake to avoid: A green pipeline establishes only what its checks actually cover.
Deployment
Meaning: Making a software version available in a target environment.
Example: An authorised release installs a new form version in the live service.
Common mistake to avoid: Distinguish staging from production and deployment from user acceptance.
DevOps
Meaning: Practices supporting collaboration and feedback between software development and operational work.
Example: Developers and support staff agree release checks, monitoring and incident feedback together.
Common mistake to avoid: Buying an automation tool alone does not create effective DevOps practice.
Monitoring
Meaning: Collecting and reviewing signals about the behaviour of a running system.
Example: A team watches error rates after deploying a change.
Common mistake to avoid: Choose meaningful signals and an owner who can respond to problems.
Rollback
Meaning: Returning to an earlier state or version as a recovery action.
Example: A failed release is replaced by the previously working application version.
Common mistake to avoid: Data changes may not reverse safely; plan recovery before assuming rollback is simple.
Test case
Meaning: A defined check with conditions, actions and an expected result.
Example: A tester submits a valid enquiry and checks that one confirmation is produced.
Common mistake to avoid: Record expected results before execution so that success is not judged retrospectively.
A distinction worth keeping clear
Continuous integration checks changes together frequently. Continuous delivery keeps changes ready for release. Continuous deployment automatically releases qualifying changes. These terms describe different practices; an organisation can use one without using all three.
Practise using the terms
A branch passes automated tests and is merged. A release waits for approval before reaching the live service. Identify the branch, continuous integration and deployment boundary. Does this scenario prove continuous deployment? Write your answer in your own notes before reading the explanation. No answer is submitted or stored by this page.
Suggested answer and explanation
The branch holds the separate line of work. The automated checks and frequent integration support continuous integration. The approved release to the live service is deployment. A manual approval before production means this example does not demonstrate automatic continuous deployment.
Sources and scope
The sources below support the terminology and relevant context. The definitions, examples, cautions and practice tasks on this page are original RDE teaching material, not verbatim extracts or a replacement for an official standard or certification syllabus. Reviewed 8 October 2026. Author: Jefferson Otonbara Imgbi.
Cover image: AI-generated illustrative scene created specifically for this resource.