BABOK Requirements Life Cycle Management 3

Question 1

What is the purpose of a 'requirements repository' in BABOK?

Accepted Answer

To provide a centralized, organized location for maintaining and accessing all requirements and related information

Answer

To store project financial records

Answer

To house completed code modules

Answer

To track team meeting notes

Question 2

When should a business analyst recommend placing requirements under formal change control?

Accepted Answer

When requirements have been baselined and agreed upon by stakeholders

Answer

Only after the project is complete

Answer

Before any requirements have been elicited

Answer

When the project manager requests it

Question 3

Which of the following is an output of the 'Maintain Requirements' task?

Accepted Answer

Requirements (maintained)

Answer

Elicitation results

Answer

Requirements management plan

Answer

Stakeholder engagement plan

Question 4

How does requirements traceability support solution testing?

Accepted Answer

It allows testers to identify which test cases correspond to which requirements, ensuring full coverage

Answer

It defines the testing budget

Answer

It assigns testers to requirements

Answer

It replaces test plans

Question 5

What does 'reuse' of requirements refer to in BABOK?

Accepted Answer

Leveraging existing requirements artifacts across multiple projects or components when applicable

Answer

Copying requirements from other projects without modification

Answer

Using the same requirements for every project

Answer

Reusing old documentation to save time

Question 6

In BABOK, which task specifically focuses on ensuring requirements reflect the current needs of stakeholders and remain valid over time?

Accepted Answer

Maintain Requirements

Answer

Trace Requirements

Answer

Prioritize Requirements

Answer

Approve Requirements