[[Property:title|Scopes]]
[[Property:weight|8]]
[[Property:uuid|303fb469-9f2b-d7cc-55e7-d657fb87b8fe]]
Every metric has a scope:

{{definition|Scope of a metric|<br/>
The '''scope''' of a metric is defined as follows: <br/>
- For a raw product metric, the type of product over which the metric is counted, such as: a feature, a class, a group, an archive built for a given system to make it possible to compare systems. <br/>
- For a raw process metric, the type of process on which the metric is measured, such as analysis, documentation, entire project etc. <br/>
- For a derived metric (recursively), the scope of the raw metric from which it is derived. <br/>
- For a composite metric (recursively), the largest of the scopes of all its constituent metrics, where cluster is "larger than" class and so on. }}



This notion also applies to measures:

{{definition|Scope of a measure|<br/>
The '''scope''' of a measure is defined as follows: <br/>
- For an elementary measure (the application of an elementary metric, raw or derived), the set of products or processes to which the associated metric has been applied to yield the measure. <br/>
- For a composite measure, the union of (recursively) the scopes of its constituent measures. }}

For both metrics and measures, the notion of scope will help us compare our quantitative assessments to some already on record. For example you may compare the value of a certain metric, such as number of invariant clauses in each class, with the values that have been archived for your project, for a reference project such as the EiffelBase library, for the previous projects of your company, or for a global set of previous projects maintained at some central location. You may also, with appropriate permissions, update such a shared archive with the values from your own measurements.

In the environment, the notion of scope will be handled by defining an input domain. If the input domain contains a duplicated elements, the computation is done twice on the duplicated elements.