Archive for April, 2012

  • Static analysis is NOT Bugzilla

    on Apr 24, 12 • by Alen Zukich • with 1 Comment

    Static analysis is NOT Bugzilla

    Time and time again I get asked, how does static analysis fit into my existing bug tracking system? ”I need an integration with my system (i.e. Bugzilla) because that is what we use everyday. Every time I find a bug I need to track this through my system.” This is where I take a deep breath as I scream on the inside. Taking every bug and putting that into your bug tracking system is just wrong. Horribly wrong. The best way I can describe this is through the compiler analogy. Every time you add a feature or bug fix,

    Read More »
  • Making static analysis simple, one squiggly line at a time

    on Apr 10, 12 • by Brendan Harrison • with No Comments

    Making static analysis simple, one squiggly line at a time

    As we continue to rollout Klocwork Insight 9.5 our message around making static analysis simple is taking hold. To put the change we’ve made into its appropriate context, let’s think about how spell checkers mainstreamed, and how a somewhat obvious (looking back) usability change turned this amazingly useful technology from something you do at the end of writing a document, to an activity that just automatically works while you create documents, making people more productive in the process.         On the surface the difference looks subtle but the changes are huge. The

    Read More »
  • Answering questions about your code base — Part 2

    on Apr 2, 12 • by Patti Murphy • with No Comments

    Answering questions about your code base — Part 2

    In this continuing story about the journey to source code awesomeness, we left off at the point where we identified priority defect types for your organization, kicked off pre-checkin static analysis on developer desktops and saw build-over-build improvements in our trending reports as a result. The next question we tackle here is: What is my cost of ownership? The answer, my friend, is not blowing in the wind, it’s in your Complexity Trend report: Why there? you might ask. Well, it’s because there’s a straight-line correlation between the complexity of a function and its cost per

    Read More »
Scroll to top