BCS PC-BA-FBA-20 Exam With Confidence Using Practice Dumps

The BCS Business Change Lifecycle (which governs the entire change process from initial alignment to final benefit verification) typically comprises five key stages: Alignment, Definition, Design, Implementation, and Realisation. Realisation is the final, crucial stage where the actual benefits and expected business outcomes from the implemented solution are reviewed, measured, and confirmed against the original Business Case. Options A, B, and C are important activities or concepts that occur within the lifecycle but are not one of the five named stages of the complete end-to-end lifecycle model.

(Reference: BCS Business Analysis Practice – Business Change Lifecycle)

The Requirements Engineering (RE) Framework is a structured approach used by business analysts to define, document, and manage requirements. It consists of five iterative stages: Investigate Situation, Consider Perspectives, Analyze Needs, Evaluate Options, and Define Requirements .

Key Considerations:

Suitability for Waterfall Projects Only: The RE Framework is flexible and can be adapted to both waterfall and Agile methodologies.

Iterative Stages: The framework emphasizes iteration and refinement, making it suitable for evolving requirements.

Defining Requirements: The framework explicitly supports the definition and management of requirements.

Sequential Steps: While the stages are presented in a sequence, they are iterative and not strictly linear.

Evaluation of Each Option:

A. It is only suitable for use with waterfall projects:The RE Framework can be applied to both waterfall and Agile projects.Conclusion: This is not correct .

B. It shows five iterative stages that a business analyst needs to carry out to establish the requirements:This accurately describes the RE Framework's structure and purpose.Conclusion: This is correct .

C. Using the Requirements Engineering Framework does not help to define requirements:The framework is specifically designed to define and manage requirements.Conclusion: This is not correct .

D. It shows steps in the requirements engineering process that a business analyst must follow sequentially:While the stages are presented in a sequence, they are iterative and not strictly sequential.Conclusion: This is not correct .

In a UML Use Case Diagram, the entities that interact with the system being modeled (the System Boundary) are called Actors. An Actor represents a role played by a user, piece of hardware, or another system. External systems that exchange information with the system being defined are always represented as an actor outside the system boundary, just like human users. This clearly separates the responsibilities of the system under study from all entities and systems that lie outside its scope.

(Reference: BCS Requirements Engineering – Use Case Modelling)