liveBook · Manning

Design pattern

As explained in Effective Behavior-Driven Development

A reusable description of a solution to a recurring software design problem.

A design pattern is a general, reusable solution to a recurring challenge in a particular context. It captures an approach that has worked more than once, so a team can draw on it when a similar challenge arises. section 12.2

A solution is not automatically reusable everywhere: some approaches are specific to one project. A pattern names both the challenge and the context where its solution may apply. section 12.2

A useful pattern description can:

  • Explain the problem it is intended to solve and where it may apply. section 12.2
  • Describe how to apply the solution and note trade-offs. section 12.2
  • Link to code examples and use a descriptive name that supports design discussions. section 12.2

How Effective Behavior-Driven Development covers it

How deep it goes
Defines patterns and outlines documentation contents, but does not prescribe a single format.
Examples
Uses a team discussion about capturing automation-POC findings in a project wiki as its illustration.
What you can do after
Apply it by recording a solution’s problem, applicability, usage, trade-offs, and code examples.
How it connects
Connects design patterns with scenario automation, test automation, and project wikis.

Also explained in

Compare how 9 books explain design pattern →

Related concepts

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