Free ECBA Exam Dumps Preview

Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.

Business analysts perform a cultural assessment to:
1. identify if cultural changes are required to better achieve the goals, 2. identify whether stakeholders understand the rationale for the current state of the enterprise and the value delivered by it, and ascertain whether the stakeholders view the current state as satisfactory or if change is needed.

The highest level diagram is a context diagram which represents the entire system.

Stakeholders are more likely to support change if business analysts collaborate with them and encourage the free flow of information, ideas, and innovations. Genuine stakeholder engagement requires that all stakeholders involved feel that they are heard, their opinions matter, and their contributions are recognized.

Domain Subject Matter Expert: references maintained requirements on a regular basis to ensure they are
accurately reflecting stated needs.

A data flow diagram illustrates the movement and transformation of data between externals (entities) and processes. The output from one external or process is the input to another. The data flow diagram also illustrates the temporary or permanent repositories (referred to as data stores or terminators) where data is stored within a system or an organization. The data defined should be described in a data dictionary.

Page 76 - BABOK V3 Prioritize Requirements: assesses the value, urgency, and risks associated with particular requirements and designs to ensure that analysis and/or delivery work is done on the most important ones at any given time.

Page 86 - BABOK V3
The purpose of Prioritize Requirements is to rank requirements in the order of relative importance.

Page 87 - BABOK V3
Prioritization is the act of ranking requirements to determine their relative importance to stakeholders.

To maintain stakeholder support for the solution, consensus among stakeholders is usually sought prior to requesting approval of requirements.

It is important for the interviewer to organize the information and confirm results with the interviewees as soon as possible after the interview

References:
https://blog.fhyzics.net/fibaar/ba-techniques-user-stories

Elicitation Results (confirmed): integrated output that the business analyst and other stakeholders agree correctly reflects captured information and confirms that it is relevant and useful as an input to further work.

Business analysis information may be captured in a formal document or set of representations following standardized templates.

Verification activities include:
comparing each model against other relevant models, checking for elements that are mentioned in one model but are missing in other model

Derive: relationship between two requirements, used when a requirement is derived from another requirement. This type of relationship is appropriate to link the requirements on different levels of abstraction. For example, a solution requirement derived from a business or a stakeholder requirement.

Stability: the likelihood that the requirement will change, either because it requires further analysis or because stakeholders have not reached a consensus about it.

Create: solution components are assembled, constructed, or developed by experts as a direct response to a set of requirements.