In general, this kind of work involves a very limited scope. As a result, it is difficult to establish a relationship between the functional size and others metrics such as effort, time and COST. However, it´s important to remember that Function Point Analysis (FPA) is not simply a TOOL for generating estimates, used in project planning. The nature of the work involved in this question is characterized not as a project, but as a continuous operation.

Take as an example the systems maintenance with estimated effort up to 200 hours. Separately, the sizing of orders that represent the requirements (not ALWAYS functional) object maintenance may not have a linear relationship with the effort involved for its ACHIEVEMENT. However, taking into account the knowledge with all of the requests in a given period of time, we can arrive at different conclusions.

For example, a given maintenance request did not involve the addition, modification or elimination of certain system features. In this case, it is USELESS to know that the main-tenance functional size will have no function points. But the system that gives mainte-nance has a functional size. You can monitor the amount of maintenance hours per function points of this system. This trend helps to evaluate whether or not it is time to replace this system with a new one.

Suppose that there is a process in this organization where, after the service order has been served by the maintenance team, the product goes through an approval process. The feature set in the approval may be scaled in terms of function points. Likewise, the amount of identified defects in the process can be documented. Monitoring the interaction of these two metrics — Function Point and Defects — during a period of time can bring out problems in the maintenance process. Based on this trend it is pos-sible to take actions to reduce this relation.

In general, this kind of work involves a very limited scope. As a result, it is difficult to establish a relationship between the functional size and others metrics such as effort, time and cost. However, it´s important to remember that Function Point Analysis (FPA) is not simply a tool for generating estimates, used in project planning. The nature of the work involved in this question is characterized not as a project, but as a continuous operation.

Take as an example the systems maintenance with estimated effort up to 200 hours. Separately, the sizing of orders that represent the requirements (not always functional) object maintenance may not have a linear relationship with the effort involved for its achievement. However, taking into account the knowledge with all of the requests in a given period of time, we can arrive at different conclusions.

For example, a given maintenance request did not involve the addition, modification or elimination of certain system features. In this case, it is useless to know that the main-tenance functional size will have no function points. But the system that gives mainte-nance has a functional size. You can monitor the amount of maintenance hours per function points of this system. This trend helps to evaluate whether or not it is time to replace this system with a new one.

Suppose that there is a process in this organization where, after the service order has been served by the maintenance team, the product goes through an approval process. The feature set in the approval may be scaled in terms of function points. Likewise, the amount of identified defects in the process can be documented. Monitoring the interaction of these two metrics — Function Point and Defects — during a period of time can bring out problems in the maintenance process. Based on this trend it is pos-sible to take actions to reduce this relation.