Pass the BCS Business Analysis PC-BA-FBA-20 Questions and answers with Dumpstech

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 Project Sponsor is the senior executive or manager who owns the project, champions it, secures funding, and holds ultimate accountability for the benefits. While they are the most important stakeholder and sign off on the requirements, they are typically NOT an active, day-to-day working member of the project team responsible for executing the Requirements Engineering activities. The Project Manager (A), Business Analyst (C), and Software Tester (D) are all core, active members of the project team with specific roles in managing, defining, and validating the requirements, respectively.

(Reference: BCS Requirements Engineering – Roles in Requirements Engineering)

One of the core principles of business analysis is the continuous need for negotiation and consensus building, particularly when dealing with conflicting stakeholder perspectives and requirements. Business analysis actively seeks to negotiate and resolve these conflicts rather than avoiding them, which is a key part of establishing a shared understanding of the problem and the proposed solution. The other options contradict established BA principles: the principle is to find root causes, not symptoms (leading to superficial and ineffective solutions); to investigate and evaluate multiple options, not just solutions (ensuring the optimal change is selected); and to focus on business improvement as the driver for any necessary IT system change, not the other way around. The BA role necessitates working across competing interests to reach a successful outcome, making negotiation a fundamental principle.

(Reference: BCS Business Analysis Practice – Principles of Business Analysis / Analysing and Managing Stakeholders)

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.

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 .

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)

The concern of consumers about unnecessary packaging is an external factor that influences the organisation. The appropriate technique for systematically analysing these external macro-environmental factors is PESTLE analysis. PESTLE stands for Political, Economic, Sociological, Technological, Legal, and Environmental factors. The increasing consumer concern about packaging falls clearly under the Sociological or Environmental categories of the PESTLE framework. This technique helps the business analyst identify trends and issues arising from outside the organisation that may create a business need or risk, which then drives strategic change. The other options are incorrect: a Power/Interest grid is for stakeholder management; Boston Box (BCG Matrix) is for product portfolio management; and a Resource Audit is for internal analysis of resources.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Strategic Analysis, External Environment Analysis)

Workshops are structured meetings designed to achieve specific objectives through group participation. Regardless of the workshop ' s focus, collaboration is a fundamental goal.

Key Considerations:

Collaboration: Workshops bring stakeholders together to share ideas, solve problems, and make decisions collaboratively.

Reviewing the Business Case: While reviewing the business case may be a specific objective of some workshops, it is not a universal goal.

Creating Mind Maps and Process Models: These are tools or outputs of workshops, not overarching goals.

Brainstorming Ideas: Brainstorming is a technique used in workshops but is not the ultimate goal of all workshops.

Evaluation of Each Option:

A. Collaboration: Collaboration is the core purpose of workshops, enabling participants to work together effectively. Conclusion: This is correct .

B. Reviewing the business case: This is a specific objective, not a universal goal of all workshops. Conclusion: This is not correct .

C. Creating mind maps and process models: These are tools or outputs, not goals. Conclusion: This is not correct .

D. Brainstorming ideas: Brainstorming is a technique, not the overarching goal of all workshops. Conclusion: This is not correct .

Final Recommendation:

The goal of all workshops is:

A. Collaboration.

Functional and non-functional requirements sit within the detailed requirements area and describe what the solution must do and how well it must perform. Functional requirements define required behaviour, services, processing, calculations, or interactions. Non-functional requirements define qualities and constraints such as performance, security, usability, availability, and reliability. In a requirements hierarchy, these requirements are developed from broader business, general, and technical requirement categories. Option B is too narrow because it describes mainly non-functional requirements, not functional requirements. Option D is wrong because the highest level is the business need or business requirement. Option A refers to project principles, not solution requirements. Therefore, functional and non-functional requirements are best described as an elaboration of General and Technical requirements.

A process that is " well designed " (optimally structured, free from unnecessary steps) implies that issues like Redundancy (B), Lack of standardisation (C), and Duplication (D) have been eliminated or minimised through effective process design (i.e., making it lean and efficient). However, even a perfectly designed process will fail to achieve its objectives if the necessary resources are not available to execute it. Insufficient resources (such as people, funding, equipment, or time) represent a constraint on the execution, leading to bottlenecks, delays, and a failure to meet performance targets, regardless of the quality of the process design itself. This is often an implementation or operational management issue, not a design flaw.

(Reference: BCS Business Analysis Practice – Process Improvement)