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

In a UML (Unified Modeling Language) Activity Diagram, the symbol used to represent a task (or action/activity) is a round-cornered rectangular box. This shape denotes an individual piece of work or step carried out within the process.

The other symbols represent:

A filled in circle (B): The Initial Node (start of the process).

A diamond shaped box (C): A Decision or Merge Node (a point where a choice is made or paths recombine).

A bullseye (D) (a filled circle inside an outer circle): The Activity Final Node (end of the process flow).

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – UML Activity Diagrams)

===========

Prototyping is a technique used to create a working model of a system or product to validate requirements and gather feedback. Let’s evaluate each statement to determine which are false :

Evaluation of Each Statement:

A. Suitable for waterfall requirements elicitation:Prototyping is generally not suitable for traditional waterfall methodologies because waterfall follows a linear, sequential approach where requirements are defined upfront before development begins. Prototyping, on the other hand, involves iterative feedback loops, which are more aligned with Agile methodologies.Conclusion: This statement is false .

B. Allows an analyst to confirm their understanding of requirements:Prototyping enables analysts to validate their understanding of requirements by creating a tangible representation of the system for stakeholders to review and provide feedback.Conclusion: This statement is true .

C. Only suitable for Agile project environments:While prototyping is commonly used in Agile environments due to its iterative nature, it is not limited to Agile. Prototyping can also be used in hybrid or iterative waterfall projects to clarify requirements and reduce ambiguity.Conclusion: This statement is false .

D. Enables the elicitation of usability requirements:Prototyping is particularly effective for gathering usability requirements because it allows stakeholders to interact with a mock-up or early version of the system, providing insights into user experience and interface design.Conclusion: This statement is true .

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)