Analyze elicitation results and transform them into requirements

The business analyst analyzes elicitation results, creates representations of those results, and defines stakeholder requirements as well as detailed solution requirements. The requirements architecture guides the business analyst in using a combination of text, charts, diagrams, and models.

When analyzing elicitation results and transforming them into requirements, business analysts should consider using a combination of models that best meet stakeholder needs. There are different model categories that can be utilized:

• People and Roles: These models represent organizations, groups of people, roles, and their relationships within an enterprise and to a solution. Techniques include Organizational Modelling, Roles and Permissions Matrix, and Stakeholder List, Map, or Personas.
• Rationale: These models represent the "why" of a change. Techniques include Decision Modelling, Scope Modelling, Business Model Canvas, Root Cause Analysis, and Business Rules Analysis.
• Activity Flow: These models represent a sequence of actions, events, or a course that may be taken. Techniques include Process Modelling, Use Cases and Scenarios, and User Stories.
• Capability: These models focus on features or functions of an enterprise or a solution. Techniques include Business Capability Analysis, Functional Decomposition, and Prototyping.
• Data and Information: These models represent the characteristics and exchange of information within an enterprise or a solution. Techniques include Data Dictionary, Data Flow Diagrams, Data Modelling, Glossary, State Modelling, and Interface Analysis.

Elements

• Model Requirements: A model is a descriptive and visual way to convey information to a specific audience to support analysis, communication, and understanding. Business analysts choose from one or more of the following modelling formats.
• Analyze Requirements: Business analysis information is decomposed into components to examine what to change, to stay, is missing, unnecessary, constraint, assumption.
• Represent Requirements and Attributes: Various attributes can be specified for each requirement or set of requirements. These are selected when planning information management.
• Implement the Appropriate Levels of Abstraction: The level of abstraction of a requirement varies based on the type of requirement and audience for the requirement.

Guideline and Tools

• Modelling Notations/Standards: allow requirements and designs to be precisely specified, as is appropriate for the audience and the purpose of the models. Standard templates and syntax help to ensure that the right information is provided about the requirements.
• Modelling Tools: software products that facilitate drawing and storing matrices and diagrams to represent requirements. This functionality may or may not be part of requirements life cycle management tools.
• Requirements Architecture: the requirements and interrelationships among them can be used to ensure models are complete and consistent.
• Requirements Life Cycle Management Tools: software products that facilitate recording, organizing, storing, and sharing requirements and designs.
• Solution Scope: the boundaries of the solution provide the boundaries for the requirements and designs models.