liveBook · Manning

Technical approach

As explained in Spec-Driven Development

The planned way a feature or change fits into an existing architecture and is implemented under its technical constraints.

A technical approach states how a feature fits the existing architecture: identify affected components, integration points, and security, performance, or compliance constraints, then record the decisions that shape implementation. section 2.2.1

Treat it as the How, informed by previously captured business context. Once the approach and acceptance criteria are explicit, work can be broken into tasks with definitions of done tied to both. section 2.2.1

Figure 2.4 Overview of the Design phase in SDD.

The design phase scopes the conversation to technical details and establishes decisions for implementation. section 2.2.1

How Spec-Driven Development covers it

How deep it goes
Specifies affected components, integration points, and constraints, then records decisions; leaves execution breakdown to the task phase.
Examples
Records affected components, integration points, and security, performance, or compliance constraints as design decisions.
What it assumes
Builds on business context and acceptance criteria established before the design conversation.
What you can do after
Apply it by recording architectural fit, affected components, integration points, and constraints before decomposing implementation work.
How it connects
Connects architecture, security, performance, compliance, acceptance criteria, and task breakdown within spec-driven development.

Also explained in

Compare how 2 books explain technical approach →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.