"ACRUMEN: What IS Software Quality, Anyway?"
summary
A concise, actionable definition called ACRUMEN claims software must be Appropriate, Correct, Robust, Usable, Maintainable, Efficient and fits on a business card as a checklist. It shows how to apply it with concrete practices: given–when–then tests for appropriateness, property-based testing and mutation testing to raise confidence, static analyzers and fuzzers for robustness, profilers and packet captures for efficiency, and regression test suites to enable safe, fast changes.
AI-written summary · about
chapters (11)
- 0:00Software quality intro
- 1:49Problems with quality definitions
- 4:38Introducing ACRUMEN
- 5:44ACRUMEN's six aspects
- 8:54Appropriateness deep dive
- 12:02Ensuring software correctness
- 13:46Achieving robustness
- 16:23Usability's critical role
- 19:15Maintainability and changes
- 21:20Efficiency and resources
- 23:08Conclusion
related talks
56mControlling Quality in Software Development
15mDefining Quality
52mNavigating Software Quality - From Chaos to Control
40mAmplifying Agile Quality Practices
06m“Quality-conscious Software Delivery”
40mReal Quality Assurance from an Agile and Lean Viewpoint
19mHow can we improve quality on a project?
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)