Continuous quality assessment and improvement

Software quality assessment and improvement has to be considered during the whole development process and throughout the software system's lifecycle. Taking and interpreting measures is necessary and stakeholders have to derive required actions from it regularily.


continuous quality assessment, quality improvement, quality review

“Quality cannot be tested in, it has to be built-in"

common understanding of required quality and how to measure it

generic: high level abstract best practice, metalevel category (e.g. manage architectures)

Application domain:
Medicine/Healthcare, Education (Technology enhanced learning), Data science (analysis & visualisation), Industry (Production), Mobility, Energy, Software engineering

Main phase:
Generic: Requirements/Exploration, Generic: Design/Plan, Data Science: Preparation/Integration, Data Science: Modeling/Training/Evaluation, Development: Implementation/Code/Build, Development: Testing, Operations: Deployment/Release, Operations: Maintenance/Monitor

Related literature:
W. Lewis, Software Testing and Continuous Quality Improvement, 3rd Edition, 3rd edition. Auerbach Publications, 2017.

In which projects do/did you use this practice?
SQI, AutoTest (most propably all)

Software Tester, Software Engineer, Project Manager, Researcher

>10 years of experiences
Software Competence Center Hagenberg

1. How do ​you rate the potential benefit for your projects? 5
2. How often are you using that practice? 4
3. What is the effort to introduce the practice in your project upfront? 2
4. What is the effort to apply the best practice in your project daily basis? 3

Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)

You are running an old browser version. We recommend updating your browser to its latest version.

More info