design-first-engineering

A design-first approach in software engineering means planning architecture and defining system capabilities before coding. It iteratively frames problems, identifies components, maps interactions, and establishes interface contracts to ensure clarity and reduce costly rework.

You plan system architecture by following a four-step design process: define system capabilities, identify components, map their interactions, and establish interface contracts. This iterative approach validates design with stakeholders before implementation begins.

You need a design document when planning new features, executing system re-designs, or conducting architecture reviews. It ensures early stakeholder validation and establishes clear interface contracts and component interactions before development starts.

Yes, this design process applies to system design, feature planning, and architecture discussions across both product and engineering teams. It emphasizes separation of concerns and iterative validation regardless of the specific project context.

The best way to define interface contracts is through an iterative four-step process. After framing capabilities and identifying components, you map interactions to establish clear contracts, ensuring separation of concerns and stakeholder alignment before coding.

Skipping architecture planning leads to rework because it bypasses problem framing, component identification, and interface contract validation. A design-first approach ensures separation of concerns and stakeholder alignment early, preventing costly changes during coding.