Вы находитесь на странице: 1из 12

Calculation Mechanism for Impact factor

Classification of Degree of
Impact Element Impact Element

Business Priority Select Degree


Complexity of Work Select Degree
Technology Select Degree
Onsite Support (elective) Select Degree
Proficiency of QA Team Select Degree

Risk Impact Factor (Avg. of Resultant Factor)


r Impact factor

Risk Weightage of Impacted element Resultant Factor


representation (A numeric
representation for Risk Priority)

Select Risk Priority 1


Select Risk Priority 1
Select Risk Priority 1
Select Risk Priority 1
Select Risk Priority 1

1.00
NEXT
ESTIMATION SHEET
Degree of Weightage of
Feature /
QA Activities Complexity Recurring Functional Risk
Module / CR
Activity
One Time Activity
Select Degree F1 Select Risk Priority
Requirement /
Use Cases Select Degree F2 Select Risk Priority
Analysis Select Degree F3 Select Risk Priority

Select Degree F1 Select Risk Priority


Simple Low
TC Designing
Select Degree F2 Select Risk Priority
Select Degree F3 Select Risk Priority
Select Degree F1 Select Risk Priority
Regression Select Degree F2 Select Risk Priority
Select Degree F3 Select Risk Priority
Recurring Activity
Select Degree F1 1 Select Risk Priority
Functional
Select Degree F2 1 Select Risk Priority
Testing
Select Degree F3 1 Select Risk Priority
Select Degree F1 0.25 Select Risk Priority
TC Updation Select Degree F2 0.25 Select Risk Priority
Select Degree F3 0.25 Select Risk Priority

Size of Testing assignment (TQTP)


Sub total of one time activity (Person h
Sub total of Recurring activities (Person h
QA Iterations plann
Total QA Effort Estimates (Person Hour
Total QA Effort Estimates (Person Days)
default 3 cycle = [One time tasks + 3* (Recurring Tasks) ]
Size of Avg. Man Hr =
Impact
Activity Resultant Factor X
Factor
(TQTP) Impact Factor

1 1
1 1 Click for Degree of Complexity
1 1
1 1 Click for Functional risk
1 1.00
1 1
1 1
1 1
1 1
1 1

1 1
1 1
1 1
1
1.00 0.25
1 0.25
1 0.25

16
tal of one time activity (Person hr) 6
of Recurring activities (Person hr) 3.75
QA Iterations planned 3
ort Estimates (Person Hours) 17
2
egree of Complexity details

Functional risk details


DEGREE OF COMPLEXITY
SIMPLE
Number of functionalities getting affected (developed) in
Front End is > =1<=4; Known Functionality & Feature.
If it’s CR development & Affecting > 1 < =2 functionality.
(~20 %).
Change in Screen Layout without change in structures and
not affecting more than 25 % of application functionalities
Business risk involved is <40%
(simple Information collection & search, employee profiler,
request/approval system with simple business logic)
DEGREE OF COMPLEXITY
AVERAGE
Number of functionalities getting affected (developed) in Front
End is >4<=8
If it’s CR development & Affecting > 2 <= 5 functionality. (~40
%).
Change in Screen Layout without change in structures and
not affecting more than 50 % of application functionalities.
Business risk involved is 40-70%
(simple e-Learning , Information search, employee profiler,
request/approval system with average business logic)
COMPLEX
Number of functionalities getting affected (developed) in
Front End is >8
If it’s CR development & Affecting > 5 functionality (~60 %).

Change in Screen Layout without change in structures and


affecting more than 50 % of application functionalities.
Business risk involved is 70-100%
(Complicated e-commerce, Banking, ERP, Third Part / E-
Payment / currency transaction involvement and
request/approval system with complex business logic)
FUNCTIONAL RISK PARAMETERS
Low
Number of processes (E2E Scenario) involved is >= 1<3
Maximum actor involved in system is >=1 < 3.

Features enhancement rather than the entirely new CR.

Involves change in the system forcing to system forcing to


V&V ~25% system (impact analysis)
FUNCTIONAL RISK PARAMETERS
Medium
Number of processes (E2E Scenario) involved is >= 3<5
Maximum actor involved in system is >=3<5

Developing utilities from scratch and feeding other


processes.
Involves change in the system forcing system forcing to
V&V ~40% system (impact analysis)
High
Number of processes (E2E Scenario) involved is >= 5.
Entirely fresh development & involving maximum actor in
system is >=5
Developing entirely new utilities / processes / functionality

Involves change in the system forcing to V&V >50%


system (impact analysis) OR entire system altogether

Вам также может понравиться