Score Higher on Verified PC-BA-FBA-20 | BCS Foundation Certificate in Business Analysis V4.0 Exam Questions with Answers

The stakeholder wheel is a framework used to categorize stakeholders based on their relationship to the organization or project. It typically includes categories such as customers, partners, suppliers, regulators, and competitors , among others.

Key Considerations:

Regulators, Compliance, Owners: While regulators and owners are valid stakeholders, "compliance" is not a stakeholder category but rather a function or responsibility.

Competitors, Customers, Partners: These are all valid stakeholder categories commonly found on the stakeholder wheel.

Competitors, Consumers, Providers: While competitors and consumers (a synonym for customers) are valid, "providers" is not a standard term used in the stakeholder wheel.

Contractors, Partners, Suppliers: Contractors are not typically included as a primary stakeholder category on the stakeholder wheel, though partners and suppliers are.

Evaluation of Each Option:

A. Regulators, Compliance, Owners:"Compliance" is not a stakeholder category; it refers to adherence to rules or regulations.Conclusion: This is not correct .

B. Competitors, Customers, Partners:These are all valid stakeholder categories found on the stakeholder wheel.Conclusion: This is correct .

C. Competitors, Consumers, Providers:While competitors and consumers (customers) are valid, "providers" is not a standard stakeholder category.Conclusion: This is not correct .

D. Contractors, Partners, Suppliers:Contractors are not typically included as a primary stakeholder category on the stakeholder wheel.Conclusion: This is not correct .

Final Recommendation:

The list that only includes stakeholders shown on the stakeholder wheel is:

B. Competitors, Customers, Partners

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 Business Readiness Assessment is a key activity conducted during the Implementation or Business Change Deployment stage of the project. Its primary purpose is to determine whether the target business areas, including the People, Organisation, and Processes, are sufficiently prepared to accept the business change and begin operating the new solution in the 'To Be' state. This involves checking factors such as whether staff have been trained, new processes are documented, communication has been effective, and necessary resources are in place. This assessment informs the 'Go/No Go' decision for the system's launch, ensuring a smooth transition to the new way of working.

(Reference: BCS Business Analysis Practice – Business Change Deployment, Business Readiness)