ACRUMEN: What IS Software Quality Anyway?!
summary
A simple, portable definition of software quality claims software should be Appropriate, Correct, Robust, Usable, Maintainable, Efficient (the N stands for Nothing) and prioritizes appropriateness above all. It shows concrete ways to prove each aspect: stakeholder-facing given–when–then tests and regression suites for correctness, property based testing and mutation testing for edge cases, fuzzers and static analyzers for robustness, profilers and performance tests for efficiency, plus usability checks and maintainability via automated tests.
AI-written summary · about
chapters (11)
- 0:00The search for a definition
- 4:10Introducing Acrumen
- 5:06Breaking down the aspects
- 7:13Applying the framework
- 9:27Ensuring appropriateness
- 13:03Focusing on correctness
- 16:19Achieving robustness
- 20:18Improving usability
- 26:18Prioritizing maintainability
- 28:13Efficient resource usage
- 32:29Conclusion and resources
related talks
37mACRUMEN: The Six Key Aspects of Software Quality
30mWorking Software Is the Primary Measure of Progress
01h 01mThe art to define and test System Quality Attributes
35mQuantitative measures for software Architecture quality evaluation
44mMaking It Count: Quality is NOT an Option
01h 07mBuilt In Quality Reach Beyond the Team
58m4 Key Trends Towards Better Software Architecture
51mTesting Software Architecture