IIBA CCBA Practice Test - Questions Answers, Page 33

A state model describes:

• a set of possible states for an entity,

• the sequence of states that the entity can be in,

• how an entity changes from one state to another,

• the events and conditions that cause the entity to change states, and

• the actions that can or must be performed by the entity in each state as it moves through its life cycle.

While a process model can show all of the entities that are used in or affected by that process, a state model shows a complementary view: what happens to one entity across all the processes that affect it or use it.

Level of abstraction describes the breadth and depth of the information being provided.

Representations of information may range from highly conceptual or summarized to very detailed. In determining how much detail each stakeholder may require as the initiative evolves, consideration is given to the needs of the stakeholders, the complexity of what is being explained, and the importance of the change. Rather than present the same information to all stakeholders, business analysts should present information with appropriate breadth and level of detail based on each stakeholder's role. Business analysis information regarding a topic of significant importance or high level of risk is frequently represented in greater detail.

Level of Power or Influence Understanding the nature of influence and the influence structures and channels within an organization can prove invaluable when seeking to build relationships and trust. Understanding the influence and attitude each stakeholder may have can help develop strategies for obtaining buy-in and collaboration. Business analysts evaluate how much influence is needed to implement a change compared to the amount of influence the key stakeholders can bring. If there is a mismatch between the influence required and the amount of influence the stakeholder has or is perceived to have, business analysts develop risk plans, responses and other strategies that might be needed to obtain the required level of support.

Reference:

Babok v3.0 – IIBA guide

The purpose of requirements traceability is to trace where each requirement or design comes from or originated from and what its life cycle is throughout the project. If it is known why a requirement exists, or where it originated from, it will ensure that once the solution has been delivered, it does in actual fact solve the original requirement. By knowing where a requirement came from, or what the need that should be addressed is, the business analyst will know who to communicate to as well as be able to manage the risk, scope, and any changes associated with that requirement.

The predictive approach to delivery is a more formal approach and hence can cause a rework of tasks and activities already completed when a change is implemented as well as of the activities required to assess the proposed change on the whole.

A lot of requirements elicitation and analysis done in the early phases of a project follow the predictive approach. This means when a change is required during later phases of this type of project, there is often a higher impact on the time, cost, and effort required. An adaptive approach will try and minimize the impact of changes with iterative implementations from an early stage of the project. This approach typically lends itself to a less formal and more adaptable approach to manage the impact of change that is introduced during the life cycle of the project. Within the adaptive approach to delivery, the idea of an evolutionary delivery may also reduce the need for a formal impact assessment to be performed when a change is proposed to a requirement.

A key step in preparing for elicitation is to ensure that the logistics of the session or series of sessions are well planned for by considering the following key aspects:

The goals of the session.

Who are the participants and what are their roles?

Scheduled resources including people, rooms, and tools such as flip charts. Locations and communication channels.

Techniques that will be used.

Languages used by the stakeholders specifically being prepared to understand subject matter terminology and key abbreviations.

Stakeholder Engagement Approach: understanding the stakeholders and their concerns and interests may influence decisions made when determining the business analysis approach.