Slides of February 2011 Java User Group in Lausanne dedicated to Software Quality Analysis
Videos soon available on Parleys: http://parleys.com/#id=102931&st=4
28. Coverity Integrity Center
Precision Software Analysis Across Lifecycle
• Increase customer satisfaction by
eliminating product delays and recalls
caused by software problems
• Speed time to market by making software
changes faster and with less risk
• Innovate rapidly by reducing time
developers spend fixing software design,
code, and delivery problems
29. Steps To Mitigate Risk
1 Scan Fix
Emacs
your priority
software defects
4
5 Report
Integrity defect
Analysis
Engine
remediation
Map
2 Find defect
priority impact PRODUCTS
List of Defects
_ 10001 critical
defects
_ 10002 major
Browse code 3 Project 1
_ 10003 major
_ 10004 critical Code
Project 2
_ 10005 major base
Impact Rankings Project 3
30. Shared Code Branching & Defect Impact
2.6.2.1 release
2.6.2 release
Merge
2.6 release
fix
Mainline/Trunk/Head/Development
2.4 release
2.4.1 release
Defect in the original Defect introduced in a Defect introduced in a
development branch and release branch before a release branch after a
never fixed affects all merge merge
products
31. Analyze 2.6, 2.6.2 and 2.6.2.1 releases
Branch of a codebase:
Project 2.4
2 streams
2.6.2.1 release
2.6.2 release
2.6 release
Mainline/Trunk/Head/Development
2.4 release
2.4.1 release
32. Common Defects are merged by CIM
Branch of a codebase:
Project 2.4
2 streams
2.6.2.1 release
Stream 1
2.6.2 release Project 2.6
Stream 2
2.6 release Stream 3
Mainline/Trunk/Head/Development
2.4 release
2.4.1 release