📘 Software Project Metrics: Metrics & Indicators

---

🔹 1. Definition

Software Project Metrics are quantitative measures used to assess, monitor, and control different aspects of a software project such as progress, quality, productivity, and cost.

👉 In simple words: They are numbers used to check how well a project is performing.

---

🔹 2. What are Indicators?

Indicators are derived values or signals obtained from metrics that help managers make decisions about the project status.

👉 In simple words:

• Metrics = raw measurements
• Indicators = interpreted results for decision-making

---

🔹 3. Difference Between Metrics and Indicators ⭐

Feature	Metrics	Indicators
Meaning	Direct measurement	Derived interpretation
Nature	Quantitative data	Decision-support signal
Purpose	Measure performance	Show project status
Example	Number of defects	High defect risk indicator

---

🔹 4. Types of Software Metrics

---

🔸 1. Product Metrics 📦

Measure software product characteristics.

Examples:

• Size (LOC – Lines of Code)
• Function Points
• Complexity
• Reliability

👉 Example:

• A system has 10,000 LOC

---

🔸 2. Process Metrics ⚙️

Measure software development process quality.

Examples:

• Development time
• Defect removal efficiency
• Testing effort

👉 Example:

• 80% defects found during testing phase

---

🔸 3. Project Metrics 📊

Measure overall project performance.

Examples:

• Cost variance
• Schedule variance
• Effort spent

👉 Example:

• Project is 10% behind schedule

---

🔹 5. Types of Indicators

---

🔸 1. Progress Indicators ⏱

• Show project completion status

👉 Example:

• 60% project completed

---

🔸 2. Quality Indicators ⭐

• Indicate software quality level

👉 Example:

• High defect rate = poor quality

---

🔸 3. Risk Indicators ⚠️

• Show possible project risks

👉 Example:

• Frequent requirement changes = high risk

---

🔸 4. Performance Indicators 🚀

• Measure productivity and efficiency

👉 Example:

• Low productivity = project delay risk

---

🔹 6. Important Software Metrics

---

🔸 1. Size-Oriented Metrics 📏

• Based on LOC (Lines of Code)

Productivity = LOC / Effort

---

🔸 2. Function-Oriented Metrics ⚙️

• Based on Function Points (FP)

---

🔸 3. Productivity Metrics 🚀

Productivity = Output / Effort

---

🔸 4. Quality Metrics ⭐

Defect Density = Defects / Size

---

🔹 7. Relationship Between Metrics & Indicators

👉 Flow:

Metrics → Analysis → Indicators → Decision Making

📌 Example:

• Metric: 50 defects found
• Indicator: High quality risk ⚠️
• Decision: Improve testing

---

🔹 8. Why Metrics & Indicators are Important

• Help in project tracking
• Improve decision-making
• Identify risks early
• Ensure quality control
• Improve productivity

---

🔹 9. Example (Simple)

Metric	Value	Indicator
Defects	100	High risk ⚠️
Progress	70%	On track ✅
Cost variance	+20%	Over budget ⚠️

---

🔹 10. Important Exam Points

• Metrics = raw measurements
• Indicators = interpreted results
• Used for monitoring and control
• Help in decision-making
• Types: product, process, project metrics

---

🔹 11. Short Summary

• Software metrics measure project performance quantitatively
• Indicators interpret metrics to show project status
• Both help managers in tracking, controlling, and improving software projects

---

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

Software project metrics are quantitative measures used to evaluate software development performance, while indicators are interpreted values derived from metrics that help in decision-making. Together, they assist in monitoring, controlling, and improving software projects.

---

🔹 13. Likely Exam Questions

1. Define software project metrics.
2. What are indicators in software projects?
3. Differentiate between metrics and indicators.
4. Explain types of software metrics.
5. What are quality indicators?
6. Why are metrics important in project management?
7. Draw relationship between metrics and indicators.