liveBook · Manning

Accountability

As explained in Grokking Software Architecture

Architectural accountability is responsibility for making and owning system-wide architectural decisions.

Architectural accountability means making and owning final decisions that shape a system as a whole. It is the destination in the Three A’s: awareness of architecture and alignment of daily coding decisions come first. section 1.1 section 1.10

Accountability includes decisions such as:

  • Choosing the database. section 1.1
  • Approving the architecture and signing off on system boundaries. section 1.1

How Grokking Software Architecture covers it

How deep it goes
Defines the responsibility and names example decisions, while distinguishing it from responsibilities expected of developers without that authority.
Examples
Names choosing a database, approving architecture, and signing off on system boundaries.
What you can do after
Understand which system-wide decisions accountability entails and how it differs from awareness and alignment.
How it connects
Distinguishes architectural accountability from architectural awareness and architectural alignment.

Also explained in

Compare how 17 books explain accountability →

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.