PARKADE – Smart Parking Management System
Phase 3: Project Estimation
1. Introduction
This document presents the estimation of effort, cost, schedule, and staffing required to
develop the Parkade Smart Parking Management System. Parkade is a web-based platform
that connects drivers with available parking spaces and allows owners to manage their
listings.
To ensure accurate estimation, the following standard software engineering techniques are
applied:
Function Point Analysis (FPA) – to determine system size
Detailed COCOMO – to estimate effort and development time
PERT Chart – to model task dependencies and schedule
Jordan’s Algorithm – to optimize team allocation and workload
The estimation includes all core functionalities such as authentication, parking search,
booking, payment processing, and administrative control.
2. Function Point Analysis (FPA)
Function Point Analysis is used to evaluate the size of the system based on its functional
components rather than implementation details.
2.1 Functional Components
The system is divided into:
External Inputs (EI): user actions like login, booking, payment
External Outputs (EO): confirmations, reports, notifications
External Inquiries (EQ): data retrieval operations
Internal Logical Files (ILF): system-managed data (users, bookings, payments)
External Interface Files (EIF): third-party APIs like payment gateway and maps
2.2 Unadjusted Function Points (UFP)
After assigning weights to all identified components, the total UFP is:
UFP = 238
2.3 Value Adjustment Factor (VAF)
Based on system characteristics such as performance, security, and online data handling:
Total Degree of Influence (DI) = 41
VAF = (0.01 × 41) + 0.65 = 1.06
2.4 Adjusted Function Points
[
AFP = UFP \times VAF = 238 \times 1.06 = 252
]
So, the final size of the system is 252 Function Points.
2.5 LOC Estimation
Using standard conversion ratios:
Frontend (React): ~4,646 LOC
Backend ([Link]): ~6,215 LOC
Database (SQL): ~1,102 LOC
Total LOC ≈ 12,000 lines of code
3. Detailed COCOMO Estimation
The COCOMO model is used to estimate development effort and duration.
3.1 Project Classification
Mode: Semi-Detached
Size: ~12 KLOC
Development type: Structured web application
3.2 Effort Estimation
[
E = a \times (KLOC)^b
]
[
E = 3.0 \times (12)^{1.12} = 49.23 \text{ PM}
]
After applying Effort Adjustment Factor (EAF = 0.720):
[
E_{adjusted} = 49.23 \times 0.720 = 35.44 \text{ PM}
]
3.3 Development Time
[
T = 2.5 \times (E)^{0.35}
]
[
T = 2.5 \times (35.44)^{0.35} ≈ 8 \text{ months}
]
3.4 Team Size
[
Team = \frac{Effort}{Time} = \frac{35.44}{8} ≈ 4–5 \text{ members}
]
3.5 Cost Estimation
Assuming $3000 per person-month:
Development cost = $106,320
Infrastructure + APIs = $2,000
Contingency (10%) = $10,832
Total Cost ≈ $119,152
4. PERT Chart (Scheduling)
PERT is used to model task dependencies and estimate project duration.
Each task is assigned:
Optimistic (O)
Most likely (M)
Pessimistic (P)
Expected time:
[
T_e = \frac{O + 4M + P}{6}
]
4.1 Critical Path
The longest dependency chain is:
T1 → T2 → T5 → T7 → T8 → T13 → T19 → T20 → T21 → T22
Total duration ≈ 74 days (~3.7 months)
Any delay in these tasks will directly impact the overall project timeline.
4.2 Project Completion Probability
Standard deviation ≈ 4.11 days
90% completion ≈ 80 days
95% completion ≈ 81 days
This indicates a high probability of completing within the estimated schedule.
5. Staff Scheduling (Jordan’s Algorithm)
Jordan’s Algorithm is applied to distribute workload evenly across the project timeline while
respecting dependencies.
5.1 Approach
Tasks with zero float are scheduled first
Tasks with flexibility are shifted to reduce workload peaks
Resource usage is balanced across all phases
5.2 Team Structure
Academic team:
3 members working as full-stack developers
Industry model:
1 Project Manager
2–3 Developers
1 QA Engineer
5.3 Resource Utilization
Weekly utilization ranges between 87% to 100%
Workload is evenly distributed
No extreme peaks or underutilization observed
Jordan’s algorithm successfully smooths resource allocation throughout development.
6. Summary
Metric Value
Function Points 252 FP
LOC ~12,000
Effort 35.44 PM
Duration ~8 months
Team Size 4–5 members
Cost $119,152
Critical Path Defined via PERT
Resource Utilization 87–100%
7. Conclusion
The Parkade system is estimated to require approximately 35.44 person-months of effort
and can be completed in about 8 months with a small development team.
The most critical components include authentication, booking logic, payment integration,
and system testing. These require close monitoring to avoid delays.
By applying Jordan’s Algorithm, the team workload remains balanced, ensuring efficient use
of resources without overload.
Overall, the estimation shows that the project is feasible within the defined timeline and
resource constraints.