1
Copyright © Serena Software 2015
Take your code and quality to the next level
With Dimensions CM & Kiuwan
Hosted by Don Irvine
VP of ALM Products
September 10th, 2015
2
Agenda
Introduction
Why measure software quality
How to measure software quality
Our Solution - Kiuwan
How Kiuwan integrates with Serena Pulse
Demo – Kiuwan & Serena Pulse
3
4
More than 2,000 users… and growing
Global and local partners around the world
5
how many businesses today
do NOT
depend on software?
6
would you buy a car from a company
who does not assure quality?
7
Knight Capital algorithmic trading software goes
haywire
Market-making firm Knight Capital Group – the largest trader in
U.S. equities - made headlines last August when its algorithmic
trading software malfunctioned, resulting in wild price swings on the
New York Stock Exchange.
The rogue robot cost the company $440 million to ‘trade out’ of its
entire erroneous trade position, as it saw its own stocks plummet.
8
8
What are the common software quality issues?
• Software does not fulfill user
nor business expectations.
• Bad requirements
• Software has security issues.
• Software is not stable.
• Software is difficult to use
• Response times soar under
heavy loads.
• Software changes are costly.
• Software can also have “toxic
assets”
9
9
Why measure software quality?
10
What is software quality in the broader sense?
Quality = Testing + … not only testing.
o The # of functional defects is a quality indicator but not the only
one
o Wider angle approach: verify the compliance with standards
and normatives, avoid common coding and configuration ,
detect design anti-patterns defects, make software easier to
maintain, and in general technically measure other
characteristics (efficiency, portability, security, reliability…)
11
11
How much does software quality cost?
The PAF* model: More prevention, less failure, improve Defect Removal
Efficiency
Find the quality level to minimize Cost of Quality
•
12
What can you do about it?
• The goal is reach your required levels of quality balancing
the cost with the savings you will get by having those quality
levels.
• This will yield to a high Defect Removal Efficiency (DRE)
and reduce total cost.
• Focusing only in 3 possible quality assurance techniques:
Static Code analysis, Peer Reviews and Testing (functional
mostly)
• A combination of the 3 of them implies a best overall cost
scenario: 33% more cost efficient than only doing testing.
13
How can you do it?
• Integrate all quality assurance practices in your SDLC.
• Automate Static Code Analysis to have a continuous
analysis and measurement process. It is the only way to
detect and remove code defects as early as possible.
• Use static analysis information to make your peer review
process more efficient
• Automate testing as much as you can.
14
Local analysis or in the cloud
Simulations
Code defects
Action plans
Portfolios
Quality model management
Detailed reports
ALM Integration
Continuous code quality and security in the cloud
http://www.kiuwan.com
15
Integration with Dimensions CM
16
Overview
• Integration between Serena Dimensions CM Pulse & Kiuwan
• Provided out-of-the-box with Dimensions CM 14
• Visibility of quality information
• Part of the health of your development activity
• Shown alongside health/quality metrics from other tools
• Aids the Peer Review process
• Can enable continuous analysis
• Measuring quality and finding issues on every delivery
• Also allows scheduled or manual analysis
17
Providing information for Peer Review
• Results of analysis run shown on Peer Review page
• Details about the run
• Overview of metrics reported by Kiuwan
• URL link to Kiuwan for further information
• Defects shown alongside the code
• Indication of defect severity and some details of the defect
• Helps the reviewer make decision about the review
• Bringing quality information together in one place
• Build, static analysis, style checkers, security analysis tools etc
18
Measuring health/quality of changes
• Visibility of metrics from Kiuwan
• Configurable report views
• Trends, Percentages, Counts for a Stream
• Is quality getting better or worse?
• Shown alongside data from other tools
• Release readiness of a Stream
• Quality metrics reflected on the branch graph
• Link to Kiuwan Dashboard
19
20
Thank you
www.serena.com

Take your code and quality to the next level by Serena Software

  • 1.
    1 Copyright © SerenaSoftware 2015 Take your code and quality to the next level With Dimensions CM & Kiuwan Hosted by Don Irvine VP of ALM Products September 10th, 2015
  • 2.
    2 Agenda Introduction Why measure softwarequality How to measure software quality Our Solution - Kiuwan How Kiuwan integrates with Serena Pulse Demo – Kiuwan & Serena Pulse
  • 3.
  • 4.
    4 More than 2,000users… and growing Global and local partners around the world
  • 5.
    5 how many businessestoday do NOT depend on software?
  • 6.
    6 would you buya car from a company who does not assure quality?
  • 7.
    7 Knight Capital algorithmictrading software goes haywire Market-making firm Knight Capital Group – the largest trader in U.S. equities - made headlines last August when its algorithmic trading software malfunctioned, resulting in wild price swings on the New York Stock Exchange. The rogue robot cost the company $440 million to ‘trade out’ of its entire erroneous trade position, as it saw its own stocks plummet.
  • 8.
    8 8 What are thecommon software quality issues? • Software does not fulfill user nor business expectations. • Bad requirements • Software has security issues. • Software is not stable. • Software is difficult to use • Response times soar under heavy loads. • Software changes are costly. • Software can also have “toxic assets”
  • 9.
  • 10.
    10 What is softwarequality in the broader sense? Quality = Testing + … not only testing. o The # of functional defects is a quality indicator but not the only one o Wider angle approach: verify the compliance with standards and normatives, avoid common coding and configuration , detect design anti-patterns defects, make software easier to maintain, and in general technically measure other characteristics (efficiency, portability, security, reliability…)
  • 11.
    11 11 How much doessoftware quality cost? The PAF* model: More prevention, less failure, improve Defect Removal Efficiency Find the quality level to minimize Cost of Quality •
  • 12.
    12 What can youdo about it? • The goal is reach your required levels of quality balancing the cost with the savings you will get by having those quality levels. • This will yield to a high Defect Removal Efficiency (DRE) and reduce total cost. • Focusing only in 3 possible quality assurance techniques: Static Code analysis, Peer Reviews and Testing (functional mostly) • A combination of the 3 of them implies a best overall cost scenario: 33% more cost efficient than only doing testing.
  • 13.
    13 How can youdo it? • Integrate all quality assurance practices in your SDLC. • Automate Static Code Analysis to have a continuous analysis and measurement process. It is the only way to detect and remove code defects as early as possible. • Use static analysis information to make your peer review process more efficient • Automate testing as much as you can.
  • 14.
    14 Local analysis orin the cloud Simulations Code defects Action plans Portfolios Quality model management Detailed reports ALM Integration Continuous code quality and security in the cloud http://www.kiuwan.com
  • 15.
  • 16.
    16 Overview • Integration betweenSerena Dimensions CM Pulse & Kiuwan • Provided out-of-the-box with Dimensions CM 14 • Visibility of quality information • Part of the health of your development activity • Shown alongside health/quality metrics from other tools • Aids the Peer Review process • Can enable continuous analysis • Measuring quality and finding issues on every delivery • Also allows scheduled or manual analysis
  • 17.
    17 Providing information forPeer Review • Results of analysis run shown on Peer Review page • Details about the run • Overview of metrics reported by Kiuwan • URL link to Kiuwan for further information • Defects shown alongside the code • Indication of defect severity and some details of the defect • Helps the reviewer make decision about the review • Bringing quality information together in one place • Build, static analysis, style checkers, security analysis tools etc
  • 18.
    18 Measuring health/quality ofchanges • Visibility of metrics from Kiuwan • Configurable report views • Trends, Percentages, Counts for a Stream • Is quality getting better or worse? • Shown alongside data from other tools • Release readiness of a Stream • Quality metrics reflected on the branch graph • Link to Kiuwan Dashboard
  • 19.
  • 20.