PC-BA-FBA-20 BCS Foundation Certificate in Business Analysis V4.0 Questions and Answers

A mind map is used to organise ideas, information, and themes visually around a central topic. In business analysis, it helps structure early thinking, capture workshop outputs, group related concepts, and identify branches of investigation. It is especially useful when information is broad, unstructured, or exploratory. Option B describes a process model or activity diagram because flows of activities and decisions are shown using process modelling notation. Option C is closer to requirements modelling, use case modelling, product backlog decomposition, or solution architecture. Option A may be a possible outcome of analysis, but it is not the main purpose of a mind map. The key feature of a mind map is organising information into related themes and sub-themes, so option D is the best answer.

Business processes are typically organised into a three-level hierarchy to manage complexity and provide a clear line of sight from strategy to execution. The standard levels, moving from the highest to the lowest level of detail, are:

Enterprise (or Value Chain): The highest level, showing the core business functions (e.g., " Sell Product, " " Develop Product " ).

Event-Response (or End-to-End): The mid-level, showing the process triggered by a business event and concluding with an outcome (e.g., " Handle Customer Order " ).

Actor-Task (or Detailed/Procedure): The lowest level, showing the individual steps and actions taken by the actors to complete a process (e.g., " Check stock availability, " " Package item " ).

Therefore, the three key levels that define this breakdown are Enterprise, event-response, actor-task.

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – Business Process Hierarchy)

===========

Gap analysis is a technique for comparing the current state of the business ( ' As Is ' ) with the desired future state ( ' To Be ' ) to identify what is missing and what needs to change. The logical first step is to establish the current starting point. Therefore, the process begins by:

Assemble representations of existing situation (The ' As Is ' model). This involves investigating and documenting the current processes, organisation, people, information, and technology (POPIT).

Assemble representations of target or desired situation (The ' To Be ' model).

Identify gaps to be addressed (The difference between As Is and To Be).

Consider possible actions to address the gaps (Developing the recommendations).

(Reference: BCS Business Analysis Practice – Gap Analysis)

===========

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)

===========

Regulators are stakeholders who define, monitor, or enforce rules, standards, legislation, and compliance obligations that affect an organisation. In business analysis, regulators may influence what changes are possible, acceptable, or mandatory. For example, financial, data protection, safety, or industry regulators may require proposed changes to comply with legal or professional standards. Partners may collaborate with the organisation, but they do not normally enforce rules. Managers control internal resources and operations, but they are not the external rule-enforcing stakeholder category. Owners have financial or strategic interest in the organisation, but they do not normally monitor regulatory compliance unless they also hold a governance role. Since the question asks who monitors whether proposed changes fall within enforced rules, the correct stakeholder category is Regulators.

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)

Kaplan and Norton ' s Balanced Business Scorecard is a strategic framework that evaluates organizational performance across four key perspectives: Financial, Customer, Internal Business Processes, and Learning and Growth . To determine which area has not been considered, we need to map the provided KPIs to these perspectives.

Mapping the KPIs:

The time to deliver orders for products: This relates to operational efficiency and falls under the Internal Business Process perspective.

Consumer satisfaction with products: This directly measures customer experience and falls under the Customer perspective.

Wastage in product production: This also relates to operational efficiency and falls under the Internal Business Process perspective.

The qualifications of production employees: This measures employee capabilities and development, falling under the Learning and Growth perspective.

Evaluating Each Perspective:

Financial: None of the provided KPIs address financial performance, such as revenue, profitability, or cost management. Conclusion: This perspective has not been considered .

Customer: Consumer satisfaction with products is a clear indicator of the Customer perspective. Conclusion: This perspective has been considered.

Internal Business Process: Both " time to deliver orders " and " wastage in production " relate to internal processes. Conclusion: This perspective has been considered.

Learning and Growth: The qualifications of production employees indicate employee development, which aligns with this perspective. Conclusion: This perspective has been considered.

Final Recommendation:

The Financial perspective has not been considered in the company’s KPIs.

Interviews are valuable in requirements elicitation because they allow the business analyst to explore stakeholder knowledge, experience, concerns, assumptions, and expectations through direct conversation. This is especially useful for uncovering tacit knowledge: knowledge that stakeholders possess but may not have formally documented. Through questioning and follow-up, the analyst can probe unclear points and understand motivations, constraints, and priorities. Option B describes observation, not interviewing. Option C describes workshops, which are better for group consensus and shared understanding. Option D describes surveys or questionnaires, which are better for collecting responses from a large population. Interviews are strongest where depth, context, and personal insight are required. Therefore, the key advantage is access to tacit knowledge through direct stakeholder dialogue.

The Iterative (or Agile) lifecycle model is specifically designed to deal with changing requirements and a rapid pace of change. Unlike linear models like Waterfall or the V model, which expect requirements to be fixed early, the iterative model delivers the solution in a series of repeated cycles (iterations/sprints). This approach embraces the reality that requirements will change as stakeholders learn more about the evolving product and the business environment shifts. It explicitly incorporates frequent feedback loops and allows for the adaptation of requirements throughout the project, making it the most flexible and suitable model for unstable or complex environments.

(Reference: BCS Requirements Engineering – Lifecycle Models, Agile/Iterative)

The power/interest grid is a tool used in stakeholder analysis to categorize stakeholders based on their level of power (influence) and interest in the project. The position of stakeholders on the grid reflects their current status.

Key Considerations:

Where the Stakeholders Will Be After the Proposed Change: The grid represents the current state, not future projections.

Where the Stakeholders Should Be: The grid does not prescribe ideal positions but reflects actual positions.

Where the Stakeholders Actually Are at a Point in Time: The grid is a snapshot of stakeholders ' current power and interest levels.

Where the Stakeholders Believe They Should Be: The grid is based on objective analysis, not subjective beliefs.

Evaluation of Each Option:

A. Where the stakeholders will be after the proposed change: The grid reflects the present, not future states. Conclusion: This is not correct .

B. Where the stakeholders should be: The grid does not prescribe ideal positions but reflects actual positions. Conclusion: This is not correct .

C. Where the stakeholders actually are at a point in time: This accurately describes the purpose of the power/interest grid. Conclusion: This is correct .

D. Where the stakeholders believe they should be: The grid is based on objective analysis, not subjective beliefs. Conclusion: This is not correct .

Final Recommendation:

The position of stakeholders on a power/interest grid represents:

C. Where the stakeholders actually are at a point in time.

The investigation technique best suited to achieve these outcomes is the Interview. A one-on-one interview provides a private and focused setting, which is essential for discussing confidential or politically sensitive issues that a stakeholder would not be comfortable raising in a group or on a written questionnaire. The personal interaction during an interview is the most effective way to build rapport with the stakeholder, leading to more open and honest communication. This deeper level of trust and detailed conversation is what allows the analyst to gain a richer appreciation of the political and cultural landscape of the business. Special purpose records, document analysis, and questionnaires are more impersonal and cannot provide the same level of qualitative insight or trust.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Investigative Techniques, Interviews)

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)

===========

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)

The POPIT™ model ' s five elements are: People, Organisation, Processes, Information, and Technology.

The element that encompasses all matters related to data, records, and systems is Information and Technology. The ' Information ' part specifically covers the data that the organisation collects, stores, uses, and communicates, which includes the way that data (information) is distributed and shared across the organisation and with external parties. The ' Technology ' part covers the applications and hardware used to manage this information. Therefore, considering the distribution of data falls under the joint element of Information and Technology.

(Reference: BCS Business Analysis Practice – POPIT Model)

A benefits plan outlines how the anticipated benefits of a project or change initiative will be achieved, tracked, and managed. Its primary purpose is to ensure that benefits are realized as planned.

Key Considerations:

Tracking Changes to Requirements: A benefits plan focuses on benefits realization, not changes to requirements.

Quantifying Intangible Benefits: While intangible benefits may be included, the primary focus is on managing all benefits, tangible and intangible.

Tracking and Managing Benefits Realisation: The benefits plan provides a structured approach to monitor progress and ensure benefits are delivered.

Publishing to Shareholders: While stakeholders may review the plan, its primary purpose is internal management, not external communication.

Evaluation of Each Option:

A. It provides a firm basis for tracking the benefits of making changes to requirements: The benefits plan focuses on overall benefits realization, not specifically on changes to requirements. Conclusion: This is not correct .

B. It quantifies intangible benefits that could not be quantified when the business case was presented: While intangible benefits may be included, this is not the primary purpose of the plan. Conclusion: This is not correct .

C. It provides a firm basis for tracking the business benefits and managing their realisation: This accurately describes the primary purpose of a benefits plan. Conclusion: This is correct .

D. It is published to shareholders to show that their investment made will result in tangible benefits for the organisation: The benefits plan is primarily for internal use, not external reporting. Conclusion: This is not correct .

Final Recommendation:

The primary purpose of a benefits plan is:

C. It provides a firm basis for tracking the business benefits and managing their realisation.

The Business Change Lifecycle encompasses multiple stages, including alignment, analysis, design, implementation, and realisation. The role of a business analyst (BA) is versatile and can span across all these stages, depending on the project ' s needs.

Key Considerations:

Involvement Across All Stages: A business analyst can contribute to every stage of the lifecycle, from identifying business needs during alignment to ensuring benefits realization post-implementation.

Implementation Focus: While BAs are often heavily involved in implementation, their role is not limited to this stage.

Realisation Stage: BAs may also be involved in the realisation stage to validate that the intended benefits have been achieved.

Alignment Stage: Business analysis plays a critical role in aligning project objectives with organizational goals.

Evaluation of Each Option:

A. A business analyst can be involved at every stage in the lifecycle: This is true; BAs can contribute across all stages of the lifecycle. Conclusion: This is correct .

B. The business analyst is involved more heavily during the implementation stage of the lifecycle than any other stage: While BAs are often active during implementation, their involvement is not restricted to this stage. Conclusion: This is not correct .

C. The business analyst would not be involved in the realisation stage of the lifecycle: BAs can play a role in validating benefits realization, so this statement is false. Conclusion: This is not correct .

D. Business analysis does not take place in the alignment stage of a business change: Alignment involves understanding business needs and objectives, which is a core BA responsibility. Conclusion: This is not correct .

Requirements documentation generally follows two main styles: text-based and diagrammatic (or model-based).

Data model (A), Use case model (C), and Business process models (D - e.g., UML Activity Diagrams or BPMN) are all forms of diagrammatic documentation, using standardised graphical notation to express requirements.

A User story (B) is a short, simple, text-based statement written in the format: " As a [role], I want [goal] so that [benefit] " . It is a form of text-based requirement documentation used primarily in Agile environments, not a diagrammatic style.

(Reference: BCS Requirements Engineering – Documentation Styles)

===========

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.

Critical Success Factors (CSFs) are the few areas in which an organisation must achieve consistently high performance to meet its mission and strategic goals. To monitor whether a CSF is being achieved, a BA defines quantitative measures of performance, which are known as Key Performance Indicators (KPIs). KPIs are the specific, measurable metrics used to track and assess the success of an activity or the progress towards an objective. For example, if a CSF is " Excellent Customer Service, " a corresponding KPI might be " Average Call Waiting Time (less than 60 seconds) " —a clear, quantitative measure. While the Balanced Business Scorecard (D) is a framework that uses CSFs and KPIs, the specific quantitative measures themselves are the KPIs. Objectives (B) are the desired outcomes, not the measure of the outcome.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Strategic Context, CSFs and KPIs)

Here are the next five questions:

PESTLE analysis is a strategic analysis technique used to examine the external business environment. It considers Political, Economic, Social, Technological, Legal, and Environmental factors that may affect an organisation, business change, or proposed solution. It helps business analysts identify external opportunities, threats, constraints, drivers for change, and risks. Stakeholder power is assessed using stakeholder analysis techniques such as the power/interest grid, not PESTLE. Customer sentiment is more likely analysed through customer research, reviews, surveys, interviews, or customer journey work. Internal environment analysis is better supported by techniques such as SWOT, POPIT, value chain analysis, process analysis, and capability assessment. Since PESTLE focuses on factors outside the organisation’s direct control, the correct answer is External environment.

The Business Analysis Service Framework (BASF) identifies six core services provided by a business analyst. These services span the lifecycle of a business change initiative and focus on analysis and enablement activities. The six services are: Situation Investigation and Problem Analysis, Feasibility Assessment and Business Case Development, Business Process Improvement, Requirements Definition, Requirements Management, and Business Change Deployment. The service Solution design and development (which involves the technical building of the IT system) is a distinct project activity typically performed by solution architects and developers and, while the BA collaborates with them closely, it is not one of the core Business Analysis services as defined in the BASF.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Business Analysis Service Framework (BASF))

The Power/Interest Grid is a tool used to determine appropriate strategies for managing different stakeholder groups based on their level of power (influence) and interest in the project. The grid defines four quadrants, each with a recommended management strategy:

High Power, High Interest: Manage Closely

High Power, Low Interest: Keep Satisfied

Low Power, High Interest: Keep Informed

Low Power, Low Interest: Watch (Minimum effort)

The category of Some Power, Some Interest is generally considered the mid-range or main group of stakeholders. For these individuals, the best strategy is to Keep onside (or Manage Regularly). This strategy means maintaining regular communication, involving them in the project at appropriate times, and ensuring their needs and concerns are addressed so that their interest remains positive and their moderate power does not turn against the project.

(Reference: BCS Business Analysis Practice – Stakeholder Management, Power/Interest Grid)

===========

To determine the best way to present the changes to the scheduling team, we need to consider the nature of the information being communicated and the audience (the scheduling team). The extract describes changes to processes, roles, and systems, which are best represented visually to ensure clarity and understanding.

Key Considerations:

Business Process Model (BPM): A BPM is a visual representation of the steps in a process. It is particularly useful for communicating changes to workflows, roles, and responsibilities. Since the extract discusses splitting the scheduling team into two groups and introducing new software and processes, a BPM would effectively illustrate how these changes impact the workflow.

Business Activity Model (BAM): A BAM focuses on high-level activities and their logical dependencies, often used in strategic planning. However, it is less detailed than a BPM and may not adequately capture the specific changes to scheduling processes.

POPIT (People, Organization, Process, Information, Technology): POPIT is a framework for analyzing business change across multiple dimensions. While it provides a holistic view, it is not a presentation tool and would not be the best choice for directly communicating the changes to the scheduling team.

Prototype: A prototype is typically used to demonstrate the functionality of a system or software. While the introduction of telephony software and an online booking system could involve prototyping, this option does not address the need to communicate process and role changes.

Evaluation of Each Option:

A. Business Process Model: A BPM is ideal for illustrating the changes to the scheduling process, including the split into inpatient and outpatient teams and the integration of new software. It provides a clear, step-by-step visual representation that the scheduling team can easily understand. Conclusion: This is the best option .

B. Business Activity Model: While a BAM could provide a high-level overview of the changes, it lacks the detail needed to explain specific process adjustments. Conclusion: This is not the best option .

C. POPIT: POPIT is a framework for analysis, not a communication tool. It would not effectively convey the changes to the scheduling team. Conclusion: This is not the best option .

D. Prototype: Prototyping is relevant for demonstrating software functionality but does not address the need to communicate process and role changes. Conclusion: This is not the best option .

Final Recommendation:

The changes should be presented using a Business Process Model , as it effectively communicates the revised workflows and roles to the scheduling team.

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)

Requirements may be documented using several diagrammatic styles where visual representation helps stakeholders understand scope, data, behaviour, or process flow. A use case model is diagrammatic because it shows actors, system boundaries, and use cases. A data model is diagrammatic because it represents data entities, attributes, and relationships. A business process model is also diagrammatic because it shows tasks, decisions, flows, hand-offs, and responsibilities. An epic, however, is normally a high-level Agile requirement or large user story, not a diagrammatic document style. It may be broken down into features or user stories, but the epic itself is textual rather than a modelling notation. Therefore, “Epic model” is the item that is not suitable as a diagrammatic document style for requirements.

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 .

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)