UK Software DevelopmentGlossary
Browse 200 expert definitions covering UK software development technologies, regulations, methodologies, and business concepts.
Showing 24 of 200 glossary terms
Pair-programming
Pair Programming explained for UK software developers. Pair programming is a software development technique where two programmers work together at one workstation — one writes...
Disaster-recovery
Disaster Recovery explained for UK software developers. Disaster Recovery (DR) is the set of processes, policies, and tools that enable an organisation to recover its IT system...
Feature-flag
Feature Flag explained for UK software developers. A feature flag (also called a feature toggle or feature switch) is a technique that allows software behaviour to be chan...
Caching
Caching explained for UK software developers. Caching is the practice of storing copies of data in a fast-access storage location (the cache) so future requests for t...
Code-review
Code Review explained for UK software developers. A code review is the systematic examination of code by one or more developers (other than the original author) before it...
Technical-specification
Technical Specification explained for UK software developers. A technical specification (tech spec) is a document that describes how a software system will be built — covering: syste...
Product-backlog
Product Backlog explained. A Product Backlog is a prioritised list of everything the product team wants to build — user stories, bug fixe...
Api-key
API Key explained. An API key is a unique identifier used to authenticate a client making API calls. It is typically a long rando...
Deployment-pipeline
Deployment Pipeline explained. A deployment pipeline is the automated sequence of processes that takes code from a developer's laptop to prod...
Sql
SQL explained. SQL (Structured Query Language) is the standard language for interacting with relational databases. SQL allows...
Latency
Latency explained. Latency is the time delay between a request being made and the response being received. In software, API laten...
Ip-ownership
IP Ownership explained. Intellectual Property (IP) ownership in software refers to who legally owns the copyright, patents, and other ...
Uptime
Uptime explained. Uptime is the percentage of time a software system is operational and available to users. Common uptime target...
Continuous-delivery
Continuous Delivery explained. Continuous Delivery (CD) is a software development practice where code changes are automatically built, tested...
Incident-management
Incident Management explained. Incident Management is the process of identifying, responding to, and resolving incidents that affect a softwa...
Git
Git explained. Git is a distributed version control system that tracks changes to source code over time. Every developer has ...
Tdd
Test-Driven Development explained. Test-Driven Development (TDD) is a software development practice where tests are written before the production...
Api-versioning
API Versioning explained. API versioning is the practice of managing changes to an API by maintaining multiple versions simultaneously, ...
Technical-debt-interest
Technical Debt Interest explained. Technical debt "interest" is the ongoing cost of keeping technical debt unaddressed — analogous to interest pa...
Headless-architecture
Headless Architecture explained. Headless architecture separates the "head" (presentation layer — the user interface) from the "body" (backend ...
Devsecops
DevSecOps explained. DevSecOps is the practice of integrating security throughout the software development lifecycle — not just at ...
Blue-green-deployment
Blue-Green Deployment explained. Blue-green deployment is a release strategy that reduces downtime by running two identical production environm...
Soc2
SOC 2 explained. SOC 2 (System and Organisation Controls 2) is a voluntary compliance standard for service organisations that s...
Retrospective
Retrospective explained. A Sprint Retrospective (Retro) is a Scrum ceremony held at the end of each sprint where the development team r...