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

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)

The actor-task level is the lowest and most detailed level of the business process hierarchy. Its purpose is to show the sequence of actions and decisions taken by specific actors to complete a process. It effectively illustrates the work conducted within each individual task (often referred to as the procedure or work instruction). This level details how the work is performed.

Option A describes the Event-Response level (mid-level).

Option C is only part of the description—the actor is crucial, but the level shows the tasks they perform.

Option D describes the trigger for the Event-Response level.

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – Business Process Hierarchy)

===========

A business analyst is responsible for understanding business needs, analysing problems, eliciting requirements, exploring options, and helping stakeholders define valuable change. Options A, B, and D are all normal business analysis responsibilities. The analyst investigates the business situation, identifies needs, supports option development, and uses elicitation techniques such as interviews, workshops, observation, and document analysis to understand requirements. Ensuring that projects are delivered within budget constraints is primarily a project management responsibility. A project manager controls project delivery, manages schedule, cost, resources, risks, and progress against the approved plan. The business analyst may contribute estimates or impact analysis, but they do not normally own budget delivery. Therefore, option C is least likely to be a business analyst responsibility.

A benefits dependency network shows how business objectives, expected benefits, enabling business changes, and supporting outputs are connected. It helps analysts and stakeholders understand how a proposed change is expected to create value. The technique is useful because benefits are rarely achieved simply by delivering a system or product; they depend on business changes such as process redesign, behaviour change, training, new roles, or organisational adoption. Option B is too narrow because a benefits dependency network is not merely a stakeholder-benefit list. Option C describes cost breakdown, not benefit dependency. Option D describes requirements traceability, which is a different requirements management technique. The correct description is an overall representation linking objectives, benefits, and the business changes needed to realise those benefits.