liveBook · Manning

Architecture advice process

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

A decision-making process in which architectural decisions are advised on by people beyond the group that initially makes them.

The architecture advice process moves architectural decisions beyond the group that initially makes them. Communicate each decision to people who were absent but may be affected or possess relevant expertise. section 11.2.1

Use the process to widen participation without involving everyone continuously:

  • Identify stakeholders who may be affected or whose expertise matters, including people discovered during collaborative modeling. section 11.2.1
  • Check whether those stakeholders consent to proceeding without them, treating their absence as an ongoing sensemaking question. section 11.2.1
  • Record options in an architectural decision record and share it asynchronously through email or messaging when appropriate. section 11.2.1
  • Invite further involvement through an architecture advice process, an Architecture Advisory Forum, or a dedicated meeting. section 11.2.1

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

How deep it goes
Defines a stakeholder-communication heuristic and outlines consent checks, ADR updates, asynchronous sharing, and additional participation routes.
Examples
Uses ADRs, email or messaging updates, collaborative modeling sessions, Architecture Advisory Forums, and newly scheduled meetings.
What it assumes
Assumes stakeholder identification and collaborative modeling practices while emphasizing that new stakeholders can emerge during sessions.
What you can do after
Apply it by finding affected or expert stakeholders, checking consent, recording options, and selecting an appropriate involvement channel.
How it connects
Connects architectural decision records, collaborative modeling, stakeholder identification, buy-in, and Architecture Advisory Forums.

Related concepts

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.