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 .

The Requirements Engineering Framework describes the sequence of activities for defining and managing the requirements for a solution. The core activities typically include:
Requirements Elicitation (gathering requirements).
Requirements Analysis (checking, prioritizing, and modelling).
Requirements Documentation (recording in a catalogue or specification).
Requirements Validation (checking fitness for purpose and completeness).Requirements Traceability (linking requirements to their source, design, and tests) is a key aspect of Requirements Management, which is the overarching framework for handling requirements changes and status, but it is typically viewed as a component of the ongoing management process rather than a standalone core engineering activity on the same level as Elicitation or Validation.
(Reference: BCS Requirements Engineering - Requirements Engineering Framework and Activities)

A use case diagram is a visual representation of how users (or systems) interact with a system to achieve specific goals. Actors represent the entities (e.g., users or external systems) that expect to receive services from the system.
Key Elements of a Use Case Diagram:
* Actors: Represent individuals or systems that interact with the system to achieve a goal.
* System Boundaries: Define the scope of the system being modeled.
* Users: While " users " may seem similar to actors, the term " actors " is the correct technical term in use case diagrams.
* Entities: Entities typically refer to data objects or components, not those receiving services.
Evaluation of Each Option:
* A. Actors: Actors are the correct element used to indicate those who expect to receive a service from the system. Conclusion: This is correct .
* B. System boundaries: System boundaries define the scope of the system but do not represent those receiving services. Conclusion: This is not correct .
* C. Users: While users may interact with the system, the correct term in use case diagrams is " actors. " Conclusion: This is not correct .
* D. Entities: Entities represent data objects or components, not those receiving services. Conclusion:
This is not correct .

The Requirements Catalogue (or the Requirements Specification section) is the comprehensive, organised list of all types of requirements. Technical Requirements are the non-functional constraints placed on the solution
' s design or build (e.g., specific hardware, operating system compatibility, integration protocols). While these inform other models, they are typically documented and tracked with other requirements (Functional and Non- functional) in the master Requirements Catalogue, often within the Non-functional or System Requirements section of the catalogue structure. Options A, B, and C are supporting documents or models, not the primary repository for a list of technical requirements.
(Reference: BCS Requirements Engineering - Requirements Catalogue Structure)