Model vs. Modal vs. Module

So, you come from a non-tech background and you are a bit frustrated that the techies like to use similar sounding words? Let’s quickly learn what these three terms mean, in software engineering context.

This article is part of my ELI5 (Explain Like I’m 5) series, where I try to explain complex tech and product concepts simply.

Term	ELI5 meaning	Simple example
MODULE	A self-contained piece of software/code	The “Payments” part of an app
MODAL	A UI window that appears on top of the current screen	“Are you sure you want to delete this?” popup
MODEL	A representation of something: data or behavior	A User object containing name, email, ID

The easiest way to remember them:

• module = code organization
• modal = UI
• model = representation/data

Module

A module is essentially a chunk of a larger software system that has a particular responsibility.

Imagine an online banking app. It might have:

Banking App = Accounts module + Payments module + Cards module + Profile module

Let’s look at one of those modules: Payments. The Payments module might contain everything necessary for handling payments: payment-related code, business rules, APIs, etc.

The exact meaning of “module” varies depending on the architecture and programming language. Sometimes it’s literally a technical unit supported by the language (module, package, library, etc.); sometimes engineers use it more loosely to mean “this relatively independent section of our system.”

From the workplace: when a developer says “the bug is in the authentication module,” they roughly mean the problem is somewhere in the chunk of the system responsible for authentication.

---

Modal

A modal is specifically a UI concept. It’s a window/dialog that appears on top of the interface and requires your attention before you continue interacting with the underlying screen.

For example, if you try to delete your account on a social media platform, you will typically see something like this:

“Delete your account? This cannot be undone.”
[Cancel]  [Delete]

That’s a modal. It temporarily puts the underlying interface “on hold.” You generally have to deal with it before continuing with any other action.

From the workplace: when a QA engineer writes in a ticket “the confirmation modal doesn’t close after clicking Cancel,” they’re talking about that visible UI component specifically.

---

Model

This one is broader and can mean slightly different things depending on context, but fundamentally: a model is a representation of something.

Suppose your application has users. A user in real life has hundreds of characteristics, but the software might only care about a few:

Field	Value
id	8472
name	Noelle
email	noelle@example.com
accountStatus	ACTIVE

That’s your (very simple) User model. The actual human being obviously has many more characteristics, but this model is the software’s useful representation of that person.

Other examples: Payment model, Transaction model, Product model, Order model, etc. An Order model, for instance, might just track id, customer, items, totalPrice, status, and createdAt.

“Model” gets additional meanings in specific contexts — database/data models, domain models, MVC models, machine-learning models, etc. — but the underlying idea of representation connects them.

Oh, by the way — ever wondered why fashion models are called models? Find out here.

Consolidating all this with a simple example

Let’s imagine a banking app:

• Payments MODULE — the section of the software responsible for handling payments.
• Payment MODEL — the representation of a single payment: amount, currency, recipient, status.
• Confirmation MODAL — the popup shown when the user attempts a payment: “Send €50?” [Cancel]  [Send]

The module contains functionality, the model represents something, and the modal is something the user sees and interacts with.