The hierarchy of requirements organizes requirements into levels (e.g., business needs, stakeholder requirements, solution requirements) to ensure alignment and traceability. Let's evaluate each statement to determine which is false .
Key Characteristics of the Requirements Hierarchy:
* Linking Requirements: The hierarchy ensures that detailed requirements are connected to higher-level business needs and objectives.
* Order of Development: The hierarchy does not dictate the sequence in which requirements should be developed; it focuses on relationships and dependencies.
* Driven by Strategy: Requirements are derived from the organization ' s values, strategy, and objectives.
* Traceability: The hierarchy links different types of requirements to ensure consistency and alignment.
Evaluation of Each Statement:
* A. The requirements hierarchy enables detailed requirements to be linked to the business need:
This is true; the hierarchy ensures traceability between high-level and detailed requirements.
Conclusion: This is true .
* B. The requirements hierarchy shows the order in which requirements should be developed: The hierarchy does not specify the development order; it focuses on relationships and dependencies.
Conclusion: This is false .
* C. Requirements are driven by the organisation ' s values, strategy and objectives: This is true; requirements must align with organizational goals. Conclusion: This is true .
* D. The requirements hierarchy links different requirements to each other: This is true; the hierarchy ensures traceability and alignment across levels. Conclusion: This is true .
Final Recommendation:
The false statement is:
B). The requirements hierarchy shows the order in which requirements should be developed.

Actor-task level analysis looks at detailed work performed by specific actors, roles, or users. At this level, a task can be broken into smaller steps, inputs and outputs can be identified, and performance measures can be applied to assess efficiency, quality, or timeliness. Therefore, options B, C, and D are valid statements about actor-task analysis. Value chain analysis, however, is not used at this detailed actor-task level. It is an enterprise-level technique used to understand how organisational activities create value for customers. It examines primary and support activities across the business, not the detailed steps performed by a particular actor. Because value chain analysis belongs at a higher level of business process analysis, option A is the false statement.

The true statements about workshops are b and c. Workshops are collaborative, structured meetings involving multiple stakeholders. Statement (b) is true because having multiple stakeholders present allows the facilitator (often the BA) to immediately cross-check and resolve conflicting information or assumptions in real-time.
Statement (c) is true because the group environment, led by a skilled facilitator, is highly effective for discussing differing viewpoints and working towards a consensus or agreed-upon outcome. Statement (a) is false as this describes formal observation, not a workshop. Statement (d) is false; workshops are primarily used to gather qualitative information (opinions, requirements, process logic), not to collect accurate quantitative data (e.g., process timings or volumes), which is usually obtained from documents or system logs.
(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice - Investigative Techniques, Workshops)

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.

Personas are fictional but evidence-based representations of typical users or customer groups. They help business analysts and design teams understand user goals, behaviours, needs, frustrations, and motivations. Personas are often developed from user research and can be based on generic user roles, then enriched with characteristics that make them realistic and useful for analysis. They are not equivalent to a RACI chart because RACI defines responsibility, accountability, consultation, and information responsibilities for tasks. A single real user may also perform multiple roles, so option B is too restrictive. Personas are useful in user-centred design and requirements analysis, but they are not mandatory for decision analysis. Therefore, the true statement is that personas are taken from generic user roles.