Skip to content
LEF LEF Docs
GitHubLinkedIn

Delivery aspect

The delivery aspect describes how changes become production: acceptance, releases, handover, and lane-based risk control.

What this aspect answers

Section titled “What this aspect answers”
  • How do we move changes safely through DTAP lanes?
  • How do we keep releases repeatable and auditable?
  • How do we avoid “it works on my machine” drift?

Organization

Section titled “Organization”
  • Clear roles for approval, release coordination, and deployment execution.

Process

Section titled “Process”
  • Acceptance approach and release cadence.
  • Change handling and configuration management.

Technique

Section titled “Technique”
  • Delivery automation (CI/CD), migrations, and rollback strategy.
  • Deployment-by-lane (DTAP) as a risk management tool.

Lane model (concept)

Section titled “Lane model (concept)”

In LEF docs:

  • A software system is typically an Environment.
  • A lane (in DTAP) is an occurrence of that system; the construct is stable across lanes.
  • Shared infra services (VPN / firewall / DNS / proxies / storage) enable many systems across lanes.

In C4, deployment diagrams show how instances of software systems and containers map onto deployment nodes inside a deployment environment. For LEF, the lane is the deployment environment for an environment system.

Operationalization (where to go next)

Section titled “Operationalization (where to go next)”