BCS PC-BA-FBA-20 Exam Dumps

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 technique focused on analyzing the fit between an organisation's offerings and customer needs, specifically examining the combination of product and service attributes, the company's image, and the customer relationship, is the Value Proposition. The Value Proposition describes the unique benefits, value, and experience that a company promises to deliver to its customers to satisfy their needs and wants better than the competition. It's a critical tool for ensuring that the business improvement efforts are truly valuable from a customer's perspective. Porter's Five Forces and SWOT analysis are macro-strategic tools, and SIPOC is a process analysis technique.

(Reference: BCS Business Analysis Practice -- Improving Business Services and Processes, Value Proposition)

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)

An organization chart visually represents the structure of an organization, including roles, responsibilities, and reporting relationships. By reviewing the organization chart, Sara can learn specific details about the sponsor of her project.

Key Considerations:

Position in the company hierarchy: The organization chart clearly shows where the sponsor fits within the company's structure (e.g., senior leadership, middle management). This helps Sara understand their level of authority and influence.

Span of control: The chart also reveals how many teams or individuals report to the sponsor, providing insight into their scope of responsibility and decision-making power.

Culture within their team: While the chart may hint at team structure, it does not provide qualitative information about team culture, which requires direct observation or interviews.

Scope of their responsibilities: The chart outlines reporting lines but does not explicitly detail the specific responsibilities of the sponsor.

Preferred management style: Management style is a behavioral trait that cannot be inferred from an organization chart alone.

Evaluation of Each Option:

A . Their position in the company hierarchy: The organization chart explicitly shows the sponsor's position in the hierarchy, helping Sara understand their level of authority. Conclusion: This is relevant .

B . Their span of control: The chart reveals how many people or teams report to the sponsor, indicating their span of control. Conclusion: This is relevant .

C . The culture within their team: Team culture is not represented in an organization chart. It requires additional qualitative data. Conclusion: This is not relevant .

D . The scope of their responsibilities: While the chart provides structural information, it does not specify the exact responsibilities of the sponsor. Conclusion: This is not relevant .

E . Their preferred management style: Management style cannot be determined from an organization chart. Conclusion: This is not relevant .

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)