volume_mute

Tracking Functional–NFR Relationships

publish date: 2026/06/06 23:08:30.544782 UTC

volume_mute

How might an engineer responsible for drawing up a system requirements specification keep track of the relationships between functional and non-functional requirements? Which approach is most effective?

Omit non-functional requirements from the specification since they are harder to manage

Completely separate functional and non-functional requirements into different documents with no cross-references

Ask developers to memorize the relationships between requirements

Use a requirements traceability matrix that explicitly links each non-functional requirement to the functional requirements it affects, generates, or constrains

Correct Answer

Use a requirements traceability matrix that explicitly links each non-functional requirement to the functional requirements it affects, generates, or constrains

Explanation

A requirements traceability matrix is the most effective way to track relationships between functional and non-functional requirements. It makes visible which NFRs affect which functional requirements (and vice versa), making it easier to assess the impact of changes and ensure all NFRs are properly addressed in the functional specification.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Applied Requirements Engineering - Exercises