The document outlines 10 reasons to use static testing techniques for risk mitigation in software projects. Static testing can be more efficient than dynamic testing, and allows testing of code before it is executable. It helps find errors early in the development process when they are cheaper to fix. Static testing also aims to directly find failures, reduces project costs, and improves testware quality when used with other testing approaches. The document encourages identifying additional reasons and risks static testing could help address for specific projects.

1. 10+ Reasons To Use
Static Testing Techniques
Risk Analysis
Mikhail Pavlov
Tuesday, 30 April, 13

2. “Risk management is project
management for adults.”
Tom DeMarco “Waltzing With Bears”,
2003
2
Tuesday, 30 April, 13

3. Reason 1
Static testing is more
efficient than other
approaches
3
Tuesday, 30 April, 13

4. Reason 1 - Risk
Mitigation
Schedule and efforts overrun
Product quality level is lower than
expected
4
Tuesday, 30 April, 13

5. Reason 2
Static testing can be
conducted even if an
object of testing is not
ready to be executed
5
Tuesday, 30 April, 13

6. Reason 2 - Risk
Mitigation
Later application-under-test
readiness for testing
Time for test execution is not
sufficient
6
Tuesday, 30 April, 13

7. Reason 3
Static testing helps to find
errors early
7
Tuesday, 30 April, 13

8. Reason 3 - Risk
Mitigation
Information about application-
under-test quality is not available
for project stakeholders on time
Timeframes for fixing defects are
not sufficient
8
Tuesday, 30 April, 13

9. Reason 4
Sometimes static testing is
the only approach to test
on time
9
Tuesday, 30 April, 13

10. Reason 4 - Risk
Mitigation
Requirements and design defects can leak out
to subsequent SDLC phases
Requirements and design defects are harder
to find and more expensive to fix later in SDLC
Tests executed are not enough to achieve a
certain level of quality
10
Tuesday, 30 April, 13

11. Reason 5
About half of defects
detectable by dynamic
testing techniques can be
found using static testing
11
Tuesday, 30 April, 13

12. Reason 5 - Risk
Mitigation
Defect leakage to production
Late defect detection
Inefficient use of testing resources
12
Tuesday, 30 April, 13

13. Reason 6
Static testing aims to find
failures directly
13
Tuesday, 30 April, 13

14. Reason 6 - Risk
Mitigation
High debugging costs
Higher testing costs
14
Tuesday, 30 April, 13

15. Reason 7
The highest product quality
can be delivered to
customer when static
testing is used in synergy
with other approaches
15
Tuesday, 30 April, 13

16. Reason 7 - Risk
Mitigation
Product quality level is lower than
expected (esp. for mission-critical
systems)
Project execution discipline does
not match project goals
16
Tuesday, 30 April, 13

17. Reason 8
Static testing reduces total
costs of a project
17
Tuesday, 30 April, 13

18. Reason 8 - Risk
Mitigation
Budget overrun
High rework efforts
18
Tuesday, 30 April, 13

19. Reason 9
Static testing of testware
leads to its higher defect
detection power
19
Tuesday, 30 April, 13

20. Reason 9 - Risk
Mitigation
Insufficient test coverage
Goals of test scripts cannot be achieved
Unreliable test automation framework
Defects leakage to production
20
Tuesday, 30 April, 13

21. Reasons 10+
What are your reasons to use
static testing in your project?
What risks do you mitigate?
Tuesday, 30 April, 13