|
Home
ISSUE
Where a function point count is constrained by time limitations and a lack of relevant documentation, how should functional complexity be determined?
GENERAL DISCUSSION On occasion, a function point count may be seriously impeded by time constraints and/or a lack of relevant documentation. Under these circumstances, it is considered impractical to perform a complete and accurate count, as the time and effort involved in counting would often outweigh the benefits derivable from the count. It is therefore pragmatic to adopt a short-cut approach to counting using industry standard weightings, which are as follows:
| Functional Type
|
Weighting
|
| External Input |
AVE
|
| External Output |
AVE
|
| External Enquiry |
AVE
|
| Internal Logical File |
LOW
|
| External Interface File |
LOW
|
However, these weightings may be adjusted as appropriate based on the unique characteristics of the system being counted. For example, the EO functions of a Robot application typically would be assigned HIGH complexity.
It must be noted, however, that this approach is considered most appropriate for application baselines and when counting projects based upon packaged software. When counting enhancement projects, the smaller size of the counts, and access to recently produced specifications, usually enable the FP Analyst to accurately assess functional complexity.
|
