Grammar-oriented programming¶

A software-development approach that makes a domain grammar the primary executable model for a domain-specific language and its processing architecture.

Version: v1 · 2026-09-08 · History
Domain-specific #: 4763
Origin domain: software language engineering
Subdomain: software language engineering
Aliases: Grammar-oriented Object Design, GOOD

Core Idea¶

The label is not uniformly standardized, and a grammar alone is insufficient: domain semantics, generated or interpreted execution and a maintenance relationship between language and application must be explicit. Domain concepts are encoded as productions and semantic actions or transformations, a parser turns business expressions into structured models and the grammar-driven runtime or generated components execute those models. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application¶

Grammar-oriented programming belongs to software language engineering and is useful where the analyst can specify the typed software language engineering carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the business or problem domain, domain-specific vocabulary and grammar, concrete and abstract syntax, parser or compiler, semantic actions or transformations, generated or interpreted runtime behavior, reconfiguration mechanism, validation and error handling and relationship to host architecture are explicit.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the business or problem domain, domain-specific vocabulary and grammar, concrete and abstract syntax, parser or compiler, semantic actions or transformations, generated or interpreted runtime behavior, reconfiguration mechanism, validation and error handling and relationship to host architecture are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Grammar-oriented programming. Grammar-oriented programming compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed software language engineering carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the business or problem domain, domain-specific vocabulary and grammar, concrete and abstract syntax, parser or compiler, semantic actions or transformations, generated or interpreted runtime behavior, reconfiguration mechanism, validation and error handling and relationship to host architecture are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of software language engineering because they reuse the typed software language engineering carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Domain concepts are encoded as productions and semantic actions or transformations, a parser turns business expressions into structured models and the grammar-driven runtime or generated components execute those models., and type the carrier, state every parameter and convention in the definition, test that the business or problem domain, domain-specific vocabulary and grammar, concrete and abstract syntax, parser or compiler, semantic actions or transformations, generated or interpreted runtime behavior, reconfiguration mechanism, validation and error handling and relationship to host architecture are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Grammar-oriented programming Domain-specific

Parents (1) — more general patterns this builds on

Grammar-oriented programming is a kind of Representation Prime

The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

Grammar-oriented programming → Representation → Abstraction

Neighborhood in Abstraction Space¶

Grammar-oriented programming sits in a crowded region of the domain-specific corpus (28^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Software Modeling & Program Architecture (45 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08