UK Software DevelopmentGlossary
Browse 200 expert definitions covering UK software development technologies, regulations, methodologies, and business concepts.
Showing 24 of 200 glossary terms
Minimum-viable-product
Minimum Viable Product explained. A Minimum Viable Product (MVP) is the smallest version of a product that allows you to validate your most impo...
Refactoring
Refactoring explained. Refactoring is the process of restructuring existing code without changing its external behaviour. The goal is...
Version-control
Version Control explained. Version control (also called source control) is the practice of tracking and managing changes to source code o...
Penetration-test
Penetration Test explained. A penetration test (pen test) is a simulated cyber attack against a software system, network, or application —...
Acid
ACID explained. ACID is an acronym describing four properties that guarantee database transaction reliability: Atomicity (all ...
Monorepo
Monorepo explained. A monorepo (monolithic repository) is a version control strategy where multiple projects or packages are store...
Sprint-review
Sprint Review explained. A Sprint Review (also called a sprint demo) is a Scrum ceremony held at the end of each sprint where the devel...
Api-contract
API Contract explained. An API contract is a formal specification of how an API behaves — defining: available endpoints, request forma...
Microservice
Microservice explained. A microservice is a small, independently deployable software service that is responsible for a specific busine...
Acceptance-testing
Acceptance Testing explained. Acceptance testing is the process of verifying that a software system meets business requirements and is ready...
Boilerplate
Boilerplate explained. Boilerplate (in software) refers to sections of code that are repeated across many parts of a codebase with li...
Mock-testing
Mock (Testing) explained. A mock (or mock object) is a simulated object in software testing that mimics the behaviour of a real dependen...
Code-smell
Code Smell explained. A code smell is a surface indication in code that suggests there may be a deeper problem with the code's desig...
Continuous-deployment
Continuous Deployment explained. Continuous Deployment (CD) is a software development practice where every code change that passes the automate...
Rate-of-change
Rate of Change explained. Rate of change (in software) refers to how frequently a software system is updated — including new features, b...
Software-licence
Software Licence explained. A software licence is a legal agreement that defines how software may be used, distributed, and modified. For ...
Non-functional-requirements
Non-Functional Requirements explained. Non-functional requirements (NFRs) describe how a system should perform, rather than what it should do. They i...
Dependency
Dependency explained. A software dependency is a library, package, or module that a software project relies on to function. Modern s...
Technical-interview
Technical Interview explained. A technical interview is a job interview format used for software engineering roles that evaluates a candidate...
Sprint-backlog
Sprint Backlog explained. A Sprint Backlog is the subset of items from the Product Backlog that the development team has committed to co...
Definition-of-done
Definition of Done explained. The Definition of Done (DoD) is a shared agreement within a Scrum team that defines what criteria must be met ...
Kanban
Kanban explained. Kanban is an agile methodology that manages work by visualising the workflow on a board divided into columns (...
Burn-down-chart
Burn-Down Chart explained. A burn-down chart is a visual representation of work remaining versus time available in a sprint or project. T...
Story-points
Story Points explained. Story points are a unit of measure for expressing the overall effort required to fully implement a user story....