01.11.2017 Views

BABOK_Guide_v3_member_copy

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Techniques<br />

Scope Modelling<br />

Depending on the action or stakeholder needs the model supports, a business<br />

analyst determines the types of models to be used and selects boundaries and<br />

elements.<br />

.2 Scope of Change and Context<br />

Typically, business analysts are concerned with elements that will be altered as<br />

part of a change, as well as external elements that are relevant to the change. For<br />

elements inside the scope of change, the business analyst is involved in<br />

establishing the ways those elements are modified. For elements outside the<br />

scope of change but relevant to the change, the business analyst is involved in<br />

establishing the interactions between the change, the current and proposed<br />

solutions, and the context.<br />

The business analyst often determines:<br />

• business processes to be defined or modified,<br />

• business functions to be added, changed, optimized, or re-assigned,<br />

• new capabilities to be built or existing capabilities to be changed,<br />

• external and internal events to be responded to,<br />

• use cases and situations to be supported,<br />

• technologies to be changed or replaced,<br />

• informational assets to be acquired, produced, or processed,<br />

• stakeholders and organizational roles impacted by the change,<br />

• external and internal agents and entities impacted by the change,<br />

• organizations and organizational units (departments, teams, groups)<br />

impacted by the change, and<br />

• systems, components, tools, and physical assets required for the change or<br />

impacted by the change.<br />

.3 Level of Detail<br />

The purpose of analysis defines the appropriate level of abstraction at which<br />

scope elements are described. A proper level of detail provides a meaningful<br />

reduction of uncertainty while preventing 'analysis paralysis' at a scope definition<br />

stage. The elements of the final scope model can be described by enumerating<br />

them, by referring to a specific level of their decomposition hierarchy, or by<br />

grouping them into logically bound sets. For example, a subject of change can be<br />

defined as a list of specific business processes, as a high-level business process<br />

encompassing all of them, or as a generic business function. Similarly,<br />

stakeholders included in the scope can be defined by enumerating specific titles<br />

or by referring to their common organizational role.<br />

Complimentary IIBA® Member Copy. Not for Distribution or Resale.<br />

339

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!