BCS PC-BA-FBA-20 Exam Dumps

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)

===========

The T-shaped professional model is used in business analysis to describe the ideal mix of skills and knowledge. The 'T' shape consists of a vertical bar and a horizontal bar. The vertical bar represents the deep and specific domain knowledge or core expertise (e.g., business analysis techniques, specific industry knowledge). The horizontal bar (the top of the 'T') represents the multi-disciplinary breadth of skill and knowledge that an individual can apply to various situations. This breadth includes soft skills like communication, facilitation, leadership, and a broad understanding of different business areas (like finance, operations, IT, and strategy). It is this breadth that allows the business analyst to collaborate effectively across different teams and disciplines, understand the context of the change, and recommend truly holistic solutions.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice -- Competencies of a Business Analyst)

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 determine the appropriate stakeholder management strategies for Harvey, we need to analyze his role and level of interest at two points in time:

When the project started: Harvey was the Director of Operations and had little interest in the HR project because his focus was on operational projects.

Now that his role has changed: As the Director of HR, Harvey has inherited sponsorship of the HR project, making him a key stakeholder with high interest and influence.

Stakeholder Management Strategies:

Watch: This strategy is used for stakeholders with low interest and low influence. It involves monitoring their behavior without actively engaging them.

Constant active management: This strategy is used for stakeholders with high interest and high influence. It involves frequent communication and collaboration to ensure their needs and expectations are met.

Evaluation of Each Option:

A . Keep informed; Constant active management: 'Keep informed' is appropriate for stakeholders with moderate interest but does not align with Harvey's initial lack of interest. Conclusion: This is not correct .

B . Ignore, Constant active management: Ignoring a stakeholder is inappropriate, especially for someone in a senior leadership role like Harvey. Conclusion: This is not correct .

C . Watch, Constant active management:

Initially, Harvey had low interest and low influence on the HR project, making 'watch' an appropriate strategy.

After becoming the Director of HR and inheriting sponsorship, Harvey now requires 'constant active management' due to his high interest and influence. Conclusion: This is the correct answer .

D . Constant active management, keep informed: This reverses the order of strategies and does not align with Harvey's initial lack of interest. Conclusion: This is not correct .

A Requirements Catalogue (or Requirements Specification) serves as the central repository for all documented requirements for a solution. BCS guidance categorises requirements hierarchically. At the highest level are the Business Requirements (often called General Requirements (c) and Technical Requirements (d)). These constrain the lower-level Solution Requirements, which consist of Functional Requirements (a) (what the system must do) and Non-functional Requirements (b) (quality attributes like performance, security, and usability). Since the catalogue aims to provide a complete picture of the business need and the proposed solution's capabilities, it must contain all four categories: Functional, Non-functional, General (Business), and Technical requirements.

(Reference: BCS Requirements Engineering -- Requirements Categorisation and Documentation)