In requirements management, what is change control?

Change control is a critical aspect of requirements management in business analysis. It ensures that changes to requirements are systematically evaluated, approved, and implemented without negatively impacting the project. Key Considerations: Change Control Definition: Change control is a formal process used to manage modifications to requirements, ensuring that changes are necessary, feasible, and aligned with project goals. Version Numbering: While version numbering is part of documentation management, it is not the primary purpose of change control. Preventing Changes: Change control does not prevent changes but ensures they are managed appropriately. Tracing Requirements: Tracing requirements involves tracking their origin and impact, which is separate from managing changes. Evaluation of Each Option:
A . A process to control version numbering: Version numbering is a documentation practice, not the purpose of change control. Conclusion: This is not correct .
B . A process to manage changes to requirements: This accurately describes change control as a structured approach to handling modifications to requirements. Conclusion: This is correct .
C . A process to ensure that changes cannot be made: Change control does not block changes but ensures they are managed effectively. Conclusion: This is not correct .
D . A process to trace requirements: Tracing requirements is a related but distinct activity focused on linking requirements to their source and impact. Conclusion: This is not correct .