| |
|
Knowing the software size facilitates the
creation of more accurate estimates of project resources
and delivery dates. Software metrics
allows you to do this early in the project life
cycle, before you've outlaid most of your cost. Management can then make
informed decisions whether to proceed, reduce scope or not
to proceed.
- Project Scoping
You can functionally decompose your software into its
elementary functional components,
providing a graphical map of the application to be delivered. This can
convey the scope of the application to the user, illustrating the number
of processes delivered by each functional area as well as the comparative
size of each functional area.
- Negotiating Scope
Processes can be easily identified and flagged as mandatory, essential or
optional. This allows users to make informed decisions on which
functionality is to be included in each release of the application based
on their priority, given the time, cost and resource constraints of the
project. The project size can then be measured given the different
scenarios.
- Estimating Project Resource
Requirements
Once the scope of the project is agreed, and if the productivity rates
(hours per Function Point, $cost per
Function point) from previous projects are known, the project manager can
use the Function Point count to develop appropriate estimates.
More Benefits |
|
