Phase 3 · Requirements Analysis & Documentation
TopicsFunctional vs Non-Functional Requirements
Part of the Business Analyst Roadmap.
Summary
Functional requirements describe what a system should do (specific behaviors); non-functional requirements describe how it should perform (speed, security, usability) — both are essential, and non-functional ones are easy to forget.
How to Learn This
- 1Classify 5 sample requirements as functional or non-functional.
- 2Learn to specify non-functional requirements concretely (e.g. 'loads in under 2 seconds').
- 3Understand why skipping non-functional requirements causes expensive rework late in development.
More topics in Requirements Analysis & Documentation
Business Requirements Document (BRD)Functional Requirements Document (FRD)User Stories & Acceptance CriteriaUse Cases & Use Case DiagramsRequirements Traceability Matrix (RTM)Requirements Prioritization (MoSCoW)Writing Clear, Testable RequirementsRequirements Validation & Sign-OffManaging Requirement Changes
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.