Modifications to software applications after their distribution are referred to as maintenance. The aim of maintenance is to correct faults, increase performance or to improve other aspects of the software, as well as in some cases to adapt it to other operational conditions.

Cf. software maintenance on Wikipedia.

Management review

This refers to following review processes:

  • an analysis of project planning and development processes;
  • a systematic analytic evaluation of all stages of software acquisition, supply, development, maintenance and operation. This kind of review is carried out for management and aims to track progress made, budget discipline and project status. A management review often reviews the efficiency of management itself, too.


A metric is used to measure a certain criteria of a software application. They are produced using a static analysis; metrics is also the term for the method and scale used to carry out the measurements.

For further details, see software metrics on Wikipedia.


A defined point in time during a software development project at which a particular component, result or deliverable should be available. Milestones are, when successfully reached, often the point at which contractors invoice work to date.

Cf. Wikipedia on milestones.

Mock objects

These are dummy parts of software that are used to simulate actual program functions whilst testing single components (see component testing).

However, mock objects are not complete dummies inasmuch as they can be programmed to feed certain inputs ints to the component being tested.

Cf. Mock-Objekt on Wikipedia.


The moderator is title of the person who leads a review meeting; it also refers too the person in charge of an inspection.

Module testing

This is another term for component testing, also known as unit testing. Modular testing aims to verify single modules in software. Any change to the software as a whole should be followed by running the full range of module tests.


Also refered to as a monitoring tool, this is a software program that interacts with a program being tested and supervises, records and then analyses the way in which the software was executed during testing.

Multiple condition coverage

This is a part of white-box testing whereby all combinations of all single conditions in a given decision statement (i.e. a statement which is either true or false) are tested.

Cf. mulitple condition coverage on Wikipedia.