Time behaviour asks how long the product takes to respond and to process. A measure compares observed times with the times the requirements state, under recorded conditions. The number is the easy part; the conditions are the measure. Load, data volume, hardware, network and concurrent users all move the result, and the draft has no target values, so the requirement has to supply them. The family covers both response time, which a user feels, and processing time, which a batch or a job consumes. A measure that reports an average without a distribution hides the tail, and the tail is what users complain about.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.