What type of document helps in tracking changes to requirements?

What type of document helps in tracking changes to requirements?

• A. Change Request Form
• B. Requirements Traceability Matrix
• C. Stakeholder Analysis Report
• D. Project Plan

Answer: (B)

The Requirements Traceability Matrix is the correct answer because it is specifically designed to track changes to requirements throughout the project lifecycle. This matrix provides a comprehensive overview of how requirements align with business goals, project deliverables, and key stakeholders. Each requirement can be linked to corresponding project elements such as test cases, design specifications, and implementation details. By maintaining a traceability matrix, a business analyst can easily identify the impact of changes to requirements, monitor their status, and ensure all stakeholders are aware of how these changes affect the overall project. This documentation is essential for managing the evolving nature of requirements and ensuring that all modifications are accounted for and appropriately addressed within the project scope. The other options serve different purposes. A Change Request Form is used to formally propose changes, but it does not provide a complete overview of how requirements connect to each other or to the project's goals. A Stakeholder Analysis Report focuses on identifying and understanding stakeholders, while a Project Plan outlines the overall project scope, objectives, timelines, and resources but does not track specific requirement changes.

The Requirements Traceability Matrix is the correct answer because it is specifically designed to track changes to requirements throughout the project lifecycle. This matrix provides a comprehensive overview of how requirements align with business goals, project deliverables, and key stakeholders. Each requirement can be linked to corresponding project elements such as test cases, design specifications, and implementation details.

By maintaining a traceability matrix, a business analyst can easily identify the impact of changes to requirements, monitor their status, and ensure all stakeholders are aware of how these changes affect the overall project. This documentation is essential for managing the evolving nature of requirements and ensuring that all modifications are accounted for and appropriately addressed within the project scope.

The other options serve different purposes. A Change Request Form is used to formally propose changes, but it does not provide a complete overview of how requirements connect to each other or to the project's goals. A Stakeholder Analysis Report focuses on identifying and understanding stakeholders, while a Project Plan outlines the overall project scope, objectives, timelines, and resources but does not track specific requirement changes.