Scribd Logo
Upload

Welcome to Scribd!

    • 376 views

    Functional Point Analysis 1679309233589

    Uploaded by

    Narsini AKSHARA
    Functional Point (FP) Analysis is a method of estimating the size of a software application based on its functionality. It was initially developed by Allan J. Albrecht in 1979 at IBM. FPs measure different elements of an application including external inputs, outputs, inquiries, internal files, and external interfaces. These elements are assigned weighting factors and counted to determine the total function points. The function points are then adjusted based on complexity factors to estimate the effort required to develop the application. FP analysis allows software size to be measured independently of the programming language used, and can be used to estimate metrics like productivity, documentation needs, and cost.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Functional Point Analysis 1679309233589

    Uploaded by

    Narsini AKSHARA
    376 views6 pages
    Functional Point (FP) Analysis is a method of estimating the size of a software application based on its functionality. It was initially developed by Allan J. Albrecht in 1979 at IBM. FPs measure different elements of an application including external inputs, outputs, inquiries, internal files, and external interfaces. These elements are assigned weighting factors and counted to determine the total function points. The function points are then adjusted based on complexity factors to estimate the effort required to develop the application. FP analysis allows software size to be measured independently of the programming language used, and can be used to estimate metrics like productivity, documentation needs, and cost.

    Original Title

    Functional_Point_analysis_1679309233589

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Functional Point (FP) Analysis is a method of estimating the size of a software application based on its functionality. It was initially developed by Allan J. Albrecht in 1979 at IBM. FPs measure different elements of an application including external inputs, outputs, inquiries, internal files, and external interfaces. These elements are assigned weighting factors and counted to determine the total function points. The function points are then adjusted based on complexity factors to estimate the effort required to develop the application. FP analysis allows software size to be measured independently of the programming language used, and can be used to estimate metrics like productivity, documentation needs, and cost.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    376 views6 pages

    Functional Point Analysis 1679309233589

    Uploaded by

    Narsini AKSHARA
    Functional Point (FP) Analysis is a method of estimating the size of a software application based on its functionality. It was initially developed by Allan J. Albrecht in 1979 at IBM. FPs measure different elements of an application including external inputs, outputs, inquiries, internal files, and external interfaces. These elements are assigned weighting factors and counted to determine the total function points. The function points are then adjusted based on complexity factors to estimate the effort required to develop the application. FP analysis allows software size to be measured independently of the programming language used, and can be used to estimate metrics like productivity, documentation needs, and cost.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 6

    Functional Point (FP) Analysis

    Allan J. Albrecht initially developed function Point Analysis in 1979 at IBM and it has
    been further modified by the International Function Point Users Group (IFPUG). FPA
    is used to make estimate of the software project, including its testing in terms of
    functionality or function size of the software product. However, functional point
    analysis may be used for the test estimation of the product. The functional size of the
    product is measured in terms of the function point, which is a standard of
    measurement to measure the software application.

    Objectives of FPA
    The basic and primary purpose of the functional point analysis is to measure and
    provide the software application functional size to the client, customer, and the
    stakeholder on their request. Further, it is used to measure the software project
    development along with its maintenance, consistently throughout the project
    irrespective of the tools and the technologies.

    Following are the points regarding FPs

    1. FPs of an application is found out by counting the number and types of functions
    used in the applications. Various functions used in an application can be put under
    five types, as shown in Table:

    Measurements Parameters Examples

    1.Number of External Inputs(EI) Input screen and tables

    2. Number of External Output (EO) Output screens and reports

    3. Number of external inquiries (EQ) Prompts and interrupts.

    4. Number of internal files (ILF) Databases and directories

    5. Number of external interfaces (EIF) Shared databases and shared routines.

    All these parameters are then individually assessed for complexity.

    The FPA functional units are shown in Fig:


    2. FP characterizes the complexity of the software system and hence can be used to
    depict the project time and the manpower requirement.

    3. The effort required to develop the project depends on what the software does.

    4. FP is programming language independent.

    5. FP method is used for data processing systems, business systems like information
    systems.

    6. The five parameters mentioned above are also known as information domain
    characteristics.
    The Function Point (FP) is thus calculated with the following formula.

      FP = Count-total * [0.65 + 0.01 * ∑(f i)]


                  = Count-total * CAF

    where Count-total is obtained from the above Table.

                  CAF = [0.65 + 0.01 *∑(fi)]

    and ∑(fi) is the sum of all 14 questionnaires and show the complexity adjustment
    value/ factor-CAF (where i ranges from 1 to 14). Usually, a student is provided with
    the value of ∑(fi)
    Based on the FP measure of software many other metrics can be computed:

    a. Errors/FP
    b. $/FP.
    c. Defects/FP
    d. Pages of documentation/FP
    e. Errors/PM.
    f. Productivity = FP/PM (effort is measured in person-months).
    g. $/Page of Documentation.

    8. LOCs of an application can be estimated from FPs. That is, they are
    interconvertible. This process is known as backfiring. For example, 1 FP is equal to
    about 100 lines of COBOL code.

    Example: Compute the function point, productivity, documentation, cost per


    function for the following data:

    1. Number of user inputs = 24


    2. Number of user outputs = 46
    3. Number of inquiries = 8
    4. Number of files = 4
    5. Number of external interfaces = 2
    6. Effort = 36.9 p-m
    7. Technical documents = 265 pages
    8. User documents = 122 pages
    9. Cost = $7744/ month

    Various processing complexity factors are: 4, 1, 0, 3, 3, 5, 4, 4, 3, 3, 2, 2, 4, 5.

    Solution:

    Measurement Parameter Coun Weighing


    t factor

    1. Number of external inputs (EI) 24 * 4 = 96

    2. Number of external outputs (EO) 46 * 4 = 184

    3. Number of external inquiries (EQ) 8 * 6 = 48

    4. Number of internal files (ILF) 4 * 10 = 40

    5. Number of external interfaces (EIF) Count-total 2 * 5 = 10


    → 378
    So sum of all fi (i ← 1 to 14) = 4 + 1 + 0 + 3 + 5 + 4 + 4 + 3 + 3 + 2 + 2 + 4 + 5 = 43

                    FP = Count-total * [0.65 + 0.01 *∑(fi)]


                    = 378 * [0.65 + 0.01 * 43]
                    = 378 * [0.65 + 0.43]
                    = 378 * 1.08 = 408

    Total pages of documentation = technical document + user document


                    = 265 + 122 = 387pages

    Documentation = Pages of documentation/FP


                    = 387/408 = 0.94

    Differentiate between FP and LOC

    FP LOC

    1. FP is specification based. 1. LOC is an analogy based.

    2. FP is language independent. 2. LOC is language dependent.

    3. FP is user-oriented. 3. LOC is design-oriented.

    4. It is extendible to LOC. 4. It is convertible to FP (backfiring)

    You might also like