liveBook · Manning

ADR canvas

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A visual template for recording the title, status, context, decision, and consequences of an architectural decision.

An ADR canvas visually records an architectural decision through its title, status, context, decision, and consequences. Teams adapt the format and keep it easy to revise and access. section 11.1.2

Use the canvas to make a decision’s history and current state legible:

  • Title identifies the decision and can include a reference number. section 11.1.2
  • Status tracks discussion and revision, commonly moving from Proposed to Accepted or Superseded; teams may add Rejected. section 11.1.2
  • Supersede an older ADR with a new record when new information changes the design, rather than silently rewriting history. section 11.1.2

BigScreen’s Anytime, Anywhere decision

BigScreen used an ADR canvas in Miro to document redesigning the BBoM into clear boundaries. The record included the architecture and a Pros-Cons-and-Fixes list, and its decision status was Accepted with an acceptance date. section 11.1.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines five core fields and a revisable status lifecycle while leaving format and team-specific statuses adaptable.
Examples
Uses BigScreen’s BBoM redesign, the Anytime, Anywhere campaign, Miro, and a Pros-Cons-and-Fixes list.
What you can do after
Apply it to document, revisit, and link architectural decisions as designs and evidence change.
How it connects
Connects architectural decisions with design documentation, decision status, design uncertainty, and reevaluation.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.