The Softwaremetrie concerns itself as subsection of the software technology with the measurement of software characteristics and the interpretation of these measurements.

A goal of the Softwaremetrie is to be able to transact it by objective and best automatically providable yardsticks different statements about a software unit.

The questions cover thereby a set of topic areas, which carry in different phases of the software development to to come and the answers to questions of different interrogators to supply are. In the following the most frequent interrogators with some typical questions are specified.

In order to be able to answer these questions, need one first as data source so-called Softwaremetriken. This Metriken supplies yardsticks to the examined software element. These can be used then supplemental by further numbers from the development process (necessary work times, error report, failure distribution, etc.), in order to supply answers to the questions begun to cut above.

The measurement of software characteristics such as quality (i.e. software quality) or complexity is very difficult. Since each Metrik can consider only few characteristics of the software, the danger that the software is going by developed exists, to affect the values seized by the Metrik into the desired direction about in order so "„the quality "“of the software to improve. If the Metrik considers for example the number of code lines ("“LINEs OF code"”), then a software developer - conscious or unconscious - could write its code in such a way that this consists of more code lines. If the number of found software faults has an influence on the Metrik, then it can lead to the fact that either many smaller nose-fixed into only one large are combined (or more badly still: certain of nose not to be repaired at all), which the amount of that nose-fixed reduces, or however that many small changes are published unnecessarily, in order to increase the amount of that nose-fixed artificially.

Critics of the Softwaremetrik therefore mean that any attempts are doomed to failure to define a Metrik for "„software quality "“or the like over a mathematical formula, since most Metriken fails, as soon as the software which can be evaluated becomes optimized on the set Metrik "„"“.

Related links

• Overview article Softwaremetrie at the University of Magdeburg

Articles in category "Softwaremetrie"

We found here 5 articles.

Related Websites

We found here 3 related websites.

• BASE Digital Collections - Bielefeld Academic Search Engine BASE ...
  ... (1) Prostatakarzinom, (1) Plasma physics and fusion, (1) Psychiatrie, (1) Softwareentwicklung / Produktivit


• Measurement Theory and Software Metrics
  Die Br


• WORKING PAPER
  Softwaremetrie: Grundlagen und Ziele. research report. Otto-von-. Guericke Universit