Steps for Using this Model

1 Fill up the required project details in the Project Information sheet

2 Identify number of Feature points in the application in Size Estimation testing sheet

3 Identify number of data transactions in Size Estimation testing sheet

Enter values for C, I, R, S, A, L, T, V, U in Size Estimation testing sheet from the
4 Guidelines sheet

Enter % distribution for the Tasks specified in the Value(V) column of Size Estimation
5 testing sheet
6 Enter the assuptions taken for doing the estimation, if any.

Version 1.0 Classification: Birlasoft Internal

 Project Details

Project Name Date of Estimation

Project Code Project Start Date

Project Manager Expected End date

SQAR Account Manager

Estimated Size Estimated Effort

Actual Size Actual Effort

Reasons for Variation if any:

Version 1.0 Classification: Birlasoft Internal

 Estimation sheet
Un-adjusted Test Points UTP Value Adjustment Factor (VAF) 0
= FP + DP (C+I)*(R+S)*(A+L)*T*(U+V)

No of Features points FP Complexity ( C )

No of Data Transactions DP Interfacing ( I )

Reusability (R)

Adjusted Test Points ATP Support System (S)

=UTP *VAF
Automated Tools (A)

Estimated Effort Uni-lingual / Multilingual (L)

Third Party Interfacing (T)

Roles and Browser Compatibility(V)

Customer CTQ(U)

Weighted Test Estimated

Estimated man
Tasks (T) Value (V) Points Effort in man
days(PD's)
WTPA=TPA*V hrs

A:Project Initiation (5-10%)

B : Planning (10-20%)
C : Test Design (20- 40%)
D : Test Execution (20-40%)
E : Consolidation of Test Results (5-
15%)

Total Effort from Size

Estimated Effort

Assumptions if Any:

Version 1.0 Classification: Birlasoft Internal

 Guidelines for Value Adjustment Factors Criteria

♦ Complexity ( C ) : Complexity of a function is derived from the logic and the

algorithm of the function. It depends on how many validation and how many condition are
there in the function

Complexity Factor Description No of conditions in a function

0.2 Low No more than five conditions
0.3 Medium Conditions between 6 to 11
0.5 High The functions containing more
than 11 conditions

♦ Interfacing ( I ) : Interfacing is an expression of the extent to which a modification in a given

function affects other parts of the system. The degree of interfacing is determined by ascertaining
first the logical data sets which the function in question can modify, then the other functions which
access these data sets.

Interfacing/ Dependency factor Interfacing of modules

Dependency
1 Low <30%
2 Medium 30 to 50%
4 High >50%

♦ Reusability (R) : This refers to the artifacts that are available in the organization database and
can be utilized in the project.

Reusability factor Reusability / Prior Description

Experience

Version 1.0 Classification: Birlasoft Internal

3 Low
2 Medium
1 High
No other features is similar to this
Upto 50% similarity is there with
some other feature
More than 50% similarity is there
with some other feature

♦ Support System (S) : This refers to the availability of the supporting documents
that enable a better understanding of the application.

Availability Factor Availability Description

3 Low
2 Medium
1 High
No supporting document or help is
available
Some initial specs are available
and old system is existing for
reference
More than 50% support document
is available

♦ Automated Tools (A) : The planning and control tools variable reflects the extent to
which automated resources are to be used for planning and control.

Availability factor Availability Description

3 Low
2 Medium
No automated tools for defect
tracking and version control is
available
Either an automated CM system or
an automated defect tracking
system is available

Version 1.0 Classification: Birlasoft Internal

1 High Both an automated defect tracking
system and CM are available

♦ Unilingual / Multilingual (L) : The number of languages on which the application needs to be
tested will have a direct impact on the testing effort.

Factor Number of languages Description

1 Low
2 Medium
3 High
The application has to be tested on
a single language interface
The application is to be tested on
two languages.
The application is to be tested on
more than two languages.

♦ Third party interfacing (T) : An application having third party interfacing would have
more number of areas to be tested.

Factor Interfacing extent Description

3 High More than 60% functionality
interfaces with third party
applications
2 Medium Between 30% and 60%
functionality interfaces with third
party applications

Version 1.0 Classification: Birlasoft Internal

1 Low Less than 30% functionality
interfaces with third party
applications

♦ Roles and Browser Compatibility (V)- This refers to the number of roles and browsers
on which the application has to be tested.

Factor Roles and Browser Description

extensibility
3 High The number of roles to be tested is
more than 10
2 Medium The number of roles to be tested is
between 4 and 10
1 Low The number of roles to be tested is
less than 4

♦ Customer CTQ (U) : The importance the user attaches to a given application relative to
other systems

Importance Factor User- Importance Description

3 High
2 Medium
The application is a real time
mission critical one
The importance of the application
relative to the other application is
normal

Version 1.0 Classification: Birlasoft Internal

1 Low The importance of the application
relative to the other application is
low for instance applications to be
used for internal purposes.

Version 1.0 Classification: Birlasoft Internal