template f pandu cp

7/27/2019 Template f Pandu Cp

1/26

This section has the project scope whose estimation will be done


2/26


3/26

Function Point Analysis

Project Name

ILF

EIF

EO

EQ

EI

Total Unadjusted Function Points

Total GSC

Total Adjusted Function Points

Programmer can complete how much FP per day(Productivity Factor)

Total Man Days

Use Case Point Analysis

Use Case Entity

Total UAW

Total UUCW

Total UUCP

Adjusted UCP

Hours

Days (By Karner Way)

Comparison Between Unadjusted Function Points and Unadjusted Use Case PointsTotal Difference between Unadjusted Values (UUCP-UAFP)

Factor Difference UAFP/UUCP

Number of elements in FP

EI

EO

EQ

ILF

EIF

Total Elements in FP

Number of Use Case in UCP

Number of actors

Total Elements in UCP

Total Difference in Elements (FP-UCP)


4/26

0

0

0

0

0

0

0.65

0

0.85

0

Use Case Entity Values

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0


5/26

Functionality DET RET Value

0

0

0

0


6/26

DET's considers RET's considerd


7/26

Functionality DET RET Value DET's considerd RET's considered

0


8/26

Functionality DET FTR Value DET's considered FTR's considerd

0


9/26

Functionality DET FTR Value DET's considerd

0

0

0

0


10/26

FTR's Considerd


11/26

Functionality DET FTR Value

0

0

0

0

0

00

0

0

0

0

0

0

0


12/26

DET's considerd FTR's Considerd


13/26

GSC Attribute Definitions Value

Data communications

How many communication facilities are

there to aid in the transfer or exchange of

information with the application or system?

Distributed data processingHow are distributed data and processing

functions handled?

PerformanceDid the user require response time or

throughput?

Heavily used configuration

How heavily used is the current hardware

platform where the application will be

executed?

Transaction rateHow frequently are transactions

executed; daily, weekly, monthly, etc.?

On-Line data entryWhat percentage of the information is

entered On-Line?

End-user efficiencyWas the application designed for end-user

efficiency?

On-Line update How many ILFs are updated by On-Linetransaction?

Complex processingDoes the application have extensive

logical or mathematical processing?

ReusabilityWas the application developed to meet

one or many users needs?

Installation easeHow difficult is conversion and

installation?

Operational easeHow effective and/or automated are start-

up, back up, and recovery procedures?

Multiple sites

Was the application specifically designed,

developed, and supported to be installedat multiple sites for multiple organizations?

Facilitate change

Was the application specifically designed,

developed, and supported to facilitate

change?

GSC 0.65


14/26

Guidelines from ifpug.org CPM guide

EI Counting Rules

Control information is received from outside the application boundary.

The control information is specified by the user to ensure compliance with business function

requirements.

For the identified process, one of the following two rules applies:

1) Processing logic is unique from other external inputs for the application.2) Data elements are different from other external inputs identified.

FTR Counting Rules

Count each ILF maintained.

Count each ILF or EIF read during processing.

Count only one FTR when an ILF is both maintained and read.

DET Counting Rules

Count each user recognizable and nonrecursive field. Each user recognizable and

nonrecursive field must be maintained on an ILF.

Count each field that is not entered by the user, but through an EI is maintained on an ILF

Count physical implementation techniques as a single DET for the entire group of fields.

EIF Counting Rules

The group of data is a logical group that fulfills specific user requirements.

The group of data is referenced by, and external to, the application being counted.

The group of data is not maintained by the application being counted.

The group of data is counted as an ILF for at least one other application.

The group of data identified has not been counted as an ILF for the application.

EO Counting Rules

The process sends data or control information external to the application boundary.

The process is the smallest unit of activity that is meaningful to the end user in the business.

The elementary process is self-contained and leaves the business in a consistent state.


Processing logic is unique from other EOs.

Data elements are different from other EOs.

EQ Counting Rules

An input request enters the application boundary.

Output results exit the application boundary.

Data is retrieved.

The process is the smallest unit of activity that is meaningful to the end user in the business.

The elementary process is self-contained and leaves the business in a consistent state.

The data retrieved does not contain derived data.

The processing does not update an ILF.


Processing logic is unique from other EQs.

Data elements are different from other EQs.


15/26

Actor Name Weight


16/26

Description so that third person can understand


17/26

Use Case Name Number of Transactions Weight

0

0

0


18/26



19/26

Technical Factor Weight Value Weighted Value

Distributed System 2 0

Response time 1 0

End user efficiency 1 0

Complex internal processing 1 0

Reusable code 1 0

Installation ease 0.5 0

Easy use 0.5 0

Portable 2 0

Easy to change 1 0

Concurrent 1 0

Security objectives 1 0

Direct access to third parties 1 0

User training facilities 1 0

Total TCF 0.6

Guide lines for each factor is inside comments : Please note these are guidelines pr


20/26

Description so a third person can understand

Application copies files to main back up system

No special requirement as its batch process which runs at night speed is of not prime importance

Simple navigation for Network administrator.

There is extensive logical processing in terms of browsing through folders and files and copying them across

This is first time the company is making this application so no reusable code is available and second there is no scop

Network administrator are technical guys who can do themselves

As used by network administrator no special user freindliness is needed.As network administrator are them self quiet t

Only should work on windows 2000 server.See assumptions for details

No special requirement as such for now.

No requirement as such

Its in house no requirement as such

No requirement as such

Network administrator can understand the application by themselves

vided by me depending on my experience and some taken from function point guidelines itself. There is no g


21/26

for reusability in application itself as its too small

echnical guys.

verning body who has approved it so use it at your own risk


22/26

Environmental Factor Weight Value Weighted Value

Familiarity with project 1.5 0

Application experience 0.5 0

Object-oriented programming experience 1 0

Lead analyst capability 0.5 0

Motivation 1 0

Stable requirements 2 0Part-time Staff -1 0

Difficult programming language -1 0

Total EF 1.4

Guide lines for each factor is inside comments : Please note these are guideline


23/26


everybody know the project very well as the requirements are very clear

20 % percent application experience people are available

Have 2 years of OOPs experience

Have around 2 years experience lead analyst leading the project

Project beign small team has less motivation

Requirements do no changesNo part time staff

Programming language is VB.NET

provided by me depending on my experience and some taken from function point guidelines its


24/26

elf. There is no governing body who has approved it so use it at your own risk


25/26

Use Case Look Up

0 0

1 5

2 5

3 5

4 10

5 106 10

7 10

8 15

9 15

10 15

These are look up values used in use case do not touch this section


26/26

Guidelines to write Use Case

Use Case Scenario should be non-recursive and processing logic should be different from other Use Cases.

Role / Actor should be non-recursive.

Minimum User goal level use case should be indentified.

If two Use Cases have 60 % in common try to accommodate them using alternate scenario. Example CRUD

operation Create,Read,Update and delete should come in one Use Case with alternate scenarios.

If UseCase is exceeding 25 transactions split Use Case in two UseCases.Every transaction in Use Case should add buisness value from User Perspective.

Sub-function level Use Case should be used to Capture algorothmic complexity.

Mapping Rules to be followed so that Use Case Point and Function Point can be compared.

Every Elementary process (EI,EO,EQ,ILF and EIF) should be mapped to a Use Case,.

Comparison can only be done on Unadjusted values that is on Unadjusted Function Points and Unadjusted Use

Case PointsGroup of Function Point EP's can map in to one Use Case.Its possible than Use Case and EP will not have one

to one mapping.

Every ILF and it associated EI should be mapped to a Use Case

Every EIF and it associated EI should be mapped to a Use Case

Actors have no equivalent mapping in EP

template f pandu cp

Documents