volume_mute

NFR Metrics — Matching Properties to Measures

publish date: 2026/06/05 21:07:10.200628 UTC

volume_mute

Match each system property to the correct metric used to measure it for non-functional requirements specification.

To complete the line match

  1. Click on an item in the first group
  2. Click on the match in the second group

To delete a match, double click on a line

Property

Speed
Size
Ease of Use
Reliability
Robustness
Portability

Measure

Percentage of target-dependent statements; Number of target systems
Processed transactions/second; User/event response time; Screen refresh time
Mbytes; Number of ROM chips
Time to restart after failure; Percentage of events causing failure
Mean time to failure; Probability of unavailability; Rate of failure occurrence
Training time; Number of help frames

Correct Answer

(1) Speed,Processed transactions/second; User/event response time; Screen refresh time
(2) Size,Mbytes; Number of ROM chips
(3) Ease of Use,Training time; Number of help frames
(4) Reliability,Mean time to failure; Probability of unavailability; Rate of failure occurrence
(5) Robustness,Time to restart after failure; Percentage of events causing failure
(6) Portability,Percentage of target-dependent statements; Number of target systems

Explanation

These are the standard metrics for specifying non-functional system properties quantitatively. Speed is measured by transaction throughput and response time. Size by memory. Ease of use by training time. Reliability by mean time to failure or unavailability probability. Robustness by recovery time. Portability by proportion of platform-specific code.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears