How do you measure the quality metrics


What do you need metrics for?

Requirements play a key role in successful system development, as errors in requirements and requirement documents can have a considerable impact on the success of your project. Quality metrics are used to minimize this risk associated with incorrect requirements.

In order to be able to control your project, you need to know the actual quality of the requirements (or that of the requirements documents) and the associated risks and optimization potential.

On the basis of a metric, you can assess the current quality of requirements with regard to a specific quality characteristic. Furthermore, you can use the calculated measured values ​​to make predictions about project key data such as B. derive the potential risk for the further course of the project or the effort still to be invested.

A long-term use of metrics also offers the possibility of planning, monitoring and evaluating measures for quality improvement or the introduction of methods. The repeated measurement of the requirements allows you to consider changes in quality within the specification documents over a longer period of time. This allows you to identify specific problems and initiate countermeasures such as training.

However, you should keep in mind that a measurement alone does not improve the quality. Measuring requirements therefore involves investing a certain amount of effort before appropriate measures can be initiated. Since you need to justify this effort to management, you should measure requirements as efficiently as possible. In the course of this blog series, we will explain how this can be achieved, for example using measurement templates or similar aids.

What quality metrics are there?

First, let's talk about quality metrics in general. Quality metrics can be divided into two categories:

  • Content-based quality metrics: With the help of these metrics, statements can be made about quality aspects of requirements and requirement documents with regard to the linguistic formulation as well as the existing information content.
  • Management-oriented quality metrics: Metrics in this group deal with quality aspects that relate to the further development and further processing of requirements and requirement documents.

Furthermore, we differentiate according to the test object, which is measured:

  • Individual requirement level: Quality metrics of this class can be used for each individual requirement without knowledge of context information.
  • Overall specification level: Quality metrics of these classes can only be used with knowledge and availability of the overall specification.

We will be presenting a selection of the most important quality metrics to you over the next few weeks. Furthermore, we will go into the process of measuring specification documents in more detail and explain what you should consider when measuring. We will give you some useful tips from practice.

If you have any questions about quality metrics or would like to let us know what experiences you have already had with metrics, use the comment function or send us an email at [email protected]

This entry was posted in Technical and tagged Metrics, Testing, Quality Assurance by SOPHIST. Permanent link to the entry.