Device Matrix

r
re
lo
xp
tE
e
rn

o
te
DEVICE Model OS OS Version Size Width Height

Go
In
iPad Air iOS 7.0.3 9.7 1536 2048
iPad 2 iOS 6.1.3 9.7 768 1024
Samsung Galaxy Tab 10.1 GT-P5110 Android 4.0.4/ 4.3 10.1 800 1280
Asus Transformer Pad infinity (TF700T) Android 4.2 10.1 1200 1920
 In
te
rn

Yes
e tE
xp
lo
Go re
o r

Yes
Yes
gle
Ch
ro
m
M e
oz

Yes
Yes
illa
Fir
ef
ox
Yes
Yes

Sa
fa
ri
Yes
Yes

An
dr
oi
d
S.No Activity
QA Analysis
1 Knowledge Transfer
2 Understanding business requirements & App architecture
3 Requirements Review/Walkthrough with Client/Technical clarifications
Total Analysis Time
Test Preparation
1 Test Planning
2 Test Environment setup
3 Authoring test cases
4 Test case Review/Rework
Total Authoring effort
QA Test Execution
1 Smoke Test
2 System test
3 Compatibility test
4 Interrupt testing
5 Defect Retest
6 Regression
7 Test Management
Total Execution effort
Closure Activities
1 Artifact Consolidation and Reporting

Screens
Complex
Medium
Simple

Low Level Test Scenarios/ screen

Complex
Medium
Simple

Authoring Effort
Complex
Medium
Simple

Execution Effort
Complex
Medium
Simple
 Man Hrs Man Days

45 5 Number of Resources
45 5 Interrupt Testing Percentage
45 5 Expected Defect Retest
135 15

48.00 5.33 No of Platforms

27.00 3.00 Total No. of device/OS/browser combinations
62.00 6.89 Compatibility percentage
6.20 0.69 Rounds of Regression
143.20 15.91 Regression Percentage

162.00 18.00 Localization/Internationalization Effort Percentage

1620.00 180.00 Number of languages/locales
648.00 72.00 Number of Releases
162.00 18.00 Percentage of new features in each new release
453.60 50.40
1458.00 162.00 Devices = 1 Emulators = 0
162.00 18.00 Native = 1 Web =0
4665.60 518.40

27 3

200
100
100

Per Screen Total

2 400
2 200
1.2 120
720
Per Test Case (Mins) Total Hrs
60 400
45 150
35 70
620
Per Test Case (Mins) Total Hrs
90 600
45 150
30 60
810
 1
10%
20%

2
6
10%
3
30%
 Effort for One App

S.No Activity Hrs

1 QA Analysis phase 135
2 Test Preparation phase 143.20
3 QA Test Execution phase 4665.60
4 Closure Activities 27
Total 4970.8

Resources 1
Total No. of person days 554.18611
No.of person weeks 110.83722
Total no.of weeks (Project Duration) 110.83722
Buffer Percentage 10%
Effort
S.No Activity Person Hrs
1 QA Analysis phase 148.5
2 Test Preparation phase 157.52
3 QA Test Execution phase 5132.16
4 Closure Activities 29.7
Total 5467.88
Person Days Person weeks
16.875 3.375
15.91 3.18222222222
518.40 103.68
3 0.6
554.1861111 110.837222222

Effort Duration
Person Days Person weeks Days Weeks Months
16.5 3.3 16.5 3.3 0.785714
17.50222222 3.50044444444 17.50222 3.500444 0.833439
570.24 114.048 570.24 114.048 27.15429
3.3 0.66 3.3 0.66 0.157143
607.5422222 121.508444444 607.5422 121.5084 28.93058
 2013 2014
Release
Dec Jan Feb Mar Apr May Jun

3
KT & environment set up
R1 Functional Testing
Test case Design
Test Execution 5
R2 Functional Testing
Test case Design
Test Execution 7
R3 Functional Testing
Test case Design
Test Execution 7
R4 Functional Testing
Test case Design
Test Execution 7
R5 Functional Testing
Test case Design
Test Execution 7 7

Total Resources 3 5 7 7 7 7 7
Onsite Test Lead
Sr Test Engineer
Offshore Test Lead
Sr Test Engineer
Test Engineer
Test Engineer
Test Engineer

Devices Count

iPad Air 1
iPad 2 2
Samsung Galaxy Tab 10.1 2
Asus Transformer Pad infinity 2
S.No

1
2
3
4
5
6
7

8
9

10
11

12
13

14
15

16
17
18
19
20
21
 Description

Assuming that this application is a Mobile Web app.

Effort was calculated based on the 400 screens as mention in the XXX assumptions. If any new screens are added, then the eff
Testing would be done using actual devices on browsers combinations identified in the device matrix.
Only functional and compatibility testing is considered part of testing scope.
Web services and database testing is not considered as part of the current scope.
Non Functional testing is not included in this effort estimation.
Devices for testing will be provided by customer

One round of regression would be performed for each sprint where the regression suite would constitute 20% of overall test c
Compatibility and functional testing would testing will be done for every sprint
CSC assumes the mobile web functionality is identical to the desktop web functionality and test cases developed for web can
testing
CSC assumes each sprint/iteration would last for 4 weeks and there would be a testable build at the start of each sprint
CSC assumes all unit tests shall be executed by XXX development team and a testable build will be provided. Build acceptance
to start of test execution activities.
Any schedule slippage in sprints will result in increase in timelines of the project duration with the proportionate increase in th
Test data should be provided by XXX before the testing starts and should be valid for the respective test cycle in a sprint. It sho
prior intimation to the testing team.
The batch jobs should be completed within 2 hours of raising the request. Any delay would increase the testing timelines.
The system test cases for mobile would include the 300 base test cases for portal and and additional 500 P1 and P2 test cases
60% of the test cases would be selected for mobile test execution.
If code quality is bad and result in unstable builds, CSC will recommend additional regression cycle and raise appropriate chan
All bug fixes by development team will be done within sprint cycle
Localization testing is out of scope
There are 4 user roles
Latest version of Chrome, firefox would be considered for cross browser testing apart from iOS and Android native browsers.
will increase accordingly.
 total 720
Reg suite 144

90 90 90 90
18 21.6 22.32
 90 90 90 90
22.464 22.4928 22.49856 22.49971