architecture three-part definition

·

Link:: https://medium.com/olzzio/from-architectural-decisions-to-design-decisions-f05f6d57032b

My three-part definition from 2009 is in line with those of the luminaries:

  1. Architectural decisions directly or indirectly determine the non-functional characteristics (or qualities) of a system (think -ilities or consult this post for examples).
  2. Each decision describes a concrete, architecturally significant design issue (problem) for which several potential solution options exist, and provides rationale for the decision outcome (the selection of the chosen solution option, that is), for instance by arguing whether and how the desired quality attributes will be achieved.
  3. Architectural decisions concern a software system as a whole, or one or more of the core components of such system (whatever the “core” is).
Какие у меня мысли по этому поводу в моменте?

Тут раскрывается только то, что такое Architecture Decision Record, при этом что такое архитектура сервиса не очень.

Какие открытые вопросы остались после обработки?

Является ли архитектура сборником таких решений?