Study guide
Scope Definition and Design Artifacts
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
Scope Definition and Design Artifacts
Key Takeaways Explain This Topic AI
Scope Modelling is a named BABOK technique used to define what is included and excluded from an initiative, often through context diagrams or scope matrices.
BABOK distinguishes a requirement, a usable representation of a need, from a design, a usable representation of a solution.
Use cases and scenarios describe an actor's step-by-step interaction with a solution, including main and exception flows.
User stories are short, structured statements of stakeholder need, typically paired with acceptance criteria to drive iterative delivery.
Design artifacts such as process models and prototypes are living documents that business analysts update collaboratively as stakeholder understanding evolves.
Last updated: July 2026
Supporting Scope Definition
Before a solution can be designed in detail, the team needs a shared, documented understanding of what is — and is not — included in the initiative. Scope Modelling is a named BABOK technique used to define these boundaries, often through context diagrams (showing the solution and everything it interacts with), feature or capability models, or a simple scope matrix listing what's in and what's out.
At the entry level, a business analyst's role is usually to support scope definition rather than set it unilaterally: documenting inclusions and exclusions as they're agreed, capturing dependencies and assumptions that affect the boundary, flagging constraints the sponsor should be aware of, and communicating the agreed scope back to stakeholders so everyone is working from the same understanding. A clearly documented scope reduces the risk of "scope creep" and gives the team a reference point whenever a new request arrives mid-project.
What "Design" Means in BABOK
BABOK Guide v3 draws a specific distinction between a requirement and a design :
A requirement is a usable representation of a need — it describes what is needed, without necessarily saying how it will be delivered.
A design is a usable representation of a solution — it describes how the need will actually be met.
Design artifacts translate requirements into something concrete enough to build, configure, test, or evaluate. Business analysts prepare and update these artifacts throughout the project, refining them as understanding of the solution matures.
Common Design Artifacts and Their Purpose
Artifact Purpose Best used for
Use case / scenario Describes the step-by-step interaction between an actor and the solution, including the main path and exception/alternate flows Clarifying functional behavior, including what happens when something goes wrong
User story A short, structured statement of a stakeholder's need — "As a <role> , I want <goal> , so that <benefit> " — usually paired with acceptance criteria Driving iterative or adaptive delivery, keeping the need stakeholder-focused
Process model A visual depiction of a workflow, such as a swimlane diagram or flowchart, showing sequence, handoffs, and decision points Clarifying how work moves between roles or systems, and where decisions occur
Prototype A mockup, wireframe, or simulation of the solution, used to gather feedback before full build Validating design assumptions early and reducing the risk of costly rework
Each of these artifacts serves a different kind of clarity. A use case clarifies functional behavior and its exceptions; a user story keeps the focus on stakeholder value; a process model clarifies flow and handoffs across roles; a prototype lets stakeholders react to something concrete before the team commits to a full build.
Choosing the Right Artifact for the Situation
A business analyst rarely picks just one artifact type for an initiative; different questions call for different artifacts, often used together. If stakeholders disagree about the order in which steps happen or which role hands work off to which, a process model resolves the ambiguity visually in a way paragraphs of text cannot. If the team needs to confirm that a system correctly handles both the happy path and less common conditions — a failed payment, an expired session, a missing approval — a use case captures those branching flows explicitly. If the priority is keeping delivery focused on stakeholder value in an iterative environment, user stories paired with acceptance criteria keep each increment tied to a specific benefit. If the risk is that stakeholders and the team are picturing the finished solution differently, a prototype turns that mental picture into something people can react to before real effort is spent building it.
Choosing the wrong artifact for the situation costs time: a lengthy process model is a poor way to capture a single stakeholder's individual need, and a user story is a poor way to document a complex multi-role workflow with several decision points. Matching the artifact to the kind of clarity the situation actually requires is part of what makes design definition work efficient rather than just thorough.
Updating Artifacts for Clarity
Design artifacts are not one-and-done deliverables — they are living documents. As elicitation continues, as stakeholders review drafts, or as conflicting expectations surface, the business analyst revisits and updates the relevant artifact so it continues to reflect the current, agreed-upon understanding. When two stakeholders describe a process differently, or a prototype review reveals a misunderstanding, the appropriate response is to update the artifact collaboratively with those stakeholders — not to abandon it, and not to leave the mismatch undocumented.
Keeping artifacts current, versioned, and traceable back to the requirements they elaborate is what allows the team to move from "what is needed" toward "what will be built" with a shared, low-ambiguity understanding — and it is what allows the artifacts to remain useful reference points later, during solution validation and evaluation.
This discipline also protects the earlier scope agreement. If an updated use case or process model reveals functionality nobody had accounted for, that is a signal to revisit the scope boundary — not simply to expand the artifact and let the change pass unnoticed. Keeping design artifacts, requirements, and the agreed scope aligned with one another is what allows the team to catch scope drift early, while it is still a documentation conversation rather than a costly rebuild.