Functional Point Analysis1

Software Testing and QA
By Aparna Naik www.DestinationQA.com
www.destinationqa.com
Agenda
What is Software Sizing Need for Software Sizing Software Sizing Methodologies Introduction to Function Point Analysis (FPA) Process of Counting Function Points Adjustment Factors in Function Point Analysis Function Point Count Types Case Study
Software Sizing
Software Sizing
Software sizing is an activity in software engineering that is used to estimate the size of a software application or component in order to be able to implement other software project management activities (such as estimating or tracking).
Size is an inherent characteristic of a piece of software just like weight is an inherent characteristic of a tangible material.
www.destinationqa.com 4
Need for Software Sizing
What do you see on the Surface?
The image represents the tip of an iceberg. The real issue is not the tip, but what is under the surface of the water and can not be seen. The same is true when you design a software application.
Airline Surface
This appears on the surface to be a simple inquiry, but this is extremely complex. The process actually includes 1,000s of elementary processes, but the end user is only exposed to a very simple process. All possible routes are calculated, city names are converted to their international three characters, interfaces are sent to all the airline carriers (each one being unique), this is an extremely complex and robust process! When we size software applications we want to understand what is exposed and what is under the surface.
7
Need for Software Sizing

Some common reasons for sizing the software are: 1. To Measure and Manage Productivity 2. Estimation and budgeting 3. Monitoring Progress 4. Evaluating Requirements coverage for buying new Software 5. Bidding for projects 6. Allocating Testing Resources 7. Risk Assessment 8. Phasing Development Work 9. Prioritizing Work 10. Software Asset Valuation 11. Outsourcing Software Development, Support or Maintenance. 12. CMMi Level 2 and 3 require that a valid sizing method be used.
Software Sizing Methodologies

Some of the common software sizing methodologies are:
1. Lines of Code (Oldest) 2. Use Case based Software Sizing 3. COSMIC - Common Software Measurement International Consortium (ISO) 4. IPFUG Function Point Analysis (ISO) 5. Mk II Function Point Analysis (ISO)
Software Sizing Lines of Code

Historically, the most common software sizing methodology has been counting the lines of code written in the application source Advantages: 1. Automation of the counting process is possible. 2. Intuitive - Can be seen and effect can be visualized. Disadvantages: 1. Lack of Accountability - The coding phase is only 30 - 35% of the total effort. 2. Very difficult to standardize lines of code for a particular function as it heavily depends on Skill level of the programmer, programming language, etc. 3. Lack of counting standards (Do comments count? Data Declarations? etc)
Hence a more mature Sizing Algorithm was needed.

11
History
The idea of measuring a size of software in terms of its functionality as opposed to its physical components was first put forward by Allan Albrecht of IBM in 1979 He proposed a method called Function Point Analysis which has since evolved into the IFPUG method. The definition of this method is now managed by the International Function Point Users Group. Albrechts clever piece of lateral thinking laid the foundations for the subject of functional size measurement. The IFPUG method actually has two components, firstly concerned with a measure of functional size and the second concerned with a measure of the contribution to overall size of 14 technical and quality factors. Albrechts original approach has been refined significantly over the last 30 years, but its basic concepts are unchanged from the mid 1970s. Nevertheless, the IFPUG method is still the most widely-used FSM method, albeit confined to the domain of business application software.
12
Developments of 1st Generation Methods

Several developments from the Albrecht/IFPUG approach have been made to improve the size measure, or to extend its domain of applicability. Capers Jones published a method based closely on that of Albrecht, called Feature Points, with the aim of extending FSM to apply to scientific algorithms. The method has been largely abandoned due to the intrinsic difficulty of sizing mathematical algorithms Charles Symons developed the MkII Function Point Method which aimed to improve on Albrechts approach by better taking into account the internal complexity of data-rich business application software.
13
Continued
Scott Whitmire developed 3D Function Points to size business application and real-time software drawing on Albrechts general approach.
The Netherlands Software Metrics Users Association (NESMA) published a variant of the IFPUG method which aimed to simplify some of the sizing rules The University of Qubec, Montral and others published the Full Function Point Method which used the IFPUG rules for business application software and added extra components for sizing real-time software. It will be seen that all of these methods can trace their roots back to Allan Albrechts original ideas. They are what we call 1st Generation FSM Methods.
14
Function Point Analysis
15
Introduction to Function Point Analysis

What is a Function Point?
A function point is a unit of measurement to express the amount of business functionality an information system provides to a user.
Some Definitions
1. Functional Size A size of the software derived by quantifying the Functional User Requirements. 2. Functional Size Measurement (FSM) The process of measuring Functional Size. 3. FSM Method A specific implementation of FSM defined by a set of rules, which conforms to the mandatory features of this part of ISO/IEC 14143. There are currently 5 ISO recognized FSM Methods.
16
Function Point Analysis - Characteristics

1. Measures Functional User Requirements 2. Excludes a. Physical or technical components b. Quality features 3. Derived in terms understood by users of the software. The measure relates directly to the business requirements, which the software is intended to address 4. Derived without reference to effort to develop or support. The Function Point technique provides an objective, comparative measure, which assists in the evaluation, planning, management and control of software production. 5. It is a method to break systems into smaller components, so they can be better understood and analysed. 6. It can therefore be readily applied across a wide range of development environments and throughout the life of a development project, from early requirements definition to full operational use.
Function points are a unit measure for software much like an hour is to measuring time, miles are to measuring distance
Function Point Unit Of Software

Function Points are the output of the software development process. Function points are the unit of software. It is very important to understand that Function Points remain constant regardless who develops the software or what language the software is develop in. Unit costs need to be examined very closely. To calculate average unit cost all items (units) are combined and divided by the total cost.
18
Unit Software example

For example, assume you are going to manufacture a computer mousepad. The total Cost to manufacture 1,000 mousepad is $2,660. The unit cost is $2.66 (per pad). The cost break down is: Artwork is a fixed cost at $500 (or .50 per unit) Set Up costs are $250 (or .25 per unit) Shipping costs are $10 (or .01 per unit) Papers for production will cost $1.50 per unit. Rubber Pads are $ .15 per unit. Application of paper to pad cost is $.25 per unit Notice the variation in the unit cost for each item. One of the biggest problems with estimating software projects is understanding unit cost. Software managers fail to break down items into similar components or like areas. They assume all units cost the same.
19
Counting Function Points
20
IPFUG FSM Counting Function Points

Function points are the units of measure used by the IFPUG Functional Size Measurement Method.
High Level Process

1. Identify Functional User Requirements. Categorize each one into one of the following types (Base Functional Components BFC): a. Transactional Functions i. Inputs ii. Outputs iii. Inquiries b. Data Functions i. Internal Files ii. External Interfaces 2. Rate each requirement based on complexity. Assign a Number for Function Points to each requirement. (Unadjusted function point count) 3. Determine the value adjustment factor (VAF) based on general system characteristics (GSCs). 4. Calculate the adjusted function point count. The final function point count (adjusted function point count) is a combination of both unadjusted function point count (UFP) and the general system characteristics (GSCs).
IPFUG FSM Identify Functional Requirements
22
IPFUG FSM Categorize into BFC
23
Example: External Interface
24
Functional point process
25
External Inputs
An elementary process in which data crosses the boundary from outside to inside. This data is coming external to the application. The data may come from a data input screen or another application. The data may be used to maintain one or more internal logical files. The data can be either control information or business information. If the data is control information it does not have to maintain an internal logical file. e.g. Data Input Fields, Error Messages, Calculated Values, Buttons
26
Identify External Inputs

The following words are associated with external input or inputs.
27
FTRs and DETs

The rating of External Input is based upon the number of data element types (DETs) and the file types referenced (FTRs). File Type Referenced (FTR): A FTR is a file type referenced by a transaction. An FTR must also be an internal logical file or external interface file. Each internal logical file that an external input maintains is counted as an FTR Data Element Type (DET): A DET is a unique user recognizable, non-recursive (non-repetitive) field. A DET is information that is dynamic and not static. A dynamic field is read from a file or created from DETs contained in a FTR. Additionally, a DET can invoke transactions or can be additional information regarding transactions.
28
Rating External Inputs (EI) Example
DETs Customer Name, Contact, Alt. Contact, Bill to, Phone, Fax, Alt. Phone, Ship To, OK button, Cancel Button FTR Customer file, Contact File, Bill To file, Ship To File
29
External Outputs
External Output is an elementary process in which derived data passes across the boundary from inside to outside. Additionally, an EO may update an ILF. The data creates reports or output files sent to other applications. These reports and files are created from information contained in one or more internal logical files and external interface files.
30
Identify External Output

The following words are associated with External Outputs
31
Rating External Outputs
32
Rating External Outputs Example Cnt.

There are 10 data elements 1. Days 2. Hits 3. % of Total Hits 4. User Sessions 5. Total Hits (weekday) 6. Total % (weekday) 7. Total User Sessions (weekday) 8. Total Hits (weekend) 9. Total % (weekend) 10. Total User Sessions (weekend) 3 FTR 1. Day Activity 2. Total Weekdays Activity 3. Total Weekend Activity
33
External Inquiry (EQ)

It is an elementary process with both input and output components that result in data retrieval from one or more internal logical files and external interface files. The input process does not update or maintain any FTRs (Internal Logical Files or External Interface Files) and the output side does not contain derived data.
34
Identify External Inquiries

The following words are associated with external Inquiries
35
Rating External Inquiry (EQ) Example
36
Internal Logical File

It is a user identifiable group of logically related data that resides entirely within the application boundary and is maintained through External Inputs. An internal logical file has the inherent meaning it is internally maintained, it has some logical structure and it is stored in a file. An ILF should have at least one external output and/or external inquiry. That is, at least one external output and/or external inquiry should include the ILF as an FTR An ILF should also have at least one external input.
37
Rating Internal Logical Files (ILF)

The rating is based upon the number of data elements (DETs) and the record types (RETs).
RET is logical group of data with recursion Most record element types are dependent on a parent child relationship.
38
Record Element Types

Some A are B
A All Customers B - Customers who havent paid in last 30 days
39
Record Element Types

All B are A
A All Customer data with Credit Card data B Credit Card Data
40
Rating ILF Example
41
External Interface File

It is a user identifiable group of logically related data that is used for reference purposes only. The data resides entirely outside the application boundary and is maintained by another applications external inputs. The external interface file is an internal logical file for another application. An application may count a file as either a EIF or ILF not both.
42
Unadjusted Function Point:
43
Adjustment Factors in Function Point Analysis
44
General System Characteristics

Definition: The value adjustment factor (VAF) is based on 14 general system characteristics (GSCs) that rate the general functionality of the application being counted. Each characteristic has associated descriptions to determine the degrees of influence. Rating:
The degrees of influence range on a scale of zero to five, from no influence to strong influence. Each characteristic is assigned the rating based upon detail descriptions provided by the IFPUG 4.1 Manual. They ratings are: 0 - Not present, or no influence 1 - Incidental influence 2 - Moderate influence 3 - Average influence 4 - Significant influence 5 - Strong influence throughout
General System Characteristics cont

1. Data communications: How many communication facilities are there to aid in the transfer or exchange of information with the application or system? 2. Distributed data processing: How are distributed data and processing functions handled? 3. Performance: Did the user require response time or throughput? 4. Heavily used configuration: How heavily used is the current hardware platform where the application will be executed? 5. Transaction rate: How frequently are transactions executed daily, weekly, monthly, etc.? 6. On-Line data entry: What percentage of the information is entered On-Line? 7. End-user efficiency: Was the application designed for end-user efficiency?
46
General System Characteristics cont

8. On-Line update How many ILFs are updated by On-Line transaction? 9. Complex processing Does the application have extensive logical or mathematical processing?
10. Reusability Was the application developed to meet one or many users needs?
11. Installation ease How difficult is conversion and installation?
12. Operational ease How effective and/or automated are start-up, back up, and recovery procedures?
13. Multiple sites Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations? 14. Facilitate change Was the application specifically designed,
47
Value Adjustment Factor (VAF)

Once all the 14 GSCs have been answered, they should be tabulated using the IFPUG Value Adjustment Equation (VAF)
48
Standard Function Point

The final Function Point Count is obtained by multiplying the VAF times the Unadjusted Function Point (UAF). The standard function point equation is:
FP = UAF * VAF
Where: UAF = Unadjusted Function Points VAF = Value Adjustment Factor
49
Function Point Count Types
50
Types Of Functional Point Counts
51
Types of FP Counts
Development Project Function Point Count
Function Points can be counted at all phases of a development project from requirements up to and including implementation. This type of count is associated with new development work. Scope creep can be tracked and monitored by understanding the functional size at all phase of a project. Frequently, this type of count is called a baseline function point count.
Enhancement Project Function Point Count

It is common to enhance software after it has been placed into production. This type of function point count tries to size enhancement projects. All production applications evolve over time. By tracking enhancement size and associated costs a historical database for your organization can be built. Additionally, it is important to understand how a development project has changed over time.
52
Types of FP Counts cont

Application Function Point Count
Application counts are done on existing production applications. This baseline count can be used with overall application metrics like total maintenance hours. This metric can be used to track maintenance hours per function point. This is an example of a normalized metric. It is not enough to examine only maintenance, but one must examine the ratio of maintenance hours to size of the application to get a true picture. Additionally, application counts can assist organizations in understanding the size of the entire corporate portfolio (or inventory). This type of count is analogous to taking an inventory for a store. Like inventory, a dollar value can be associated with any application function point count and for the entire organization portfolio.
53
Uses of FPA - Software Estimation

Estimation is not merely a technique, its an art
Accuracy of a software project estimate is Predicated on a number of things :
The degree to which the planner has properly estimated the size of the product to be built. The ability to translate the size estimate into human effort, calendar time, and dollar. The degree to which the project plan reflects the abilities of the software team. The stability of product requirements and the environment that supports the engineering effort.
54
S ize Based Estimation Model (Top Down)
In a top-down approach, the overall estimate for the project is first determined based on some models and then the estimates for different tasks are determined. E.g.: Function Point estimation which is a top down estimation technique is recognized as an industry standard scientific estimation technique that is acceptable to all stakeholders
55
56
57
Case Study Function Point Analysis
58
Case Study
The Weather Application The following application was designed to capture temperature and rainfall by city and state. There is only one input screen, one file and one report Each field on the following input screen can be modified (add, changed or deleted). The add and change functions are different. All previous entries viewed by using the scroll bar. Assume a VAF of 1.0.
59
Case Study
60
Case Study
61
Thank You
Aparna Naik Email: naik.aparna@destinationqa.com Tel: +91 99233 50980
62
Appendix
63
Data Element Types

Radio Buttons: Radio Buttons are treated as data element types. Within a group of, a frame, radio buttons the user has the option of selecting only one radio button; so only one data element type is counted for all the radio buttons contained in the frame. Check Boxes: Check Boxes differ from radio buttons in that more than one check box can be selected at a time. Each check box, within a frame, that can be selected should be treated as a data element. Command Buttons: Command buttons may specify an add, change, delete or inquire action. A button, like OK, may invoke several different types of transactions. A button like next may actually be the input side of an inquiry or another transaction.
64
Data Element Types Cont

Messages: There are three types of messages that are generated in a GUI application: error messages, confirmation messages and notification messages. Error messages and confirmation messages: indicate that an error has occurred or that a process will be or have been completed. They are not an elementary or independent process alone, but they are part of another elementary process. A message that would state, zip code is required would be an example of an error message. A message that would state, are you sure you want to delete customer is an example of a confirmation message. Neither type of message is treated as a unique external output, but each is treated as a data element for the appropriate transaction. On the other hand, a notification messages is a business type message. For example, you may try to withdraw from an ATM machine more money than you have in your account and you receive the dreaded message, You have insufficient funds to cover this transaction. This is the result of information being read from a file regarding your current balance and a conclusion being drawn. A notification message is treated as an External Output.
65
Need for Software Metrics

What does the customer want to know ? How big is it? How long will it take? How many people do we need? How much will it cost? How good is it?
66
High level process
67
Independence and Dependence

Since the rating of transactions is dependent on both information contained in the transactions and the number of files referenced, it is recommended that transactions are counted first. At the same time the transactions are counted a tally should be kept of all FTRs (file types referenced) that the transactions reference.
68
ESTABLISHING THE BOUNDARY

Identify the Boundary: Review the purpose of the function point count. Look at how and which applications maintain data. Identify the business areas that support the applications. The boundary may need to be adjusted once components have been identified. In practice the boundary may need to be revisited, as the overall application is better understood. Function point counts may need to be adjusted as you learn about the application. Standard Documentation: General Specification Documents Interface Documents Other metric reports Interviews with the users User Documentation Design Documentation Requirements Data flow diagrams
69
Benefits and Uses:

Function Points can be used to communicate more effectively with business user groups. Function points can be used to establish an inventory of all transactions and files of a current project or application.. Function Points can be used to size software applications. Sizing is an important component in determining productivity (outputs/inputs), predicting effort, understanding unit cost, so on and so forth. Unlike some other software metrics, different people can count function points at different times, to obtain the same measure within a reasonable margin of error. That is, the same conclusion will be drawn from the results. FPA can help organizations understand the unit cost of a software application or project. Once unit cost is understood tools, languages, platforms can be compared quantitatively instead of subjectively. This type of analysis is much easier to understand than technical information. That is, a non-technical user can easily understand Function Points.
70

Functional Point Analysis1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Functional Point Analysis1

Uploaded by

Copyright:

Available Formats

Software Testing and QA

By Aparna Naik www.DestinationQA.com

Need for Software Sizing

What do you see on the Surface?

Need for Software Sizing

Software Sizing Methodologies

Software Sizing Lines of Code

Hence a more mature Sizing Algorithm was needed.

Developments of 1st Generation Methods

Function Point Analysis

Introduction to Function Point Analysis

Function Point Analysis - Characteristics

Function Point Unit Of Software

Unit Software example

Counting Function Points

IPFUG FSM Counting Function Points

High Level Process

IPFUG FSM Identify Functional Requirements

IPFUG FSM Categorize into BFC

Example: External Interface

Functional point process

Identify External Inputs

FTRs and DETs

Rating External Inputs (EI) Example

Identify External Output

Rating External Outputs

Rating External Outputs Example Cnt.

External Inquiry (EQ)

Identify External Inquiries

Rating External Inquiry (EQ) Example

Internal Logical File

Rating Internal Logical Files (ILF)

Record Element Types

A All Customers B - Customers who havent paid in last 30 days

Record Element Types

Rating ILF Example

External Interface File

Unadjusted Function Point:

Adjustment Factors in Function Point Analysis

General System Characteristics

General System Characteristics cont

General System Characteristics cont

Value Adjustment Factor (VAF)

Standard Function Point

Where: UAF = Unadjusted Function Points VAF = Value Adjustment Factor

Function Point Count Types

Types Of Functional Point Counts

Enhancement Project Function Point Count

Types of FP Counts cont

Uses of FPA - Software Estimation

S ize Based Estimation Model (Top Down)

Case Study Function Point Analysis

Data Element Types

Data Element Types Cont

Need for Software Metrics

High level process

Independence and Dependence

ESTABLISHING THE BOUNDARY

Benefits and Uses:

You might also like