📘 Problem-Based Estimation (Software Project Management)

---

🔹 1. Definition

Problem-Based Estimation is a software estimation technique in which the project is analyzed based on the problem to be solved, and the effort, cost, and time are estimated by understanding the problem size, complexity, and requirements.

👉 In simple words: It means estimating a project by first understanding the problem and then breaking it into measurable parts.

---

🔹 2. Key Idea ⭐

Problem → Analyze Requirements → Break into Parts → Estimate Effort → Total Estimate

Unlike other methods, it focuses on:

• Problem complexity
• User requirements
• System behavior

---

🔹 3. Steps in Problem-Based Estimation

---

🔸 Step 1: Understand the Problem

• Study user requirements
• Identify objectives and constraints

---

🔸 Step 2: Break Down the Problem

• Divide into smaller modules (WBS) 👉 Example:
• Login system
• Payment module
• Report generation

---

🔸 Step 3: Analyze Each Component

• Identify complexity:

  • Simple
  • Medium
  • Complex

---

🔸 Step 4: Estimate Each Module

• Assign effort/time to each part
• Use expert judgment or historical data

---

🔸 Step 5: Combine Estimates

• Add all module estimates
• Include buffer for risk

---

🔹 4. Diagram Description

📊 Problem-based estimation flow:

Problem Definition
      ↓
Requirement Analysis
      ↓
Decomposition (Modules)
      ↓
Module-wise Estimation
      ↓
Total Project Estimate

---

🔹 5. Characteristics

• Focuses on problem understanding
• Uses top-down analysis approach
• Based on system functionality and complexity
• Combines technical + user perspective

---

🔹 6. Example

Problem: Develop an Online Banking System

Breakdown:

• User login system
• Account management
• Fund transfer
• Transaction history

Estimation:

Module	Effort
Login	3 days
Accounts	5 days
Transfer	6 days
Reports	4 days

👉 Total Effort = 18 days

---

🔹 7. Advantages

✔ Easy to understand initial project scope ✔ Helps in early estimation ✔ Considers real user requirements ✔ Useful for complex systems ✔ Improves planning accuracy

---

🔹 8. Limitations ❌

• Depends on accurate requirement analysis
• Early estimates may be uncertain
• Requires experienced estimators
• Not very precise for highly dynamic projects

---

🔹 9. Problem-Based vs Decomposition-Based Estimation

Feature	Problem-Based	Decomposition-Based
Focus	Problem understanding	Task breakdown
Approach	Top-down	Bottom-up
Basis	Requirements	Modules/WBS
Accuracy	Medium	High
Stage	Early estimation	Detailed planning

---

🔹 10. Importance

• Helps in initial project planning
• Useful when detailed data is not available
• Bridges gap between user needs and technical design
• Supports decision-making in early stages

---

🔹 11. Key Exam Points

• Based on understanding the problem
• Uses top-down approach
• Breaks problem into smaller modules
• Estimates each module separately
• Combines all estimates for final result

---

🔹 12. Short Summary

• Problem-based estimation focuses on analyzing the problem and requirements
• The project is divided into smaller components, each estimated separately
• Final estimate is obtained by combining all module estimates

---

🔹 13. Quick Exam Answer (2–3 lines)

Problem-based estimation is a software estimation technique where the project is analyzed based on the problem requirements and broken into smaller components. Each component is estimated separately and combined to get the total project effort, cost, and time.

---

🔹 14. Likely Exam Questions

1. Define problem-based estimation.
2. Explain steps of problem-based estimation.
3. What are its advantages?
4. Differentiate between problem-based and decomposition-based estimation.
5. Why is problem-based estimation useful in early stages?
6. Draw diagram of problem-based estimation process.