The art to define and test System Quality Attributes
summary
Defines a practical workflow: run 4–6 hour workshops with ~10–12 stakeholders to prioritize quality attributes, capture scenarios and score business value vs implementation complexity, then turn scenarios into measurable tests run in CI. Uses Sonar, Structure101, exported JIRA stats, DDA/tipdown analysis and chaos experiments (Chaos Monkey style on Kubernetes) to prove ROI. Gives concrete targets like 99.5% requests <150ms, a modifiability goal of feature ready in 2.5 days, and measured traffic of 500,000 req/min.
AI-written summary · about
chapters (7)
- 0:00System quality attributes intro
- 14:40Defining measurable scenarios
- 16:48Prioritizing quality attributes
- 21:51Quality workshops with stakeholders
- 34:04Measuring quality attributes
- 49:07Reliability testing with chaos
- 59:32Summary
related talks
35mQuantitative measures for software Architecture quality evaluation
47mQualityStorming: Collaborative Modelling for Quality Requirements
58mTesting Software Architecture
44mAI Architecture Thinking: From Idea to Impact
01h 15mHow to measure your architecture
51mTesting Software Architecture
54mValue Streams, Quality Engineering And You
01h 07mBuilt In Quality Reach Beyond the Team