Concept Modelling

Define and relate key business concepts to create shared vocabulary before detailed analysis.

Definition

Concept Modelling is a technique used to identify, define, and relate the key business concepts within a domain. It focuses on what things mean to the business rather than how systems store or process them. A concept model visually represents business concepts, their definitions, and the relationships between them — providing a shared foundation that reduces ambiguity before requirements are elaborated.

Inputs

  • Business objectives and domain documentation
  • Outputs from stakeholder interviews and workshops
  • Existing glossaries, data dictionaries, or prior models
  • Requirements under analysis that surface domain terminology

Outputs

  • A concept model diagram with business concepts as nodes and relationships as connections
  • Agreed business definitions for each concept
  • Inputs to data models, requirements, and system design
  • Improved stakeholder alignment on terminology and meaning

When to Use

  • Working in complex or unfamiliar domains where terminology is inconsistent or overloaded
  • Multiple systems share common data and a shared vocabulary is required
  • Starting large or enterprise-level initiatives before detailed requirements
  • When stakeholder misalignment on basic terms is slowing elicitation

When Not to Use

  • When the domain is simple and well understood by all stakeholders
  • When terminology is already standardized, stable, and agreed
  • When detailed data models already exist and have been validated

See this technique in action with a free RequirementsHub workspace.

Start Free Workspace →