BCS PC-BA-FBA-20 Exam With Confidence Using Practice Dumps

Observation is an investigation technique where the business analyst watches users performing their work in the real business environment. It helps the analyst understand actual behaviour, workarounds, hand-offs, delays, exceptions, and informal practices that stakeholders may forget to mention in interviews. Observation may be formal, with planned sessions and recording sheets, or informal, where the analyst watches activities less rigidly. Option A and option D describe interviews, because they involve asking stakeholders questions directly. Option C describes a workshop or collaborative modelling activity, not observation. The defining feature of observation is that the analyst studies work as it is actually performed, rather than relying only on what stakeholders say happens. Therefore, option B is the best definition.

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)

===========

To build an enterprise view of processes , we need a framework that provides a holistic understanding of how value is created and delivered across the organization.

Key Considerations:

Class Model: Represents objects and their relationships in software development, not enterprise processes.

Swimlane Diagram: Visualizes workflows and responsibilities within a process but does not provide an enterprise-wide view.

Value Chain Analysis: Analyzes the activities that create value for customers, providing a comprehensive view of enterprise processes.

Porter’s Five Forces Model: Analyzes industry competition and external factors, not internal processes.

Evaluation of Each Option:

A. Class model: A class model is used in object-oriented design and does not represent enterprise processes. Conclusion: This is not correct .

B. Swimlane diagram: While swimlane diagrams visualize workflows, they focus on specific processes rather than an enterprise-wide view. Conclusion: This is not correct .

C. Value chain analysis: Value chain analysis examines the activities that contribute to value creation, making it ideal for building an enterprise view of processes. Conclusion: This is correct .

D. Porter’s five forces model: This model analyzes external competitive forces and does not focus on internal processes. Conclusion: This is not correct .