Concept Modelling

Concept Modelling is the practice of identifying and defining the core business concepts and making sure their meanings are clearly understood and consistently used across an organization. It focuses on what things mean in the business, rather than how they are stored, processed, or implemented in systems. The purpose is to create shared understanding before any technical design begins.

The main goal of Concept Modelling is to establish a common vocabulary. In many organizations, the same word can mean different things to different teams. Concept Modelling removes this confusion by clearly defining key terms and agreeing on their meanings. When everyone uses the same language, communication improves and misunderstandings are reduced.

This modelling approach captures the essence of business concepts such as Customer, Loan, Product, or Approval Decision. It also shows how these concepts relate to one another at a semantic level. Importantly, Concept Modelling does not include technical details such as attributes, data types, tables, or system logic. It stays intentionally simple and focused on meaning. Because of this, concept models often become the foundation for later artefacts such as ontologies, information models, and data models.

A simple everyday example helps explain this idea. In a school, people may talk about a “student,” a “course,” and an “exam.” Concept Modelling defines what each of these terms means and how they relate. For example, a student enrols in a course, and a course has exams. At this stage, no one discusses student IDs, exam scores, or databases. The focus is purely on understanding the concepts and their relationships.

In a loan-based business, Concept Modelling identifies concepts such as Customer, Loan, Application, Approval Decision, and Repayment. These concepts are connected using simple, meaningful relationships. A customer applies for a loan. A loan results in an approval decision. A loan has a repayment schedule. These statements describe the business reality without introducing system-specific or technical detail.

Concept Modelling is equally important for analytics and reporting. Analytical terms and measures are built on top of these same concepts. For example, a loan approval rate is defined using the concepts of approved loans and total applications. A delinquent loan is defined as a loan with missed repayments. By grounding analytics in shared concepts, reports and key performance indicators remain consistent and trustworthy.

The nature of Concept Modelling is high-level and semantic. It is independent of technology and platforms, and it is designed to be understandable by both business and technical audiences. Because it focuses on meaning rather than implementation, it plays a crucial role in aligning business discussions with later system and data designs.

In summary, Concept Modelling establishes a shared understanding of what the business is talking about. It clarifies the meaning of core concepts before any decisions are made about processes, systems, or data structures. This makes it a critical bridge between understanding how the business runs and designing models that support that understanding in information systems and analytics.

Comparison

This table shows the progression:

• Enterprise Data Modelling = what data exists across the organization
• Conceptual/Logical Architecture = how systems and data fit together
• Concept Modelling = what the core terms actually mean