Usage Guidelines

High Level Estimation (To be used when providing a high level estimate before requirements stu
1. Provide value for expected test requirements
2. The no. of test cases that can be expected of different complexities for the test requirements is auto-calculated
3. The number of test cases of different complexity levels are auto-calculated
4. Based on the project's past data, the values in the 'Basis for Estimation' section need to be updated by the PM/TL

Detailed Estimation (To be used when the requirement study is complete

1. Based on the requirement specfications, break down the testable rquirements to the lowest possible level
2. List the low level requirements in 'Details-Analysis' and 'Details-Execution' sheets and assign a complexity ratin
for all the facots.
3. Average complexity is automatically calculated
4. Based on the average complexity and the wighted complexity guidelines provided on the details sheets, assign th
complexity for each low level requirement
5. The no. of test cases that can be expected of different complexities for the test requirements is auto-calculated
Total No. of Test Case for Requirement of Specified Complexity - This is the total number of test cases (low/ Med
complexities) that are required to completed test one of the specified complexity test requirement - For e.g. For 1 c
requirement, 10 test cases may be required, out of which, 7 may be Complex, 1 Medium and 2 may be Simple test

6. The number of test cases of different complexity levels are auto-calculated

7. Based on the project's past data, the values in the 'Basis for Estimation' section need to be updated by the PM/TL
s

stimate before requirements study is complete)

st requirements is auto-calculated

on need to be updated by the PM/TL

quirement study is complete

s to the lowest possible level

sheets and assign a complexity rating to each requirement

vided on the details sheets, assign the weighted

st requirements is auto-calculated
otal number of test cases (low/ Medium/ High
ty test requirement - For e.g. For 1 complex test
1 Medium and 2 may be Simple test cases.

on need to be updated by the PM/TL

 Testing Effort Estimates - Initial

Total No. of Test Requirements 15

Level of Complexity Count of Test Total No. of Test
Requirements Case for
Requirement of
Specified
Complexity

Complex 6 210
Medium 6 120
Simple 3 30

Total No. of Expected Test Cases

Total Man days

Other Factors
Project Familiarity Type 1 5.00

Query Resolution during Preparation phase (% of total Test 10% 4.20

Preparation Effort)
Test Data Preparation Effort 20% 8.40
Regression Pack Revision (PDs)
Test Preparation - Review and Rework 5% 2.10
Regression (PDs)
Defect Management effort (% of total test execution effort) 10% 4.20

Project Management (FTA Efforts in both Preparation and 15% 12.60

Execution Phase)
Retesting / Re-execution of scripts (% of total Test Execution 15% 6.30
Efforts)
Contingency (e.g.Downtime. %of total Test execution efforts) 10% 4.20

Total Effort 118.40

 Basis of Es

Productivity Standards (No.of Test Cases processed per

Total Number PDs - Test PDs - Test
of Test Cases Preparation Execution
for Specified
Complexity

108 21.60 21.60

108 10.80 10.80 Phase Simple Medium Complex
144 9.60 9.60 Prepration 15 10 5

360.00 Execution 15 10 5
42.00 42.00 Project Familarity
Type PDs
Type 1 5
Type 2 10

Type 3 15

Type 4 20
Expected % of Requirements for Complexity Levels
Simple 20
Medium 40
Complex 40

Expected Test Case Count Per Complexity Level of Test

Simple 10

Medium 20

Complex 35
Expected % of Test Cases of Complexity Levels

Simple 40
Medium 30
Complex 30
 Basis of Estimation

Test Cases processed per person per day)

for Complexity Levels

Complexity Level of Test Requirement

Complexity Levels
 Testing Effort Estimates - Initial

Test Preparation
Level of Complexity Count of Test
Requirements

Complex 0
Medium 0
Simple 0

Total No. of Expected Test Cases

Total Man days
Test Execution
Level of Complexity Count of Test
Requirements

Complex 0
Medium 0
Simple 0
Total No. of Expected Test Cases
Total Man days

Other Factors
Project Familiarity Type 1
Query Resolution during Preparation phase (% of 10%
total Test Preparation Effort)
Test Data Preparation Effort 20%
Regression Pack Revision (PDs)
Test Preparation - Review and Rework 5%
Regression (PDs)
Defect Management effort (% of total test 10%
execution effort)
Project Management (FTA Efforts in both 15%
Preparation and Execution Phase)
Retesting / Re-execution of scripts (% of total Test 15%
Execution Efforts)
Contingency (e.g.Downtime. %of total Test 10%
execution efforts)
Total Effort
Testing Effort Estimates - Initial

Test Preparation
Total No. of Test Case for Requirement Total Number of Test PDs - Test
of Specified Complexity Cases for Specified Preparation
Complexity
0 0 0.00
0 0 0.00
0 0 0.00

0
0.00
Test Execution
Total No. of Test Case for Requirement Total Number of Test PDs - Test
of Specified Complexity Cases for Specified Execution
Complexity
0 0 0.00
0 0 0.00
0 0 0.00
0.00
0.00

Other Factors

0.00

0.00

0.00

0.00

0.00

0.00

0.00

0.00
 Basis of Estimation
Productivity Standards (No.of Test Cases processed per person per day)

Phase Simple Medium Complex

Prepration 15 10 5
Execution 15 10 5

Project Familarity
Type PDs
Type 1 5
Type 2 10

Type 3 15
Type 4 20

Expected Test Case Count Per Complexity Level of Test Requirement

Simple 10
Medium 20
Complex 35
Expected % of Test Cases of Complexity Levels
Simple 40
Medium 30

Complex 30
Detailed Estimates - Test Analysis

SI.No. Test Requirement

Team's Testing Impact Input
Domain Knowledge
Knowledge of team

Guidelines for Weighted Complexity

Average of the complexity assigned for different

parameters (excluding the NA parameters)

Less than 3
Between 3 and 4
More than 4
 Complexity
Output No. of Other Report Field Complexity of Alternative Average
Apps checks validations the test data Flows Complexity
Affected involved

Complexity

Suggested
Weighted
Complexity
1-Simple
2-Average
3-Complex
 Comments
Weighted
Complexity
Detailed Estimates - Test Execution

SI.No. Test Requirement Complex

Batch Runs Dependency Complexity
Required in of test cases
Environment
Set-up

Guidelines for Weighted Complexity

Average of the complexity assigned for different

parameters (excluding the NA parameters)

Less than 3
Between 3 and 4
More than 4
 Complexity
Run time test Report checks Input Output Average Weighted
data set-up Complexity Complexity

r Weighted Complexity

ned for different Suggested

arameters) Weighted
Complexity
1-Simple
2-Average
3-Complex
Comments
 Defining Complexity of functionality to be Tested
Parameter Description

Analysis
Team's Domain Knowledge Domain knowledge required to understand the requirement

Testing Knowledge of team The expertease of the TA on the required domain

Impact How many modules from the same system/app are involved

Input Data No of input parameters for this requirement

Output Data No of output parameters for this requirement

No of applications affected The no of related applications the requirement refers to

Report checks The complexity of the reports that are being generated
Field validations involved Complexity of field validations involved

Complexity of the test data Effort required for test data set-up

Alternative Flows Average alternative flows in the use cases or functional docs
for the module

Execution
Batch Runs Required

Dependency in Environment Set-up

Complexity of test cases

Run time test data set-up

Report checks

Input Data

Output Data
ality to be Tested
Rules - Complexity Paramaters

1-Experts
2-Experienced
3-As Required
4-Not sufficient
5-None

1-Experts
2-Experienced
3-As Required
4-Not sufficient
5-None

1 - Impact on 1 other module

2 - Impact on 2 other modules
3 - Impact on 3 other modules
4 - Impact on 4 other modules
5 - Impact on 5 or more other modules

1 - 1 Input parameter
2 - 2 Input parameters
3 - 3-4 Input parameters
4 - 5 Input parameters
5 - More than 5 input parameters

1 - 1 Output parameter
2 - 2 Output parameters
3 - 3-4 Output parameters
4 - 5 Output parameters
5 - More than 5 Output parameters

1 - Low Impact on 1 other applications

2 - Low Impact on 2-3 other applications
3 - High Impact on 1 other applications
4 - High Impact 2-3 other applications
5 - High impact on more than 3 other applications

1 - 1 Report with 1-10 datasets

2 - 1-2 reports with 1-10 datasets
3 - 1-2 reports with 10-15 datasets
4 - 2-3 reports with more than 15 datasets
5 - More than 3 reports
1 - 2-3 Field validations
2 - 4-5 Field Validations
3 - 5-7 Field Validations
4 - 7-10 Field Validations
5 - More than 10 Field Validations

1 - Generic data can be used, no validations

2 - Specific data required, validations applicable
3 - Simple test data, affects the functional flow
4 - Complex test data with few combinations, each affecting
the expected results
5 - Complex test data with many combinations, each affecting
the expected results

1 - 1-2 Conditional Statements

2 - 3-5 Conditional Statements
3 - 6-8 Conditional Statements
4 - 9-10 Conditional Statements
5 - More than 10 Conditional Statements

1 - Short time, no set-up required

2 - Longer time, no set-up required
3 - Short time with simple set-up
4 - Longer time with simple set-up
5 - Long batch runs with complex set-up

1 - Simple set-up done by test team

2 - Simple set-up done by test team with help from support
team
3 - Complex set-up done by test team
4 - Complex set-up done by support team with help from
support team
5 - Complex set-up, completely done by support team

1 - Detailed test cases, simple functionality

2 - Test cases not very detailed, simple functionality
3 - Detailed test cases, complex functionality
4 - Test cases not very detailed, complex functionality
5 - Test cases not very detailed, complex functionality
1 - Simple test data, procedure to get the data is known and
documented in test approach
2 - Simple test data, procedure to get the data is not known
3 - Complex test data, , procedure to get the data is known
and documented in test approach
4 - Complex test data, procedure to get the data is not known
5 - Test data requirements not known atall

1 - 1 Report with 1-10 datasets

2 - 1-2 reports with 1-10 datasets
3 - 1-2 reports with 10-15 datasets
4 - 2-3 reports with more than 15 datasets
5 - More than 3 reports

1 - 1 Input parameter
2 - 2 Input parameters
3 - 3-4 Input parameters
4 - 5 Input parameters
5 - More than 5 input parameters

1 - 1 Output parameter
2 - 2 Output parameters
3 - 3-4 Output parameters
4 - 5 Output parameters
5 - More than 5 Output parameters
 COPYRIGHT © 2003-2008 HSBC Software Development (India) Pvt. Ltd.

All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted, in any
form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written
permission of HSBC Software Development (India) Pvt. Ltd.

Template Version History

Current Version
Date Version Description Author
5-Mar-08 1.0 Baselined SEPG

Previous Versions
Date Version Description Author
14-Feb-08 0.1 Initial draft Shilpa Pitke
opment (India) Pvt. Ltd.

d in a retrieval system or transmitted, in any

ing or otherwise, without the prior written
t (India) Pvt. Ltd.

Approved/Reviewed By
PCCB

Approved/Reviewed By
SEPG