Requirements

Question 1

What are Requirements?

Answer 1

Definition: Describe system services & constraints

Process -> Finding -> Analyzing -> Documenting -> Checking.

Question 2

Types of Requirements

Answer 2

User Requirements -> What users think they need (natural language)

Issues -> Vague, mixed, unclear.

System Requirements -> Detailed how-to for implementation.

Forms part of the contract

Question 3

Functional vs. Non-Functional

Answer 3

✅ Functional = What the system does (inputs, outputs, behaviour).
⚠ Issues → Imprecise specs = shortcuts, misinterpretations.
✅ Non-Functional = How well it performs (speed, security, reliability).
⚠ Must be measurable → ❌ “Fast” → ✅ “10 ops/sec”.

Question 4

Challenges & Best Practices

Answer 4

🚩 Changing requirements = Project delays.
🚩 Too rigid = No flexibility or innovation.
🚩 Too detailed = Writing takes longer than coding.
✔ Use structured, quantifiable requirements.
✔ Track who requested each requirement.
✔ Separate “must-have” vs. “nice-to-have”.

Question 5

Key Takeaways

Answer 5

✅ User = What they want | System = How it’s built.
✅ Functional = What it does | Non-functional = How well it does it.
✅ Make everything clear, measurable & flexible.