Unlock AI power-ups β upgrade and save 20%!
Use code STUBE20OFF during your first month after signup. Upgrade now β

By Olumide Adeleye | Business Analysis Coach
Published Loading...
N/A views
N/A likes
Defining Requirements in Business Analysis
π A requirement is defined as a clear description of what a user wants or needs in a solution, ensuring the final product is usable and effective.
π§΅ The video uses the analogy of visiting a tailor where unclear descriptions ("smart and traditional") lead to receiving the wrong item (a full aada instead of a simpler capan).
π In business analysis, clarifying requirements helps determine that the right solution is being built, preventing wasted effort on unnecessary features.
Types of Requirements
π Business Requirements: These are big-picture goals that answer "Why are we doing this project?" (e.g., a hospital aiming to reduce patient wait times by 40% this year).
π§ββοΈ Stakeholder Requirements: These detail the specific needs of relevant individuals, such as a receptionist needing a quicker way to register patients or a doctor wanting to see lab results in real time.
βοΈ Functional Requirements: These specify what the solution must actually do, covering concrete features like the system allowing patients to book appointments online or the app sending SMS reminders.
β±οΈ Nonfunctional Requirements: These concern the quality of the systemβhow it performs its functions (e.g., the website must load in 3 seconds or accommodate 10,000 users concurrently).
Application Example (SwiftKart)
π Business Requirement Example: SwiftKart aims to reduce average delivery time from 2 hours to 45 minutes within Lagos.
π Stakeholder Requirements Example: Customers want real-time delivery updates, and drivers need routes that avoid traffic.
π‘ Nonfunctional Requirement Example: The system must display updates even with low or unstable mobile data connections.
Key Points & Insights
β‘οΈ The role of a Business Analyst is crucial to capture, clarify, and record different requirement types because assumptions lead to disasters in project execution.
β‘οΈ Avoid building solutions nobody needs by confirming and clarifying requirements across all relevant industries (health, construction, tech).
β‘οΈ Functional requirements define the features developers build, whereas nonfunctional requirements define the performance and quality attributes of the solution.
πΈ Video summarized with SummaryTube.com on Feb 21, 2026, 10:05 UTC
Find relevant products on Amazon related to this video
As an Amazon Associate, we earn from qualifying purchases
Full video URL: youtube.com/watch?v=gZz_ruC4syU
Duration: 6:03
Defining Requirements in Business Analysis
π A requirement is defined as a clear description of what a user wants or needs in a solution, ensuring the final product is usable and effective.
π§΅ The video uses the analogy of visiting a tailor where unclear descriptions ("smart and traditional") lead to receiving the wrong item (a full aada instead of a simpler capan).
π In business analysis, clarifying requirements helps determine that the right solution is being built, preventing wasted effort on unnecessary features.
Types of Requirements
π Business Requirements: These are big-picture goals that answer "Why are we doing this project?" (e.g., a hospital aiming to reduce patient wait times by 40% this year).
π§ββοΈ Stakeholder Requirements: These detail the specific needs of relevant individuals, such as a receptionist needing a quicker way to register patients or a doctor wanting to see lab results in real time.
βοΈ Functional Requirements: These specify what the solution must actually do, covering concrete features like the system allowing patients to book appointments online or the app sending SMS reminders.
β±οΈ Nonfunctional Requirements: These concern the quality of the systemβhow it performs its functions (e.g., the website must load in 3 seconds or accommodate 10,000 users concurrently).
Application Example (SwiftKart)
π Business Requirement Example: SwiftKart aims to reduce average delivery time from 2 hours to 45 minutes within Lagos.
π Stakeholder Requirements Example: Customers want real-time delivery updates, and drivers need routes that avoid traffic.
π‘ Nonfunctional Requirement Example: The system must display updates even with low or unstable mobile data connections.
Key Points & Insights
β‘οΈ The role of a Business Analyst is crucial to capture, clarify, and record different requirement types because assumptions lead to disasters in project execution.
β‘οΈ Avoid building solutions nobody needs by confirming and clarifying requirements across all relevant industries (health, construction, tech).
β‘οΈ Functional requirements define the features developers build, whereas nonfunctional requirements define the performance and quality attributes of the solution.
πΈ Video summarized with SummaryTube.com on Feb 21, 2026, 10:05 UTC
Find relevant products on Amazon related to this video
As an Amazon Associate, we earn from qualifying purchases

Summarize youtube video with AI directly from any YouTube video page. Save Time.
Install our free Chrome extension. Get expert level summaries with one click.