Function Point Analysis FPA on A Team Planning Website Based on PHP and MYSQL

Anders L

doi:10.4172/2165-7866.1000237

Abstract

A function point analysis (FPA) has been carried out on a custom team planning website based on PHP and MYSQL. The FPA was done after the development was finished (retrospective) and a constructive cost model analysis (COCOMO) was carried out to asses source lines of code (SLOC). In the present study the function point analysis is based on entities of the relational database evaluated as internal logical files, and evaluation of PHP source code with dynamic SQL as either external input files or external inquiry files. The complexity for a custom team planning website was found to be 510 total adjusted function points (TAFP) (UAF=580 FP, TDI=23, VAF=0, 88, TAFP=510FP). The function point estimate was classified as an organic project in a COCOMO analysis, and it was concluded that the complexity corresponds to 27742 LOC (or 27, 4 KDSI). The estimate of 66-82 person-months project would correspond to a 4 crew team in 16-21 months. The estimate was compared to the actual source code count of 22300 LOC.

Highlights

Function point analysis (FPA) is one way to determine the overall complexity of a system
The unadjusted function points can be adjusted for technical complexity as the total adjusted function points (TAFP). It is this measure that can be converted to project size in terms of man years based on lines of code (LOC) for the used programming language [11]
The Internal Logical File complexity holds for the number of files/entities, but the complexity (LOW; AVERAGE; HIGH) could be overestimated for a smaller custom website

Summary

Introduction

Function point analysis (FPA) is one way to determine the overall complexity of a system. Made a literature review based on reported keywords identifying improvements to the accuracy of function point analysis [8]. The FPA Allows for quantifying different properties of the system, in LOW, AVERAGE or HIGH complexity, totaling the unadjusted function points (UAF). The unadjusted function points can be adjusted for technical complexity as the total adjusted function points (TAFP) It is this measure that can be converted to project size in terms of man years based on lines of code (LOC) for the used programming language [11]. Comparing the Total Adjusted Function Points to Delivered Source Lines of Code (SLOC), similar to the two step work effort validation [2] (Figure 1)

Method

Results

Discussion

Conclusion