fault-tolerance, backward compatibility, extensibility, reliability, maintainability, availability, security, usability, and other such -ilities. Stakeholder concerns often translate into requirements on these quality attributes, which are variously called non-functional requirements, extra-functional requirements, behavioral requirements, or quality attribute requirements.
I'm just listening, rewinding and taking note. 10+years and they take me back to school. True Masters.
Decided against the Webinar for security reasons as it required Zoom so really appreciate you sharing the talk here
Software Architect has to be hands on, Period.
Tradeoff is not only in software architecture but in whole universe.
The book and this video are same. Both are amazing!
I've enjoyed this video as much as the book! such an amazing job!
Very useful, I loved this talk. Thank you for sharing.
Just bought the book. Keen!
These folks make my head spin
Timespan axioms is an axiom which is validated/invalidated over time strictly to software discipline.
What you say “illities”, do you mean “abilities” like “observability” or “reliability”?
fault-tolerance, backward compatibility, extensibility, reliability, maintainability, availability, security, usability, and other such -ilities. Stakeholder concerns often translate into requirements on these quality attributes, which are variously called non-functional requirements, extra-functional requirements, behavioral requirements, or quality attribute requirements.
-ilities remind me of -omics in biology, like genomics, proteomics
Software architecture is WHY，while Software design is HOW
this has tradeoffs