Which one of the following is not the part of requirement management?

Answer: Page Traceability Table is not part of requirement management.

Key idea: requirement management focuses on tracking, controlling, and tracing requirements throughout the project lifecycle.

• Features Traceability Table maps features to their originating requirements to ensure coverage and to track changes.

• Dependency Traceability Table records dependencies among requirements, components, or features so impact analysis is possible when things change.

• Interface Traceability Table links interface requirements to components and tests to ensure interfaces meet specified requirements.

Why Page Traceability Table is not the correct part of requirement management:

• The term 'Page Traceability Table' is not a standard requirement management artifact. It suggests mapping UI pages rather than tracing requirements across development, design, and test artifacts.

• Mapping pages to requirements can be useful in some UX or content-heavy projects, but it is not a common, formal traceability matrix used to manage requirements across the project lifecycle.

Conclusion: Features Traceability Table, Dependency Traceability Table, and Interface Traceability Table are typical requirement-management traceability artifacts. Page Traceability Table is not a standard requirement management artifact, so it is the correct answer.