liveBook · Manning

S.O.S. test

As explained in Grokking Software Architecture

A decision-screening heuristic that checks whether a choice is significant, onerous to change, or surprising.

Use the S.O.S. test to decide whether a choice deserves an Architecture Decision Record (ADR), rather than a code comment. section 2.7

Ask whether the choice is:

  • Significant: Does it change how other parts of the system work? section 2.7
  • Onerous to change: Would reversing it later be a nightmare? section 2.7
  • Surprising: Would a future developer wonder why it was done this way? section 2.7

If any answer is yes, write an ADR. Choosing Redis over a database table may qualify; choosing a for loop over map() is a local detail better handled with a code comment. section 2.7

How Grokking Software Architecture covers it

How deep it goes
Defines three screening questions and a yes-based decision rule without detailing ADR contents.
Examples
Contrasts choosing Redis over a database table with choosing a for loop over map().
What you can do after
Evaluate choices and decide whether to document them in an ADR.
How it connects
Connects architectural significance with Architecture Decision Records and code comments.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.