Skip to main content
Software development glossary · UK reference

The software development glossary for the terms at audit. Fifty of them. Plain English.

Fifty terms UK founders, CTOs, and procurement teams hear at audit, in plain English. ADR, AML, CREST, DSPT, FCA, ISO 27001, MERN, OWASP, PCI DSS, PSD2, RAG, RLS, SOC 2, SRA, STRIDE, WCAG, and more. Save the link, send it to your team, refer back when the security questionnaire lands.

50terms defined
PlainEnglish, no jargon
UKregulator-aware
24hto add a term you need
(Why this page exists)

A 60-page security questionnaire landed. Half the acronyms were new to you.

You don’t need to memorise these. You need to find the one you’re staring at, read a plain-English line, and get back to the answer. That’s the whole job of this glossary. Grouped by topic so you can scan to the right cluster fast.

0

0

0

How this glossary is grouped

Seven groups.
Open the one your questionnaire is asking about.

You’re probably here for two or three terms, not all fifty. Open the group that matches what landed in your inbox, then drop into the accordion below for the definitions.

The UK regulators and frameworks that decide whether your software can ship into a regulated market: FCA, ICO, SRA, ICAEW, KCSIE, DCB0129, DSPT, IR35, MLR 2017, RTW, RTI, FPS.

Jump to the definitions

The certifications and questionnaires an enterprise buyer sends before they sign: SOC 2, ISO 27001, OWASP, CREST, STRIDE, CAIQ, SIG-Lite, Vanta + Drata, IDOR.

Jump to the definitions

Everything that touches money and the people moving it: PCI DSS, SAQ-A, PSD2, AML, SAR, GMV, BFCM.

Jump to the definitions

How your customers’ data is handled, transferred, and recovered: DPA, DSAR, SCCs, SCIM, SSO, RPO + RTO, TCF v2.2.

Jump to the definitions

The terms in the code review, the ADR, and the bug report: ADR, MERN, MVCC, RLS, N+1 query, EOL, SLA + SLO, SLO error budget.

Jump to the definitions

The newer additions everyone asks about: RAG (the LLM retrieval pattern), WCAG 2.2 AA (the accessibility floor), and SaaS itself.

Jump to the definitions

The terms that come up when you raise or sell: NDA, M&A, SDS, plus the TDS your proptech buyers ask about.

Jump to the definitions
Software development glossary · Group A

Regulators & compliance. Who decides if you can ship.

The UK bodies and statutes that gate regulated software. Open any term.

Financial Conduct Authority. The UK financial services regulator. Fintech-essential. If your product touches lending, payments, or investments, the FCA decides whether you operate.

Information Commissioner’s Office. The UK data protection regulator. The body you report a breach to, and the one that fines you if you handle personal data badly.

Solicitors Regulation Authority. The UK law firm regulator. Legaltech-essential. If you build for solicitors, your software has to fit how the SRA expects client money and case data to be handled.

Institute of Chartered Accountants in England and Wales. The accountancy regulator. It comes up when you build software that touches statutory accounts or audit workflows.

Keeping Children Safe in Education. UK statutory guidance for schools. Edtech-essential. If your product is used by under-18s in a UK school, you build to this from day one.

NHS Clinical Risk Management standard. Required for clinical software in the NHS supply chain. If your software informs a clinical decision, you need a clinical safety case under DCB0129.

Data Security and Protection Toolkit. NHS England’s data security framework. Healthtech-essential. Annual self-assessment that lets you handle NHS data and connect to NHS systems.

UK off-payroll working rules. Determines a contractor’s tax status. HR-tech-essential, and a question funded founders ask before hiring a studio: get IR35 wrong and you inherit a tax problem.

Money Laundering Regulations 2017. The UK’s anti-money-laundering statute. It’s the law behind the AML controls you build into any product that moves money.

Right to Work. The UK Home Office check for an employee’s work eligibility. HR-tech products often have to build the RTW check into onboarding.

Real Time Information. HMRC’s PAYE reporting regime. Payroll software submits an FPS each pay run. HR-tech and payroll products are built around it.

Full Payment Submission. The HMRC payroll report sent on or before each payday under RTI. If you build payroll, the FPS is the submission your engineering has to get right every time.

Software development glossary · Group B

Security & trust standards. What your enterprise buyer asks first.

The certifications, frameworks, and questionnaires that gate a B2B sale.

AICPA standard for service-organisation security. Type I means controls are in place. Type II means they’ve been audited over time. The report enterprise buyers ask for before they sign. Empyreal carries Type II, achieved December 2025.

International information security management standard. Certification-grade. It’s the framework behind a documented information security management system (ISMS). We wire the ISMS for clients who need to certify.

Open Web Application Security Project. The industry-standard web security framework. The OWASP Top 10 is the list of the most common web vulnerabilities, and it’s covered on every audit we run.

Council of Registered Ethical Security Testers. The UK penetration-testing certification standard. When a buyer asks for a CREST-grade pen test, this is what they mean. Empyreal carries a CREST-aligned methodology.

A threat-modelling framework. The letters stand for Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege. We use it to map the threats to your system before we write the auth.

Consensus Assessments Initiative Questionnaire. The cloud-security procurement questionnaire enterprise buyers send. It’s long. We carry one pre-filled so your sale doesn’t stall on it.

Standardised Information Gathering questionnaire, the lighter version. A procurement security assessment your buyer’s security team sends. Like the CAIQ, we keep one pre-filled.

SOC 2 and ISO 27001 evidence-automation platforms. They watch your systems and collect the audit evidence continuously instead of in a panic the week before. We wire them on day one for clients heading for certification.

Insecure Direct Object Reference. An authorisation flaw where you can read another user’s data just by changing an ID in the URL. Common in vibe-coded apps. It’s one of the first things we test for in a security audit.

Software development glossary · Group C

Payments & financial crime. Everything that touches money.

The terms behind a checkout, a settlement, and the controls around them.

Payment Card Industry Data Security Standard. The rules for handling card data. Scope minimisation via Stripe Elements (so card data never touches your servers) is our default, because it keeps you out of the heavy compliance burden.

PCI DSS Self-Assessment Questionnaire A. The lowest PCI scope you can have. Achievable when card data is handled entirely by a provider like Stripe Elements or Adyen Components. The goal for most checkouts we build.

EU Payment Services Directive 2. It mandates Strong Customer Authentication (SCA) on payments. We build a 3DS2 plus exemption strategy into every checkout so genuine customers aren’t blocked while the rules are still met.

Anti-Money Laundering. Governed in the UK by MLR 2017 and across the EU by 6AMLD. In software it means sanctions screening, PEP screening, a customer due-diligence (CDD) lifecycle, and SAR-ready exports.

Suspicious Activity Report. The AML report filed to the National Crime Agency when a transaction looks suspect. If you build fintech, your software has to make raising and exporting a SAR clean and auditable.

Gross Merchandise Value. The total transaction value running through a marketplace or ecommerce platform. The headline number a marketplace founder lives by, and the one your reporting has to get exactly right.

Black Friday and Cyber Monday. Ecommerce’s biggest traffic peak, often a large slice of the year’s sales in a single weekend. We load-test to 8x baseline before BFCM so the checkout holds when it matters most.

Software development glossary · Group D

Data, privacy & resilience. How your customers’ data is handled.

The contracts, identity standards, and recovery maths behind safe data.

Data Processing Agreement. The UK and EU GDPR-aware contract between the data controller (you) and the processor (us, or any vendor). We keep one on file so this doesn’t hold up a build.

Data Subject Access Request. A right under UK GDPR for a person to ask for all the data you hold on them. The response SLA is 30 days, so we build the export tool into the schema rather than scrambling later.

Standard Contractual Clauses. The EU Commission’s template for legally transferring personal data across borders. Module 2 (controller to processor) is the one we keep on file for cross-border work.

System for Cross-domain Identity Management. The enterprise standard for SSO and automatic user provisioning, so when an admin adds or removes someone in their identity provider, your app keeps up. WorkOS or Auth0 wire it.

Single Sign-On. One login across systems, built on SAML or OIDC. It’s a hard requirement in enterprise procurement, so if you sell B2B you’ll need it. WorkOS or Auth0 wire it.

Recovery Point Objective and Recovery Time Objective. The disaster-recovery maths: how much data you can afford to lose (RPO), and how long you can afford to be down (RTO). The two numbers that size your backups and failover.

IAB Transparency and Consent Framework v2.2. The cookie and consent standard publishers and ad-ops teams need to handle user consent legally across the ad ecosystem.

Software development glossary · Group E

Engineering & the stack. The terms in the code review.

What an ADR, a bug report, and an SLA actually mean in practice.

Architecture Decision Record. One page per significant decision: the context, the options, the choice, and the consequences. It’s how the next engineer inherits the why, not just the what. We write at least six per engagement.

MongoDB, Express, React, and Node. A full-stack JavaScript combination. It’s been Empyreal’s default stack since 2019, partly because the UK hiring pool for it is deep, so you can always find your next engineer.

Multiversion Concurrency Control. PostgreSQL’s concurrency model. In plain terms, it means a long-running report can read the data without blocking the writes happening at the same time.

Row-Level Security. A PostgreSQL and Supabase feature that pins each row to a tenant, so one customer can never read another’s data even if a query goes wrong. We test it with pgTAP before it ships.

A database anti-pattern: one query returns N rows, then N more queries fire, one per row. It’s the quiet reason a page that was fast at ten users crawls at ten thousand. We catch these at audit.

End of life. The point where a framework or language version stops getting security updates. PHP 7.4 hit EOL in November 2022. CodeIgniter 3 reaches EOL in October 2025. Running past EOL is a security liability.

Service Level Agreement and Service Level Objective. The uptime and response-time commitments you make to customers (SLA) and the internal targets you hold yourself to (SLO). We publish ours rather than hiding them.

An SRE practice: the budget of downtime you’re allowed within your SLO. When you burn through it, deploys pause until reliability recovers. Discipline plus maths, so you ship features without quietly breaking uptime.

Software development glossary · Group F

AI & accessibility. The newer terms everyone asks about.

The acronyms that turned up in the last two years of briefs.

Retrieval Augmented Generation. An LLM pattern that combines retrieval (for example pgvector plus BM25 search) with generation, so the model answers from your documents rather than guessing. We build it with citation gates so every answer can be traced back to a source.

Web Content Accessibility Guidelines 2.2, Level AA. The accessibility standard that’s a UK and EU public-sector requirement. We test it with axe plus a manual pass, because automated tools alone miss the things a real user hits.

Software as a Service. Subscription software delivered over the web rather than installed. It’s the model behind most of what we build. Empyreal has shipped 84 SaaS builds since 2019.

Software development glossary · Group G

Deals & diligence. The terms when you raise or sell.

What comes up the week before a fundraise or an acquisition call.

Non-Disclosure Agreement. Mutual, so it protects both sides before you share a brief. We countersign one inside 30 minutes during UK working hours, so it never becomes the reason a project stalls.

Mergers and Acquisitions. When you sell, the acquirer’s CTO walks your codebase on a diligence call. We ship engineering that survives that call: the ADRs, the tests, and the architecture are there to read.

Status Determination Statement. The UK IR35 document that records a contractor’s employment status for tax. HR-tech products often need to generate and store one for each engagement.

Tenancy Deposit Scheme. The UK letting industry’s deposit-protection requirement. Proptech-essential. If you build for lettings, your software has to handle deposit protection within the legal window.

The studio behind the glossary

Numbers,
not adjectives. The receipts.

We didn’t write these definitions from a textbook. They’re the terms we’ve answered for real, on real audits, since 2019. Here’s the studio behind them, in figures that survive Series B diligence.

Scale

£540M+
GMV through code we shipped
320M+
API calls a year, 2025

Trust

0
Customer-data breaches, seven years
SOC 2
Type II, achieved Dec 2025

People

28 mo
Median client retainer tenure
96%
Engineer retention, same seniors
Software development glossary — dashboard / app screen
In context

What it looks like shipped.

software development glossary, in context — the dashboards, flows and components your team actually ships, reviews and maintains.

Fifty terms covered · need one we missed?

Email the term. We add it inside the week.

If a definition you needed isn’t on this software development glossary, tell us the term and where you hit it. Mohit replies inside 24 hours, and the term goes in inside the week.

Write to mohit@empyrealinfotech.com Replies in 24h50 terms definedUK regulator-aware
If you’re here because a build is on the table
  1. < 24h

    A personal reply.

    Yes, no, or the deciding question. Straight to your inbox.

  2. Pricing

    Real numbers, in the reply.

    Audit at £8K fixed. Builds from £18K. The figure in the email, not behind a call.

  3. Always

    30-day walk-away.

    Both ways. IP assigns on commit. You keep everything.