A stakeholder would like to add requirements to an IT project which is in flight. The project manager wants to revisit the traceability repository prior to committing to the addition of any new reques

Question

Options

• ACreating test plans and test cases
• BApproving requirement relationships
• CDeveloping documentation for technical support
• DSupporting change and scope management

• B
  5% (1)
• C
  5% (1)
• D
  90% (19)

Explanation

This is because the traceability repository is a tool that helps the BA to track the relationships and dependencies among the requirements, the solution components, and the stakeholders. By using the traceability repository, the BA can assess the impact of any changes or additions to the requirements, and manage the scope of the project accordingly. Creating test plans and test cases (A) is not the main purpose of the traceability repository, although it can be used to verify the test coverage and quality of the solution. Approving requirement relationships (B) is not a valid activity, as the requirement relationships are established and documented by the BA, not approved. Developing documentation for technical support ?is not related to the traceability repository, as it is a post- implementation activity.

No community discussion yet for this question.