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

To determine the best source of information for Natasha to understand how Halliday Holdings' brand is perceived, we need to evaluate the options based on their relevance and objectivity.

Evaluation of Each Option:

A . Independent industry websites: Independent industry websites often provide unbiased insights into how a company's brand is perceived by customers, competitors, and the market. These sources aggregate reviews, ratings, and expert opinions, making them a valuable resource for understanding external perceptions. Conclusion: This is the best source .

B . The company website: The company website reflects the organization's internal perspective and branding efforts. While useful for understanding how the company presents itself, it does not provide an external view of brand perception. Conclusion: This is not the best source .

C . The company's organizational structure: The organizational structure provides insights into the company's internal hierarchy and operations but does not relate to external brand perception. Conclusion: This is not relevant .

D . The company's complaints procedures: Complaints procedures reflect internal processes for handling customer issues but do not provide a comprehensive view of overall brand perception. Conclusion: This is not the best source .

In an iterative or Agile lifecycle, requirements are not defined entirely upfront but are explored and refined just-in-time, immediately prior to implementation. The stage where the detailed solution requirements (functional and non-functional) are elaborated, modeled, and defined---ready for construction---is the Develop solution stage (often referred to as the Implementation or Construction phase of an iteration/sprint). The detailed work of defining, modelling, and validating the specific requirements happens as a preparatory step for the actual build, distinguishing it from the preceding planning phase (C) or the upstream strategic work (A, B).

(Reference: BCS Requirements Engineering -- Lifecycle Models, Iterative Development)

A formal Requirements Validation Review (or walkthrough/inspection) is conducted to ensure the requirements are correct, complete, and meet the business need before sign-off. The review group typically includes the Business Owner (A) to ensure correctness, the Solution Architect (C) and Developers to check technical feasibility, and the Tester (D) to ensure testability. The Project Manager (B) is usually the facilitator or organiser of the review process and is responsible for project delivery, but they are NOT usually a technical reviewer of the document content itself, as their direct involvement could compromise the impartiality of the review, which is focused on quality assurance, not project schedule.

(Reference: BCS Requirements Engineering -- Requirements Validation Techniques)

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.