Nonfunctional requirements specify qualities the system must have (how it performs) rather than what it does (functional requirements). Availability is a classic nonfunctional requirement - it specifies the percentage of time the system must be operational (e.g., '99.9% uptime'). Options A, B, C, and E are incorrect: Requirements are broad specifications, defect density is a quality metric, Failure Modes are risk analysis outputs, and Specifications are general documents - none are nonfunctional requirements themselves.