Function Point Analysis

Image

An exact replication of another object, file, or table that is usually created through a utility

Entity

Any distinguishable person, place, thing, event, or concept about which information is kept A thing that can be distinctly identified Any distinguishable object that is to be represented in a database A data entity that represents some "thing" that is to be stored for later reference Anything about which we store information

Processing Logic

Any of the requirements specifically requested by the user to complete an elementary process such as validations, algorithms, or calculations and reading or maintaining a data function

Reference Data Logical Characteristics

Data is mandatory for operation of the users' functional area Data is user identifiable (usually by a business user) Data is usually user maintainable (usually by an administrative user) Data is usually established when the application is first installed and maintained intermittently Data supports core user activities Data is less dynamic (occasionally changes in response to changes in the environment, external functional processes, and/or business rules of the functional area)

Steps for Performing an Enhancement Project Functional Size

1. Gather and review available documentation 2. Meet with the SME to discuss changes planned/made 3. Identify and evaluate added functionality 4. Identify and evaluate changed functionality -determine complexity of function prior to and after change 5. Identify and evaluate deleted functionality 6. Identify and evaluate any conversion or one-time functionality required to implement this enhancement

Degrees of Influence

0 - Not present or no Influence 1 - Incidental Influence 2 - Moderate Influence 3 - Average Influence 4 - Significant Influence 5 - Strong Influence throughout

14 General System Characteristics

1. Data Communications 2. Distributed Data Processing 3. Performance 4. Heavily Used Configuration 5. Transaction Rate 6. On-Line Data Entry 7. End-User Efficiency 8. On-Line Update 9. Complex Processing 10. Reusability 11. Installation Ease 12. Operational Ease 13. Multiple Sites 14. Facilitate Change

File

A set of related records treated as a unit

Functional User Requirements

A subset of the user requirements Requirements that describe what the SW should do in terms of tasks and services

Substitution Data

Provides a code and an explanatory name or description for an attribute of a business object May serve as a quick means of data entry for experienced users May also be implemented to save storage space or may be a result of normalization Ex. State Code and State Name, Color Code and Color Description

Valid Values Data

Provides a list of available values for an attribute of one or more business object types Implemented to satisfy requirements such as reducing errors and increasing user friendliness Typically used to list available values for user selection or validation of input provided by the user

Static or Constant Data

Rarely Changes Three Types: -One Occurrence -Static Data -Default Values

Data Function

Represents functionality provided to the user to meet internal and external data storage requirements Either an External Interface File (EIF) or Internal Logical File (ILF)

Count two similar EPs as the same elementary process if they satisfy all of the following:

Require the same set of Data Element Types (DETs) Require the same set of Record Element Types (RETs) Require the same set of processing logic to complete the elementary process

What is not Conversion Functionality

SW upgrades due to the installation of a revised version of vendor packages The migration of an application to a new platform The conversion of data accomplished via an existing load utility A changed EIF for the application being measured

Types of Processing Logic Requirements

Validations are performed Mathematical formulas and calculations are performed Equivalent values are converted Data is filtered and selected by using specified criteria to compare multiple sets of data Conditions are analyzed to determine which are applicable One or more ILFs are updated One or more ILFs or EIFs are referenced Data or control information is retrieved Derived Data is created by transforming existing data to create additional data Behavior of the application is altered Prepare and present information outside the boundary Capability exists to accept data of control information that enters the boundary of the application Sorting or arranging a set of data

Data or control information can be received by which transactional function types

All Types - EIs, EOs, and EQs It is mandatory that an EQ receive data or control information

At least one ILF or EIF can be referenced by which transactional function types

All Types - EIs, EOs, and EQs It is mandatory that an EQ reference at least one ILF or EIF

Information can be prepared and then presented outside the boundary by which transactional function types

All Types - EIs, EOs, and EQs It is mandatory for both EOs and EQs to prepare and present information outside the boundary

Business Data

Aka Core User Data or Business Objects Reflects the information needed to be stored and retrieved by the functional area addressed by the application

Code Data

Aka List Data or Translation Data Provides a list of valid values that a descriptive attribute may have

A set of data can be sorted and arranged by which transactional function types

All Types - EIs, EOs, and EQs

Conditions can be analyzed to determine which are applicable by which transactional function types

All Types - EIs, EOs, and EQs

Converting equivalent values can be performed by which transactional function types

All Types - EIs, EOs, and EQs

Data can be filtered and selected by using specified criteria to compare multiple sets of data by which transactional function types

All Types - EIs, EOs, and EQs

Validations can be performed by which transactional function types

All Types - EIs, EOs, and EQs

Data or control information entering the boundary of the application can be accepted by which transactional function types

All Types - EIs, EOs, and EQs It is mandatory for EIs to accept data or control information entering the boundary of the application

Merge

Multiple files with the same data elements consolidated into a single file

Data Entities

Business Data Reference Data Code Data

DET Rules

Count one DET for each unique user-recognizable, non-repeated attribute that crosses the boundary during the processing of the transactional function Count only one DET per transactional function for the ability to send application response message even if there are multiple messages Count only one DET per transactional function for the ability to initiate actions even if there are multiple means to do so

Rules for Counting RETs

Count one RET for each data function Count one additional RET for each of the following additional logical subgroups of DETs (within the data function) that contains more than one DET: -Associative entity with non-key attributes -Subtype (other than the first subtype) -Attributive entity, in a relationship other than mandatory 1-1 Do not count RETs for any data that exists because technology or methodology (headers, trailers, separate text files)

Functional User Requirements Include:

Data Transfer Data Transformation Data Storage Data Retrieval

Code Data Physical Characteristics

Data consists of key fields and usually one or two attributes only Data typically has a stable number of records Data can represent 50% of all entities in the third normal form Data is sometimes de-normalized and placed in one physical table with other Code Data Data may be implemented in different ways

Reference Data Physical Characteristics

Data has key fields and few attributes Data contains usually at least one record or a limited number of records

Business Data Physical Characteristics

Data has key fields and usually many attributes Data may have 0 - infinity records

Business Data Logical Characteristics

Data is mandatory for operation of the users' functional area Data is user identifiable (usually by a business user) Data is user maintainable (usually by a business user) Data stores the users' Core User Data to support business transactions Data is very dynamic in that normal business operations cause it to be regularly referenced and routinely added to, changed, or deleted Data is reported on

Code Data Logical Characteristics

Data is mandatory to the functional area but optionally stored as a data file Data is not usually identified as part of the functional requirements but are usually identified as part of the design to meet nonfunctional requirements Data is sometimes user maintainable (usually by a user support person) Data is used to standardize and facilitate business activities and business transactions Data is essentially static and only changes in response to changes in the way that the business operates Business transactions access Code Data to improve ease of data entry, improve data consistency, ensure data integrity, etc If recognized by the user, the data is sometimes considered as a group of the dame type of data and could be maintained using the same processing logic

Control Information

Data that influences and elementary process by specifying what, when, or how data is to be processed

Technical Requirements Characteristics

Dependent on technology Terminology unfamiliar to the user may be used Functionality may be determined by placing too much emphasis on technical constraints Boundaries may be determined according to the technical architecture rather than business processes

Purpose of Function Point Count

Determine the type of FP count and the scope of the required count to obtain the answer to the business problem Influence the positioning of the boundary between the SW under review and the surrounding SW

Behavior of the application can be altered by which transactional function types

EIs and EOs It is mandatory for both EIs and EOs to alter the behavior of an application EQs cannot alter the behavior of an application

Derived data can be created by which transactional function types

EIs and EOs It is mandatory that an EO create derived data EQs cannot create derived data

Mathematical calculations can be performed by which transactional function types

EIs and EOs It is mandatory that an EO perform at least one mathematical calculation EQs cannot perform mathematical calculations

At least one ILF can be updated by which transactional function types

EIs and EOs It is mandatory the each EI and EO update at least one ILF EQs cannot update ILFs

Transactional Functions

External Inputs, External Outputs, and External Inquiries Perform the process of storing, updating, retrieving, and displaying the logical data Elementary processes that provide functionality to the user to process data

Attribute

Generally analogous to a Data Element Type (DET)

ILF Primary Intent

Hold data maintained through one or more elementary processes of the application being measured

ELF Primary Intent

Hold data referenced through one or more elementary processes within the boundary of the application being measured

General System Characteristics Definition

Set of 14 questions that evaluate the overall complexity of the application

Elementary Process

Smallest unit of activity that is meaningful to the user -Is meaningful to the user -Constitutes a complete transaction -Is self-contained -Leaves the business of the application being counted in a constant state

Corrective Maintenance

Software maintenance performed to correct faults in hardware or software

Perfective Maintenance

Software maintenance performed to improve the performance, maintainability, or other attributes of a computer program

Adaptive Maintenance

Software maintenance performed to make a computer program usable in a changed environment

Reference Data

Stored to support the business rules for the maintenance of the Business Data

Types of Code Data

Substitution Data Static/Constant Data Valid Values Data

Refresh

The process of recreating a set of data to make it current with it's source

Load

To copy computer instructions or data from external storage to internal storage

Copy

To read data from a source, leaving the source data unchanged, and to write the same data elsewhere in a physical form that may differ from that for the source

Conversion Functionality

Transactional or data functions provided to convert data and/or provide other user-specified conversion requirements Based on the user view of the data