[BoxFour]

Software architecture is an ever-evolving aspect, especially in large companies where multiple teams may concurrently modify it without coordination.

As a simple example: Predicting the downstream impacts of updating a module from c++11 to c++20 can often be a tedious trial-and-error process. Having prior knowledge of potential effects is a valuable starting point.

Though this leans towards dependency management rather than pure architecture, in practice, the lines can blur.

[chrisjj]

It is only dependency management.