Project Estimation

Date:

Version:

Estimation approach

Consider the GeoControl project as described in the swagger, assume that you are going to develop the project INDEPENDENT of the deadlines of the course, and from scratch

Estimate by size

Estimate
NC = Estimated number of classes to be developed 10
A = Estimated average size per class, in LOC 200
S = Estimated size of project, in LOC (= NC * A) 2000 LOC
E = Estimated effort, in person hours (here use productivity 10 LOC per person hour) 200 hours/person
C = Estimated cost, in euro (here use 1 person hour cost = 30 euro) 6000
Estimated calendar time, in calendar weeks (Assume team of 4 people, 8 hours per day, 5 days per week ) 1.25 weeks

Estimate by product decomposition

component name Estimated effort (person hours)
requirement document 30
design document 30
code 100
unit tests 40
api tests 40
management documents 20

Estimate by activity decomposition

Activity name Estimated effort (person hours)
Analysis & specification 60
Design & architecture 40
Implementation (backend) 100
Integration & Testing 60
Deployment & Documentation 40

Activity Week 1 Week 2 Week 3 Week 4 L M M G V L M M G V L M M G V L M M G V

  1. Analysis & Specification █ █ █ █ █
  2. Design & Architecture █ █ █ █ █ █
  3. Implementation █ █ █ █ █ █ █ █ █
  4. Integration & Testing █ █ █ █ █
  5. Deployment & Documentation █ █ █ █

Summary

Report here the results of the three estimation approaches. The estimates may differ. Discuss here the possible reasons for the difference

Estimated effort Estimated duration
estimate by size 200 1.25 weeks
estimate by product decomposition 260 1.60 weeks
estimate by activity decomposition 300 1.90 weeks