What category does Specification-Driven Design belong to?

Specification-Driven Design belongs to the "Software Development" category in personal knowledge management and productivity.

What are the key topics related to Specification-Driven Design?

Key topics related to Specification-Driven Design include: software-development, design, architecture, specifications, methodologies.

Specification-Driven Design

Q: What are alternative names for Specification-Driven Design?

Specification-Driven Design is also known as: Spec-Driven Development, Specification-Driven Development, Design by Specification.

An approach to software development where a formal specification document drives the design, implementation, and validation of the system.

Also known as: Spec-Driven Development, Specification-Driven Development, Design by Specification

Category: Software Development

Tags: software-development, design, architecture, specifications, methodologies

Explanation

Specification-driven design is an approach to software development where a formal specification document serves as the single source of truth for system behavior. The specification defines what the system should do before any code is written, and all implementation, testing, and validation derive from this specification.

## Core Principles

- **Spec first, code second**: Define behavior explicitly before implementing it. The spec answers 'what' and 'why'; the code answers 'how'
- **Single source of truth**: The specification is the authoritative description of system behavior. Code, tests, and documentation all derive from it
- **Verifiable contracts**: Specifications define clear, testable contracts between components, services, or systems
- **Living documents**: Specifications evolve with the system but always stay ahead of the implementation

## Common Forms

- **API specifications** (OpenAPI/Swagger): Define endpoints, request/response schemas, and behavior. Generate client libraries, server stubs, and documentation automatically
- **Type specifications**: Type systems and schemas (TypeScript types, JSON Schema, Protocol Buffers) that enforce structure at compile time or runtime
- **Behavioral specifications** (BDD): Given-When-Then scenarios that describe expected behavior in natural language, executed as automated tests
- **Formal methods**: Mathematical specifications (TLA+, Alloy, Z notation) for critical systems where correctness must be proven

## Benefits

- **Alignment**: Teams agree on behavior before writing code, preventing costly misunderstandings
- **Code generation**: Specifications can generate boilerplate, reducing manual work and inconsistency
- **Contract testing**: Specs become executable tests that verify implementation matches intent
- **Documentation**: The spec is the documentation — always up-to-date by definition
- **AI-assisted development**: Specifications provide clear, structured context for AI coding assistants, enabling more accurate code generation

Related Concepts

← Back to all concepts