The Requirements Traceability Matrix (RTM) is a powerful tool used in both predictive (Waterfall) and adaptive (Agile) methodologies. Its primary function is to provide a link between the requirements and the deliverables, ensuring that the " Business Value " promised is the " Business Value " delivered.

Why Choice C is correct:

Identifying Missing Requirements: By tracing a high-level business need down to a specific technical requirement and then to a test case, the project manager can see if any " links " are broken. If a business need has no corresponding requirement or test case, it is a missing requirement.

Identifying Superfluous Requirements: Conversely, if there is a technical feature or a piece of code that cannot be traced back to an approved business objective, it is considered superfluous (also known as " Gold Plating " ). This helps the project manager remove unnecessary work that does not add value.

Methodology Neutral: Whether you are using a Product Backlog in Agile or a formal Requirements Document in Waterfall, the logic of " tracing " from origin to execution remains the same to ensure scope integrity.

Analysis of other options:

A (Creation of a solid business case): The Business Case is a pre-project document that justifies the investment. The RTM is created after the project has started and the business case has already been approved.

B (Investigation of the viability of a new product): This is typically done during the Feasibility Study or the Initiating Phase. The RTM is an execution and monitoring tool used once the requirements have already been defined to some degree.

D (Evaluation of solution and system performance): While the RTM tracks if a requirement was met, it doesn ' t typically measure how well the system performs (e.g., speed, stress testing, or latency). Those metrics are found in Quality Control Reports or Performance Testing documentation.

Key Concept: The Project Management Institute (PMI) emphasizes that the Requirements Traceability Matrix (Choice C) is the ultimate " audit trail " for project scope. It ensures that the project team builds exactly what was requested—preventing both omissions (missing requirements) and unauthorized additions (superfluous requirements)—thereby maintaining the integrity of the Scope Baseline.