Study guide

Modeling and Analysis Techniques

IIBA ECBA Entry Certificate in Business Analysis

Track your progress as you read

Finished sections get a check mark.

1 Introduction & ECBA Exam Overview

ECBA Exam Facts: Format, Eligibility, Cost, and Scoring How the ECBA Is Built: Source Documents, Blueprint Domains, and Study Plan

2 Understanding Business Analysis

What Is Business Analysis? The BACCM: Business Analysis Core Concept Model How Business Analysis Creates Value Defining Value and Assessing Value Realization

3 Mindset for Effective Business Analysis

The Business Analysis Mindset and How It Drives Effectiveness Shared Values and Core Business Analysis Principles Foundational Competencies Overview

4 Implementing Business Analysis

Business Analysis Roles and Organizational Context Choosing a BA Approach and the Requirements Classification Schema

5 Change

Contextual Factors Influencing the Work Impact Analysis Tracking Progress and Implementing Improvements

6 Need

Elicitation Methods and Stakeholder Rapport Documenting and Modeling Requirements Verifying and Validating Requirements Prioritizing Needs with MoSCoW

7 Solution

Solution Validation Criteria Evaluating Solution Options Scope Definition and Design Artifacts

8 Stakeholder

Communicating with Stakeholders Stakeholder Roles, Analysis, and RACI Facilitating Collaboration and Feedback

9 Value

Confirming Desired Outcomes and Value Opportunities Measuring Value Delivered

10 Context

Validating Information and Adapting Plans Technology Trends and Industry Standards

11 BABOK Techniques for ECBA

Elicitation and Collaboration Techniques Modeling and Analysis Techniques Strategy, Risk, and Investigation Techniques Requirements and Value Techniques

12 Underlying Competencies

Analytical Thinking, Behavioural Characteristics, and Business Knowledge Communication Skills, Interaction Skills, and Tools and Technology

13 Exam Readiness

Final Review & Exam-Day Strategy

Modeling and Analysis Techniques

Key Takeaways Explain This Topic AI

Data modelling documents entities, attributes, and relationships to standardize data terminology across business and technical teams.

Organizational modelling depicts roles, responsibilities, and reporting lines to clarify who is affected by a change.

Process analysis evaluates an existing process for inefficiencies and improvement opportunities, distinct from process modelling's visual depiction of flow.

Scope modelling visually defines the boundaries of a solution or analysis effort to prevent scope creep.

Business capability analysis identifies what an organization does, independent of how, to align investment with strategic priorities.

Last updated: July 2026

From As-Is Understanding to To-Be Design

Once a BA has elicited raw information, the next BABOK techniques turn that information into structured models stakeholders can validate. The seven techniques in this section fall into two groups: techniques that model a dimension of the business (data, organization, process, scope) and techniques that analyze what the business does or how it must behave (capabilities and rules). ECBA situational questions test whether a candidate can match a described artifact to the correct technique name.

The Seven Techniques at a Glance

Technique Purpose When to Use

Data Modelling Model entities, attributes, and relationships to document data requirements and standardize terminology Solution involves structured data that must be defined, stored, or exchanged consistently

Organizational Modelling Depict roles, responsibilities, and reporting relationships within an organizational unit Assessing organizational structure and culture, or defining stakeholder groups affected by change

Process Analysis Examine an existing (as-is) process to find inefficiencies, bottlenecks, and improvement opportunities Evaluating current processes before recommending change; process improvement initiatives

Process Modelling Visually depict the sequence of activities, events, and decisions in a process Documenting as-is or to-be process flow for a shared, unambiguous understanding

Scope Modelling Visually define the boundaries of a solution or analysis effort -- what is in and out Establishing or communicating the boundaries of a change, or defining what is included and excluded

Business Capability Analysis Identify what an organization does, independent of how, to align investment with strategy Strategic planning, portfolio prioritization, identifying capability gaps

Business Rules Analysis Identify, capture, and validate the rules that constrain or guide business decisions and operations Solution must enforce or comply with specific policies, regulations, or decision logic

Data Modelling

Data modelling documents the entities relevant to a business domain, their attributes, and the relationships between them, typically through an entity-relationship diagram and supporting data dictionary. Its purpose is a shared, unambiguous definition of the data a solution must capture, store, or exchange, avoiding conflicting interpretations of terms like "customer" or "account." Use data modelling whenever a solution touches structured data and stakeholders need a consistent vocabulary before development begins.

Organizational Modelling

Organizational modelling depicts roles, responsibilities, and reporting lines within a business unit, typically through an organization chart supplemented by role descriptions. It clarifies who does what and reports to whom, which matters when a change affects staffing or decision authority. A BA uses organizational modelling early in an initiative to understand the structure of the affected group, and again when defining which stakeholder groups fall inside the analysis scope.

Process Analysis

Process analysis examines an existing process to find value-add versus non-value-add steps, bottlenecks, and root inefficiencies. Unlike process modelling, which focuses on depicting the flow, process analysis focuses on evaluating that flow to surface improvement opportunities. It is the right technique when a business already has a defined process and the goal is to determine how the process should change -- a step that logically precedes designing a to-be process.

Process Modelling

Process modelling visually represents the sequence of activities, events, gateways or decisions, and actors in a process, often using flowchart-style notation. Its purpose is a shared, precise picture of how work flows through a business area for either the current (as-is) or future (to-be) state. Use process modelling whenever stakeholders need a common, visual reference for how a process actually works or should work, especially when steps involve multiple roles or systems.

Scope Modelling

Scope modelling visually defines the boundary of a solution, project, or analysis effort, showing what is included, what is excluded, and where the boundary sits relative to other initiatives. Common forms include context diagrams and feature or capability groupings. A BA reaches for scope modelling to prevent scope creep and to give stakeholders and sponsors a clear, agreed picture of what the initiative will and will not address, typically early in planning and whenever scope needs to be re-confirmed.

Business Capability Analysis

Business capability analysis identifies what an organization does, independent of how those capabilities are performed or which department executes them. Capabilities are typically organized into a capability map and evaluated for value, performance, and strategic importance. This technique supports strategic planning and portfolio decisions: it is used when leadership needs to prioritize investment or identify where a capability gap is limiting the achievement of goals.

Business Rules Analysis

Business rules analysis identifies, defines, and validates the rules and policies that constrain or guide business decisions and operations, for example eligibility criteria, calculation logic, or compliance requirements. Rules are typically expressed in structured business vocabulary and organized into rule sets or decision tables so they can be applied consistently. Use business rules analysis whenever a solution must enforce specific policies or regulations, or when inconsistent rule application is itself the problem.

Recognizing These Techniques on the Exam

Situational stems will describe an artifact, such as a diagram showing customer, order, and product entities and their relationships, or an activity, such as mapping what functions the finance department performs regardless of the current org chart, and ask which technique produced it. Two reliable discriminators help: modelling techniques (data, organizational, process, scope) produce a visual or structural representation of a specific business dimension, while analysis techniques (business capability, business rules, and process analysis) evaluate or classify that dimension against a goal, standard, or strategy rather than merely depicting it. Recognizing which of these two jobs a scenario describes is often enough to identify the correct technique even before matching the exact name.