BCS PC-BA-FBA-20 - BCS Foundation Certificate in Business Analysis V4.1

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.

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 Agile, the Product Backlog is an ordered list of work that may be needed to improve or deliver the product. It normally contains user stories, features, defects, technical work, and other backlog items. It is prioritised so that the highest-value or most urgent items are considered first. It also contains work that may be selected for future sprints. However, once items are selected for the current sprint, they become part of the Sprint Backlog, which is the development team’s plan for the sprint. Therefore, the Product Backlog does not specifically represent what the team is working on in the current sprint. That is the purpose of the Sprint Backlog. Option C is therefore the statement that is not true.

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)

===========

The Business Analysis Service Framework (BASF) identifies core and auxiliary services that support business analysis activities. Auxiliary services supplement the core services and are essential for delivering value.

Key Considerations:

Strategic Analysis: Focuses on high-level organizational goals and strategies but is not an auxiliary service.

Stakeholder Engagement: Involves identifying, analyzing, and collaborating with stakeholders, which supports all aspects of business analysis.

Project Management: While important, project management is a separate discipline and not part of the BASF.

External Environment Analysis: Examines external factors (e.g., market trends) but is not an auxiliary service.

Evaluation of Each Option:

A. Strategic analysis: Strategic analysis is a core service, not an auxiliary service. Conclusion: This is not correct .

B. Stakeholder engagement: Stakeholder engagement is an auxiliary service that supports all business analysis activities by ensuring stakeholder needs are understood and addressed. Conclusion: This is correct .

C. Project management: Project management is outside the scope of the BASF. Conclusion: This is not correct .

D. External environment analysis: External environment analysis is a core service, not an auxiliary service. Conclusion: This is not correct .

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)

===========

A class model is used to represent business objects or data entities and the relationships between them. Its core elements include classes, attributes, and associations. A class represents a type of business object, such as Customer, Order, or Product. Attributes describe the information held about each class, such as customer name or order date. Associations show how classes relate to each other, for example, a Customer places an Order. Dataflow is not an element of a class model. Dataflow belongs more naturally to process modelling or data flow diagrams, where the analyst shows how information moves between processes, actors, or systems. Since the question asks for the item that is NOT part of a class model, the correct answer is Dataflow.

Value chain analysis examines how an organisation creates value for customers through a set of linked activities. Porter’s value chain separates activities into primary activities and support activities. Primary activities are directly involved in creating, delivering, marketing, and servicing products or services, such as inbound logistics, operations, outbound logistics, marketing and sales, and service. Support activities enable the primary activities to operate effectively, such as procurement, technology development, human resource management, and infrastructure. Activity sampling is an investigation technique, not a value chain category. Stakeholder management concerns engagement with stakeholder groups and does not show operational value creation. The phrase “primary and secondary activities” is not the standard value chain distinction. The correct terminology is primary activities and support activities.

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)

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â„¢.