📘 Project Metrics & Software Project Estimation
(Software Project Management – Exam Notes)
🔹 1. Project Metrics
🔸 Definition
Project metrics are quantitative measures used to evaluate, monitor, and control software project performance.
👉 In simple words:
They are numbers that tell how well the project is performing.
🔸 Purpose of Project Metrics
- Measure project progress
- Improve productivity
- Track cost and time performance
- Ensure software quality
- Support decision-making
🔸 Types of Project Metrics
🔹 1. Size-Oriented Metrics 📏
Measure software size in terms of lines of code (LOC).
Example Metrics:
- LOC (Lines of Code)
- Cost per LOC
Formula:
Productivity = LOC / Effort
👉 Example:
1000 LOC / 10 person-days = 100 LOC/day
🔹 2. Function-Oriented Metrics ⚙️
Measure software based on functionality delivered.
Key Metric:
👉 Focus:
- Inputs
- Outputs
- Files
- Queries
- Interfaces
🔹 3. Productivity Metrics 🚀
Measure output per unit effort.
Formula:
Productivity = Output / Effort
👉 Example:
- 2000 LOC / 20 days = 100 LOC/day
🔹 4. Quality Metrics ⭐
Measure software quality.
Examples:
- Defect density
- Error rate
- Customer satisfaction
Formula:
Defect Density = Number of Defects / Size of Software
🔹 5. Cost Metrics 💰
Measure project cost efficiency.
Example:
- Cost per function point
- Cost per LOC
🔹 2. Software Project Estimation
🔸 Definition
Software project estimation is the process of predicting effort, cost, time, and resources required to complete a software project.
👉 In simple words:
It answers: “How much time, money, and effort will the project need?”
🔸 What is Estimated?
- ⏱ Effort (person-days/months)
- 📅 Time (duration)
- 💰 Cost (budget)
- 👨💻 Resources (team size)
🔸 Importance of Estimation
- Helps in project planning
- Prevents cost overruns
- Ensures realistic deadlines
- Improves resource allocation
- Reduces project failure risk
🔹 3. Techniques of Software Estimation
🔸 1. Expert Judgment 👨💼
- Based on experience of experts
- Fast but subjective
🔸 2. Analogous Estimation 📊
- Uses similar past projects
🔸 3. Parametric Estimation 📐
- Uses mathematical formulas
Example:
Effort = Size / Productivity
🔸 4. COCOMO Model ⭐ (Important)
COCOMO Model is a popular algorithmic model for estimating effort and cost.
Basic Idea:
Effort = a × (KLOC)^b
👉 Where:
- KLOC = Thousand Lines of Code
- a, b = constants depending on project type
🔸 5. Three-Point Estimation (PERT) 🎯
Uses:
- Optimistic (O)
- Most Likely (M)
- Pessimistic (P)
Formula:
TE = (O + 4M + P) / 6
🔹 4. Relationship Between Metrics & Estimation
- Metrics provide historical data
- Estimation uses this data to predict future effort
- Better metrics → more accurate estimation
🔹 5. Key Differences
| Feature |
Project Metrics |
Project Estimation |
| Meaning |
Measurement of performance |
Prediction of effort/time |
| Type |
Actual data |
Future prediction |
| Use |
Monitoring |
Planning |
| Example |
Defect rate |
Project cost |
🔹 6. Important Exam Points
- Metrics = measure performance
- Estimation = predict project requirements
- Estimation depends on metrics + experience
- COCOMO is a widely used estimation model
- Both are essential for successful project management
🔹 7. Short Summary
- Project metrics measure software performance (cost, quality, productivity).
- Software estimation predicts effort, cost, and time.
- Both are essential for planning, controlling, and delivering successful software projects.
🔹 8. Quick Exam Answer (2–3 lines)
Project metrics are quantitative measures used to evaluate software performance, while software project estimation is the process of predicting effort, time, and cost required for project completion. Both help in effective planning and control of software projects.
🔹 9. Likely Exam Questions
- Define project metrics.
- What is software project estimation?
- Differentiate between metrics and estimation.
- Explain types of software metrics.
- What is COCOMO model?
- Write formula for PERT estimation.
- Why is estimation important in software projects?