BCS Updated PC-BA-FBA-20 Exam Questions and Answers by enola

A Requirements Catalogue (or Requirements Specification) serves as the central repository for all documented requirements for a solution. BCS guidance categorises requirements hierarchically. At the highest level are the Business Requirements (often called General Requirements (c) and Technical Requirements (d)). These constrain the lower-level Solution Requirements, which consist of Functional Requirements (a) (what the system must do) and Non-functional Requirements (b) (quality attributes like performance, security, and usability). Since the catalogue aims to provide a complete picture of the business need and the proposed solution ' s capabilities, it must contain all four categories: Functional, Non-functional, General (Business), and Technical requirements.

(Reference: BCS Requirements Engineering – Requirements Categorisation and Documentation)

The Waterfall lifecycle is a sequential approach where phases such as requirements, design, build, test, and implementation are completed in order. Its advantages include strong project control, clear documentation, formal stage approval, and greater predictability around scope, schedule, and cost. These features can be useful where requirements are stable and governance is strict. However, Waterfall is weak when business requirements change frequently. Because requirements are defined early and later stages depend on earlier sign-off, changes can be expensive, slow, and disruptive. Agile and iterative approaches were developed partly to address this weakness by allowing evolving requirements and incremental delivery. Therefore, “quickly and inexpensively reacts to changes in business requirements” is not an advantage of Waterfall. The correct answer is option C.

Functional and non-functional requirements sit within the detailed requirements area and describe what the solution must do and how well it must perform. Functional requirements define required behaviour, services, processing, calculations, or interactions. Non-functional requirements define qualities and constraints such as performance, security, usability, availability, and reliability. In a requirements hierarchy, these requirements are developed from broader business, general, and technical requirement categories. Option B is too narrow because it describes mainly non-functional requirements, not functional requirements. Option D is wrong because the highest level is the business need or business requirement. Option A refers to project principles, not solution requirements. Therefore, functional and non-functional requirements are best described as an elaboration of General and Technical requirements.

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 .