Blog: How to stop nasty defects slipping through?
Software is everywhere!
The huge demand for software means that there is also a huge demand for software developers. Since this resource pool of software developers is not unlimited, it is tempting to lower the bar and allow less skilled and experienced software developers to make the software of tomorrow. All this comes with a threat for the software world: the risk that the quality of delivered software is too low. Software bugs might have huge financial consequences or human lives might even be at stake.
Fortunately, there are ways to safeguard software quality. One of them is the introduction of software quality gates. At various stages of the software development cycle there are automated checks that will stop the software development conveyor belt if the quality appears to be too low.
Great, but what stages need to have such quality gates and what needs to be measured? We like to show how software quality gates can be introduced in an organization to make sure that the quality of software stays at a high level.
The overview to the right might seem like a lot of effort.
Fortunately, TIOBE has paved the way for the first 5 steps. It has defined a set of metrics and tools to measure software quality based on the ISO 25010 standard. On top of that we have also defined a qualification model called the TIOBE Quality Indicator (TQI) to come to an indication of software quality. The results range from level A (very good quality) to level F (very bad quality).
In the Quality Gate Leaflet we will focus on the last 2 steps: defining quality targets and enable quality gates.