Practices
  Home arrow Practices arrow An Overview of Function Point Analysis
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
PRACTICES

An Overview of Function Point Analysis
By: Nandini Venugopalan
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 71
    2004-06-02

    Table of Contents:
  • An Overview of Function Point Analysis
  • The Five Major Components
  • Rating and Ranking the Components
  • Unadjusted Function Points

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    Web Buyers Guide
     
    ADVERTISEMENT

    TestComplete™ automates software testing for a fraction of what the big guys charge. Easy functional and load testing for all Windows, .NET, Java and Web apps. Download a free trial now.

    An Overview of Function Point Analysis
    (Page 1 of 4 )

    Function Point Analysis is a structured technique of classifying components of a system. It is a method used to break systems down into smaller components so that they can be better understood and analyzed. Function Point Analysis provides a structured technique for problem solving.

    In Function Point Analysis, systems are divided into five large classes. The first three classes are External Inputs, External Outputs and External/Data Inquiries. These classes or components transact against files and hence they are also called Transactions. The next two classes are Internal Logical Files and External Interface Files. The data is stored in these classes and they form the Logical Information.

    Objectives of Function Point Analysis:

    Function Points measure systems from a functional perspective and are independent of technology. Hence, regardless of technology, language, development method, or hardware/software used, the number of function points for a system will remain constant. The variable in Function Point Analysis is the amount of effort required to deliver a given set of function points. Therefore, function point analysis can be used to determine which environment/language/tool is more productive.

    1. Function point analysis can be used to determine which environment/language/tool is more productive.
    2. Function point analysis can provide a mechanism to track and monitor scope creep.
    3. Function point counts at the end of each phase/stage of a project can be compared to the function points actually delivered.
    4. If the number of function points has increased then there has been a scope creep.
    5. The number of function points that has increased or decreased defines the project growth.
    6. If the project has grown then it is a sure indication that the requirements haven’t been gathered well and there has been some scope creep.
    7. If the project growth has declined then the communication between the end-user and the development team has improved.

    Process of Counting Function Points:

    Function point analysis follows specific steps for counting:

    • Identification of the subsystem boundaries
    • Identification of the data functions (internal logical files and external interface files)
    • Identification of transactional functions (external inputs, external outputs and external inquiries)
    • Calculation of the Unadjusted Function Point (UAF) Count
    • Determination of the Value Adjustment Factor (VAF) using General System Characteristics (GSC)
    • Calculation of the final Function Point Count

    Establish the Subsystem Boundary:

    A project may include one or more applications or subsystems. Boundaries must be drawn to identify the external applications that interact with this project or the application that is being measured.

    More Practices Articles
    More By Nandini Venugopalan


     

       

    PRACTICES ARTICLES

    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas
    - Choosing the Right Team
    - Trees
    - Basic Array Searching in C++
    - Solving Problems with Recursion




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway