BABOK_Guide_v3_member_copy

Requirements Analysis and Design Definition
Verify Requirements
7.1.7 Stakeholders
7.1.8 Outputs
• Organizational Modelling: used to allow business analysts to model the
roles, responsibilities, and communications within an organization.
• Process Modelling: used to show the steps or activities that are performed in
the organization, or that must be performed to meet the desired change.
• Prototyping: used to assist the stakeholders in visualizing the appearance and
capabilities of a planned solution.
• Roles and Permissions Matrix: used to specify and model requirements
concerned with the separation of duties among users and external interfaces in
utilizing a solution.
• Root Cause Analysis: used to model the root causes of a problem as part of
rationale.
• Scope Modelling: used to visually show a scope boundary.
• Sequence Diagrams: used to specify and model requirements to show how
processes operate and interact with one another, and in what order.
• Stakeholder List, Map, or Personas: used to identify the stakeholders and
their characteristics.
• State Modelling: used to specify the different states of a part of the solution
throughout a life cycle, in terms of the events that occur.
• Use Cases and Scenarios: used to model the desired behaviour of a solution,
by showing user interactions with the solution, to achieve a specific goal or
accomplish a particular task.
•User Stories: used to specify requirements as a brief statement about what
people do or need to do when using the solution.
• Any stakeholder: business analysts may choose to perform this task
themselves and then separately package and communicate the requirements to
stakeholders for their review and approval, or they might choose to invite some
or all stakeholders to participate in this task.
Complimentary IIBA® Member Copy. Not for Distribution or Resale.
• Requirements (specified and modelled): any combination of requirements
and/or designs in the form of text, matrices, and diagrams.
7.2 Verify Requirements
7.2.1 Purpose
The purpose of Verify Requirements is to ensure that requirements and designs
specifications and models meet quality standards and are usable for the purpose
they serve.
141