Chapter 5 On Nonfunctional Requirements

DOI: 10.1201/9781003129509-5

Motivation to Consider NFRs Earlier in Development

Systems are characterized both by their functional behavior (what the system does) and by their nonfunctional behavior (how the system behaves concerning some observable attributes like reliability, reusability, and maintainability).

In the software/system marketplace, in which functionally equivalent products compete for the same customer, nonfunctional requirements (NFRs) become more important in distinguishing between the competing products. However, in practice, NFRs may receive little attention relative to functional requirements (FRs) (Weber and Wesbrot 2003). This is mainly true because of the nature of NFRs which ...

Get Requirements Engineering for Software and Systems, 4th Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.