volume_mute
Separating Functional and Non-Functional Requirements
publish date: 2026/06/05 21:07:12.053219 UTC
volume_mute
True or False: It is always straightforward to separate functional requirements from non-functional requirements in a requirements document, and they should always be kept in completely separate sections.
Correct Answer
False
Explanation
In practice it is difficult to separate functional and non-functional requirements. If they are stated separately, the relationships between them may be hard to understand. However, requirements that are clearly related to emergent system properties (performance, reliability) should be explicitly highlighted — for example by placing them in a separate section or distinguishing them in some way.
Reference
Software Engineering, Ian Sommerville, 9th edition