28/09/2025
How to do Requirements Analysis (Step-by-Step)
----------------------------------------------------------
Here’s a simple step-by-step guide:
1. Collect Requirements: Talk to people who will use the system:
- Ask questions.
- Watch how they currently do things.
- Use surveys, interviews, or brainstorming sessions.
Example: Ask a restaurant owner: “What do you expect from a food delivery app?”
2. Write Down Everything Clearly
Make the requirements simple and clear.
❌ Bad: “The app should be fast.”
✅ Good: “The app should load the homepage in less than 3 seconds.”
3. Categorize Requirements
Split into types:
- Functional requirements – what the system should do.
- Non-functional requirements – how the system should perform (speed, security, usability).
Example:
Functional: “User can search for restaurants.”
Non-functional: “The search results must appear in under 2 seconds.”
4. Remove Conflicts or Duplicates
Sometimes different users give conflicting requirements. You need to resolve them.
Example:
User A: Wants only cash payment.
User B: Wants only online payment.
You decide to support both options.
5. Prioritize Requirements
Not everything can be built at once. Decide:
1. What is must-have
2. What is nice-to-have
3. What can wait for later
6. Get Confirmation
Review everything with the users or stakeholders:
1. “Is this what you want?”
2. Make sure they agree before development starts.
Real-life Analogy
-----------------------
Think of building a house. Before construction:
1. You talk to the family (users).
2. Ask how many bedrooms they want.
3. Check their budget.
4. Decide what’s essential (kitchen, bathroom) vs. optional (swimming pool).
5. Create a blueprint.
Just like that, requirements analysis is the planning step before building software.
