
The Quantity type is very useful in recording measurements in computer systems. It combines both the magnitude and units. It also includes appropriate arithmetical and comparative operations. In other words, Quantity is a "whole value" that the user interface can interpret and display (it has its own print operation). Using this concept, we can represent monetary values (or Money) as quantities, using the currency as the unit. With quantities, we can easily deal with multiple currencies, rather than being tied to one currency.
Examples:

As shown, we can use conversion ratio objects between units, and provide an operation called convertTo(Unit) which returns a new quantity in the desired unit.
Example: Conversion between inches and feet can be achieved by defining a conversion ratio from feet to inches with the number 12.
As is evident, this model can handle most but not
all kinds of conversion. Some conversions require more than a simple multiplication.
For monetary values, whose units are currencies, the conversion ratios
are not constant over time. This problem can be dealt with by having an
attribute that indicates the time of applicability of the ratio. Actually,
for conversions that change frequently over time, we can use Scenarios
(described later).

Here, the subtype Category Observation is of interest to us.
In the previous example, gender is an instance of Phenomenon Type,
male and female are instances of Category, and the Object Observed
is the person. So, an Observation, particularly, Category Observation,
has a Category which is the possible set of values that the Object Observed
may take, under this Observation. If we consider the banking domain, the
Object Observed could be the state of the market. An example of a phenomenon
type related to a Category Observation would be "people's conception of
risk", having values such as "High", "Medium", "Low", etc. For a 'Measurement',
phenomenon types are quantitative in nature, such as "interest rate", "height",
"weight", etc.