27-12-2012, 04:37 PM
Metrics for Project Size Estimation
Metrics for Project.ppt (Size: 210.5 KB / Downloads: 30)
Project Size
IS NOT:
- Bytes source code occupies, executables occupy
IS:
- Measure of problem complexity in terms of time and effort required to develop product
LINES OF CODE (LOC)
The simplest among all metrics available to estimate project size
Project size estimated by counting the number of source instructions
Lines used for commenting, header lines ignored
To find LOC at the beginning of a project divide module into sub modules and so on until size of each module can be predicted
Function Point Metric
Size of Function Point (FP)= Weighted sum of
these five problem characteristics
1. Number of inputs: Data items input by user
(Group of user inputs taken together)
2. Number of Outputs: Reports, Screen outputs,
Error Messages
3. Number of inquiries: Interactive queries made
by users. user system
4. Number of Files: Logical files e.g. data
structures, physical files
5. Number of interfaces: Interfaces for
exchanging information e.g. disk, tapes,
communication links
Business Risks
- Excellent product but no one wants!!
- Losing budgetary commitment
- Losing personnel commitment
Risk Assessment
Risk exposure can be computed for each risk in risk table, once an estimate of cost of risk is made.
The total risk exposure for all risks (above the cutoff in the risk table) can provide a means for adjusting the final cost estimate for a project.
Case Study
For example, assume that software team defines a project risk in as follows:
Risk Identification: Only 70 percent of the software components scheduled for reuse will, in fact, be integrated into the application. The remaining functionality will have to be custom developed.
Risk Probability: 80% (likely)
The average component is 100 LOC and local data indicate that the software engineering cost for each LOC is $14.00
Risk Containment
Plans to suppress the most damaging and most likely
risks:
Avoid the risk
- discussion with customer and reduce scope of
work
- provide incentives to engineers to avoid
employee turnover
2. Transfer the Risk
- get the risky component developed by a third
party
Risk Reduction
- Plan ways to contain the damage due to a risk
Some key personnel might leave Plan new recruitment