1. Software Project Estimation Determining the Cost of Your Project

2. Estimation Activities Scoping the project Determined in conjunction with the customer Use narrative descriptions and use cases Identifying the resources Major resource categories People (number, skill, availability, location) Environment (s/w, h/w, network, familiarity, availability) Other (time, funding, s/w components, technical resources) Decomposing the problems (see next slide) Use empirical models (past experience) Consider impact Dev Process on schedule Determine how much you need of each resource

3. Decomposition Size-Based Estimates LOC Number of Subsystems, Classes, Use Cases, etc. Function-Based Estimates Decompose function of system into features until reasonable confidence achieved on estimate Use three-point estimate as “hedge” against uncertainty (see pg 700 7/e, 651 6/e) Reconcile Estimates

4. Make/Buy Decision Not fully applicable in CS4810/EGCP4810 Choices Cancel – Do without Reuse – Make due Make – Build what you need Contract – Have another build it for you Buy – Purchase what is already built Each choice has pros/cons according to how it meets your exact needs

5. Additional Points of Emphasis Empirical estimation models (pgs 708- 712 7/e, 659-663 6/e) can be invaluable and a business edge for repeated work See the process-based estimation chart on pg 704 7/e, 655 6/e for an example on estimating schedule