Domain concept

As explained in BDD in Action, Second Edition

A business domain is the area of organizational activity, knowledge, and processes that a software solution addresses.

A domain concept represents a meaningful part of organizational activity, such as a flight, flight schedule, or booking. A business system stores related information and enforces rules governing how external actors may use it. section 15.1

Effective delivery treats interfaces as routes into business logic, not as the primary subject of acceptance testing. The goal is to verify user-relevant behavior: for example, preventing travelers from booking nonexistent flights or dates in the past. section 15.1

Work with domain concepts by:

• Discovering business goals and user needs progressively instead of assuming that early requirements are complete and stable. section 1.2.3
• Connecting acceptance tests to business rules and supported use cases, while using web, mobile, or programmatic interfaces as interaction mechanisms. section 15.1

Figure 1.4 At the start of a project, there are many unknowns. You reduce these unknowns as the project progresses, but not in a linear or very predictable way.

Use the figure to frame domain understanding as a growing body of knowledge: projects begin with many unknowns, and learning reduces them unevenly over time. section 1.2.3

How BDD in Action, Second Edition covers it

How deep it goes

Connects domain concepts to business rules, external actors, interfaces, and evolving project knowledge without detailing implementation.

Examples

Uses flights, flight schedules, bookings, travelers, past-date bookings, and nonexistent flights as concrete domain examples.

What you can do after

Evaluate whether features and tests reflect business rules rather than merely exercising external interfaces.

How it connects

Connects business rules, use cases, external interfaces, acceptance testing, BDD, and requirements uncertainty.

liveBookmanning.com

Read BDD in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureA domain concept is a meaningful concept representing business knowledge within a domain or subdomain.

Compare how 2 books explain domain concept →

Related concepts

• api namingused by · API naming is the practice of assigning identifiers that communicate an API element's purpose and distinguish it from others.
• resourceincludes · An API resource is a conceptual entity or target exposed through an interface and addressable for access or manipulation.
• subdomainpart of · A subdomain is a bounded subdivision or subordinate namespace within a broader domain, such as a business area or a domain-name hierarchy.
• domainpart of · A domain is a subject area or problem context with relevant concepts, rules, activities, and terminology that software represents or supports.
• automation solutionused by · An automation solution is a supporting system that integrates automated tests, execution frameworks, libraries, environments, and glue code to verify another system’s behavior.

This explainer was generated by Manning's knowledge graph from the text of BDD in Action, Second Edition. The section links point to the parts of the book it draws on.