Free BCS PC-BA-FBA-20 Exam Dumps May 2026

Gap analysis identifies the differences between the current state and the desired future state. To ensure a holistic view, a comprehensive framework like POPIT (People, Organization, Process, Information, Technology) is useful.

Key Considerations:

Payback Analysis: Focuses on financial returns and does not provide a holistic view.

POPIT: Analyzes gaps across multiple dimensions (people, organization, process, information, technology), ensuring a comprehensive perspective.

Boston Box: Evaluates market positioning of products or services, not gaps in organizational capabilities.

PESTLE: Analyzes external environmental factors but does not focus on internal gaps.

Evaluation of Each Option:

A . Payback analysis: Payback analysis focuses on financial metrics and does not address holistic gap analysis. Conclusion: This is not correct .

B . POPIT: POPIT ensures a holistic view by analyzing gaps across people, organization, process, information, and technology. Conclusion: This is correct .

C . Boston box: The Boston box evaluates product portfolios, not organizational gaps. Conclusion: This is not correct .

D . PESTLE: PESTLE analyzes external factors and does not focus on internal gaps. Conclusion: This is not correct .

Final Recommendation:

The technique useful for ensuring a holistic view in gap analysis is: B . POPIT.

The Requirements Engineering Framework describes the sequence of activities for defining and managing the requirements for a solution. The core activities typically include:

Requirements Elicitation (gathering requirements).

Requirements Analysis (checking, prioritizing, and modelling).

Requirements Documentation (recording in a catalogue or specification).

Requirements Validation (checking fitness for purpose and completeness).Requirements Traceability (linking requirements to their source, design, and tests) is a key aspect of Requirements Management, which is the overarching framework for handling requirements changes and status, but it is typically viewed as a component of the ongoing management process rather than a standalone core engineering activity on the same level as Elicitation or Validation.

(Reference: BCS Requirements Engineering -- Requirements Engineering Framework and Activities)

===========

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.