What if you could eliminate the hidden costs of development?

1© 2017 Rogue Wave Software, Inc. All Rights Reserved. 1
Confronting the mission-
critical software testing
challenge
Episode 3:
What if you could eliminate the hidden
costs of development?
Alan McKellar
V.P. software development
Walter Capitani
Product manager, Klocwork

Presenter
Alan McKellar
V.P. software development
Rogue Wave Software
alan.mckellar@roguewave.com
Twitter: @AlanMcKellar
Walter Capitani
Product manager, Klocwork
Rogue Wave Software
walter.capitani@roguewave.com
Twitter: @walter_capitani

1. What are “hidden costs”?
2. Code reviews
3. A bug’s life
4. Issue crowdsourcing
5. Wait times
6. Klocwork static code analysis
7. Q&A
Agenda

What are “hidden costs”?

What everyone else says

What we’re talking about today
A different perspective on things that we know happen
every day
Time/resources consumed but not identified, tracked, or
acted upon

Poll #1
Which of the following hidden costs has the largest impact on your
organization?
• Open source software costs
• Server downtime
• Support issues / customer escalations
• Lack of skills
• Delayed or rushed releases

Code reviews

Not enough code reviews
“Further analysis revealed that individual inspection performance varied by a
factor of 10 in terms of faults found per unit time and individuals found on average
about 53% of the faults.”
1. DZone / Agile Zone, August 22, 2014
2. “Testing the value of checklists in code inspections,” Hatton, 2007
1
2

Why the reluctance?
• Expensive
– Multiple people working on the same module
• Developers would rather create than review
– Find other ways of “reviewing”
Yet we all know early detection is cheaper to fix

Static code analysis
if(i = j) j++;
if(i == j) j++;
Defect: Assignment
operator used in
conditional statement
Assignment operator
replaced with intended
comparison operator
Vulnerable Code
Fixed Code

• 80% of defects are introduced in development
• Each defect found in test costs 50x to fix
Why the reluctance?

A bug’s life

Much more than fixing code
Impact on stakeholders
Sales
Forced to avoid
selling the
feature
Sales
Spending time on
the phone
Development
Fixing issues rather
than creating new
features
Marketing
Can’t talk about it
Support
Another brick in
the wall
Marketing
Impact to brand
image
C-suite
Applying pressure!

Tools like Klocwork shorten cycle times, making it easier
to meet delivery times.

Issue crowdsourcing

How many people does it take to fix a bug?
“I found a bug!”
“Now, how do I
fix it?”
“I can help.”
“Have you tried this?”
“I’ve seen this
before.”
“Is it fixed
yet?”
MANAGER

Be faster than Googling it
• Takes time to understand and translate results to your
specific situation
• No validation that the “answer” is best for you
“Using Klocwork is WAY FASTER than Googling it!”
- Walter Capitani, Feb. 2017

Test environment vs. real world

Wait times

“The silent killer”*
30 days (53%) spent waiting between phases
“Define a software delivery strategy for business innovation,” Forrester Research, Inc., July 2014

Shull et al estimate that non-severe defects take
approximately 14 hours of debugging effort after release,
but only 7.4 hours before release.
* “What we have learned about fighting defects,” Shull et al, 2002

Poll #2
For your last major customer escalation incident, how did you feel about
the effort to resolve the problem?
• Less than I was willing to put in
• About what I expected
• More than I was willing to put in

What could you have done instead of working
on that problem we just polled?

Klocwork static code analysis

Check code earlier & faster
• Issues identified at your desktop
– Correct code before check-in
• Issues identified through Continuous
Integration
– Instant feedback at scale
• SmartRank recommendation engine helps
prioritize work
• Create custom checkers to meet specific
needs
• Debugger-like call-stack highlights the
cause of the issues

Summary
• Ineffective code reviews
• Impact of bugs on the organization
• How many people does it take to fix a bug?
• “The silent killer”

Q & A

Try Klocwork now
www.klocwork.com/free-trial

Available for binge watching
www.roguewave.com/sca
Episode 1: How to achieve security, reliability, and productivity in less time
Episode 2: Static analysis works for mission-critical systems, why not yours?
Episode 3: What if you could eliminate the hidden costs of development?
www.roguewave.com/webinars
Car cybersecurity: What do the automakers really think?
Five ways to create more secure code
Static analysis’ role in automotive functional safety (ISO 26262)

What if you could eliminate the hidden costs of development?

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (14)

Similar to What if you could eliminate the hidden costs of development?

Similar to What if you could eliminate the hidden costs of development? (20)

More from Rogue Wave Software

More from Rogue Wave Software (20)

Recently uploaded

Recently uploaded (20)

What if you could eliminate the hidden costs of development?

Editor's Notes