A software (quality) metrik is a function, which illustrates a software unit in one numerical value. This computed value is interpretable as those rate of admission of a quality characteristic of the software unit. (IEEE standard 1061)

A Metrik is a yardstick for a characteristic (or a quality criterion) of software. It can be represented a functional connection or be derived also from a check list.

The interpretation of the data of a Softwaremetrik is task of the discipline of the Softwaremetrie.

Use

• Evaluation of:
  1. Development phases and
  2. Phase results
  3. Technologies

Sight

1. Management
   • Costs of the software development (offer, cost minimizing)
   • Productivity increase (processes, experience curve)
   • Risks (market position, Time2Market)
   • Certifying (marketing)
2. Developer
   • Legibility (maintenance, re-use)
   • Efficiency and effectiveness
   • Confidence (remaining error, MTBF, test)
3. Customer
   • Estimations (budget loyalty, date loyalty)
   • Quality (reliability, correctness)
   • Return on Investment (maintenance, expandability)

Classification

1. Process Metrik
   • Resources expenditure (coworker, time, costs)
   • Error
   • Communication expenditure
2. Product Metrik
   • Extent (LOC, re-use, procedures,"…)
   • Complexity
   • Legibility (style)
   • (modularity, connection, coupling,"…)
   • Product quality (test results, test cover,"…)

Control criteria

• Objectivity
  • no subjective influences of the measurement
• Reliability
  • when repetition same results
• Standardisation
  • Result of measurement scale and comparability scale
• Comparability
  • Measure with other masses in relation settable
• Economics
  • minimum costs
• Usefulness
  • Fulfilment of practical needs
• Validity
  • of results of measurement on characteristic closable (with difficulty)

Methods/Metriken

Common procedures e.g. are:

• the Function POINT procedure for the expenditure estimation in the analysis phase
• the McCabe Metrik for implementation estimation in the design phase
• the Halstead Metrik for implementation estimation in the design phase

Proceed

1. Phase and role model specify
2. Goals determine
3. Metrik mask define
4. Measuring plan set up
5. Data collect
6. Data validate
7. Data analyze and interpret
8. Data secure and visualize

Literature

• George E. Thaller: Software Metriken begin - evaluate - measure. Publishing house technology, 2000, ISBN 3341012605

Related links

• Software complexity
• Software quality management

Articles in category "Softwaremetrik"

We found here 5 articles.

Related Websites

We found here 3 related websites.

• The IT Metrics and Productivity Institute - Better IT Management ...
  Mr. Bundschuh is also president of the Deutschsprachige Anwendergruppe f


• The IT Metrics and Productivity Institute - Better IT Management ...
  Mr. Bundschuh is also president of the Deutschsprachige Anwendergruppe fr Softwaremetrik und Aufwandschtzung (DASMA). He lectures for various organizations ...


• The IT Metrics and Productivity Institute - Better IT Management ...
  Mr. Bundschuh is also president of the Deutschsprachige Anwendergruppe f