PC-BA-FBA-20 Exam Dumps - BCS Foundation Certificate in Business Analysis V4.0

Traceability links requirements to other project artefacts. There are two main types: horizontal and vertical. Horizontal traceability (Option A) links a requirement forward to its design, code, and test cases, and backward to its source (Option D), tracing its lifecycle from inception to delivery. Vertical traceability concerns tracing a requirement up or down the requirements hierarchy (C). This ensures that lower-level requirements (e.g., functional) are aligned with and fully support the higher-level business objectives, policies, and strategy. For example, it traces a solution requirement up to the business requirement it satisfies, validating that every low-level detail is necessary and justified by a high-level business need.

(Reference: BCS Requirements Engineering – Requirements Traceability)

The POPITâ„¢ model is a holistic framework used in business analysis to ensure that all aspects of the business system are considered when investigating a situation or implementing a change. The acronym stands for People, Organisation, Processes, Information, and Technology. Therefore, the two 'P' components of the model are People and Processes. 'People' relates to skills, motivation, job roles, and culture. 'Processes' refers to the defined procedures, activities, and tasks carried out to deliver the business service. Ensuring that changes are successful requires addressing all five components, as a change in one area (e.g., a new IT system) invariably impacts the other areas (e.g., the skills of the People, or the Information required).

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Holistic View of the Business System, POPIT Model)

The Requirements Catalogue (or the Requirements Specification section) is the comprehensive, organised list of all types of requirements. Technical Requirements are the non-functional constraints placed on the solution's design or build (e.g., specific hardware, operating system compatibility, integration protocols). While these inform other models, they are typically documented and tracked with other requirements (Functional and Non-functional) in the master Requirements Catalogue, often within the Non-functional or System Requirements section of the catalogue structure. Options A, B, and C are supporting documents or models, not the primary repository for a list of technical requirements.

(Reference: BCS Requirements Engineering – Requirements Catalogue Structure)

To identify the generic business improvement strategy that involves eliminating redundant tasks, we need to analyze each option:

Key Considerations:

Change task sequence: This strategy involves reordering tasks to improve efficiency but does not necessarily eliminate redundancy.

Simplification: This strategy focuses on streamlining processes by removing unnecessary or redundant tasks, making workflows more efficient.

Redefine boundary: This strategy involves changing the scope or boundaries of a process, which may or may not involve eliminating redundant tasks.

Bottleneck removal: This strategy targets specific constraints or bottlenecks in a process but does not focus on eliminating redundant tasks.

Evaluation of Each Option:

A. Change task sequence:Changing the order of tasks does not inherently eliminate redundancy.Conclusion: This is not correct .

B. Simplification:Simplification directly involves identifying and removing redundant or unnecessary tasks to streamline processes.Conclusion: This is correct .

C. Redefine boundary:Redefining boundaries changes the scope of a process but does not specifically target redundancy.Conclusion: This is not correct .

D. Bottleneck removal:Removing bottlenecks addresses constraints but does not focus on eliminating redundant tasks.Conclusion: This is not correct .

Feasibility assessment is a critical part of developing the Business Case and typically involves four key areas: Business, Technical, Financial, and Legal/Ethical. The assessment that addresses whether a proposed solution or change initiative aligns with the organisation's overall objectives, mission, and strategy is Business Feasibility. This check is vital because if a proposal does not support the strategic direction, it will not deliver the expected value, regardless of its technical or financial viability. It ensures that the change is the right thing for the business to do at a strategic level.

(Reference: BCS Business Analysis Practice – Feasibility Assessment, Business Case Development)

To determine the position of the head of IT services on the power-interest grid , we need to evaluate their level of power/influence and interest in the project.

Key Considerations:

Power/Influence: The head of IT services holds a senior leadership role, which implies they have significant authority and influence over IT-related decisions and resources. This places them in the "high power" category.

Interest: Despite their authority, the head of IT services has not been actively involved in the project beyond the initial start-up interviews and has not attended any project meetings. This indicates a lack of ongoing engagement or interest in the project's progress.

Evaluation of Each Option:

A. High power or influence but low interest:The head of IT services has significant authority (high power) but is disengaged from the project (low interest).Conclusion: This is the correct answer .

B. Some power and influence and some interest:This option suggests moderate levels of both power and interest, which does not align with the head of IT services' senior role and lack of involvement.Conclusion: This is not correct .

C. High power or influence and high interest:While the head of IT services has high power, their lack of attendance at project meetings indicates low interest.Conclusion: This is not correct .

D. Low power and influence but high interest:The head of IT services clearly has high power due to their senior leadership role, so this option is incorrect.Conclusion: This is not correct .

Final Recommendation:

The head of IT services occupies the position of high power or influence but low interest on the power-interest grid.

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)

The MoSCoW prioritization technique categorises requirements based on their importance to the current timebox or delivery. The categories are defined as follows:

MUST Have: Non-negotiable; essential for the solution to be viable. If missed, the project fails.

SHOULD Have: Important but not vital; the solution is still viable if these are deferred, but it will be a loss or require a workaround.

COULD Have: Desirable; can be deferred until the next timebox, with a minor impact on value.

WON'T Have this time (or WANT): Agreed not to be delivered now.

The description "essential but which may be deferred in the short term" aligns perfectly with SHOULD Have. This category implies high importance, but the risk of non-delivery is managed through a temporary workaround, making them the first requirements considered for deferral if the schedule is threatened.

(Reference: BCS Requirements Engineering – Prioritisation Techniques, MoSCoW)

===========