About architectural characteristics from the book "Fundamentals of Software Architecture"

Yesterday. participated At a book club meeting {between parentheses } where we discussed the fourth chapter of the book Foundations of Software Architecture, in which Mark Richards and Neal Ford talked about characteristics that usually fall on the shoulders of people who play the role of architects, since business itself does not often remember about this type of requirements. In the book Fundamentals of Software Architecture, the authors of the book from place to place in the quarry and talk about what are usually called non-functional requirements. (nonfunctional requirements)But they don't like the term because it's self-deprecating. Next, they remember the attributes of quality. (quality attributes)But they are not satisfied with this option because of the bias towards post-factual verification. And they stop at the term architectural characteristics. (architecture characteristics)It is good enough to describe the critical moments that affect architecture. For the sake of completeness, I have added a story about Architecture Tradeoff Analysis Method to this article. (ATAM) book Architecture for Busy Developers, as well as short stories about the search for compromises (tradeoff analysis) book Building Secure and Reliable Systems.

P.S. The recording will be publicly available through 2 I’ll share it with you in this channel too.

#Architecture #Software #SoftwareArchitecture