Posts Tagged ‘Software Deployment’

  • 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 1

    on Feb 8, 12 • by Patti Murphy • with 1 Comment

    Answering questions about your code base – Part 1

    Static analysis captures the current state of your code base and helps you answer key questions about the quality, security and maintainability of your software project. Think Magic 8 Ball with build omniscience and powerful reporting tools. OK, maybe Magic 8 Ball isn’t a good analogy. Answers to what questions, you ask? One we often hear from customers is: Where do I start? A good place to start is a report that captures the distribution of defect types from your current build.  For example, we recommend that our customers glance over the Top 10 Issues

    Read More »
  • Top 10 List: Well Traveled Path to Source Code Analysis Success

    on May 31, 11 • by Brendan Harrison • with 1 Comment

    The Code Integrity folks have developed a lot of best practices on deploying static analysis and have compiled many of them in a solid whitepaper. They include a Top 10 list of what they call “The Well Traveled Path to Success”. Below is their (somewhat paraphrased in spots) list. 1. Determine who cares. Who has a vested interest that bugs actually get fixed. How much do they care? 2. Get an expert to tune the solution for your codebase. Static analysis tuning will maximize defect finding while minimizing false positives. 3. If possible, pilot with

    Read More »
Scroll to top