Archive for June, 2009

  • T.E.S.T.: Doctoring the Code (page 32)

    on Jun 30, 09 • by Lynn Gayowski • with No Comments

    Alen Zukich, director at source code analysis specialist Klocwork explores how software testing can help save lives while reducing costs in the rapidly changing medical device industry. When lives are at stake, software bugs are not just a nuisance, they can have serious, and even fatal, consequences. A glitch in a medical device can mean peacemakers don’t keep hearts beating, diabetics can’t check their insulin levels and a patient’s heart isn’t properly monitored. Not to mention the lost revenue and damaged brand reputation for the manufacturer. Read More

    Read More »
  • Static analysis for Ruby/Python

    on Jun 29, 09 • by Denis Sidorov • with 13 Comments

    As a developer of static analysis tool for mainstream statically-typed languages, like C++ and Java, I was wondering for quite a while about how well static analysis applies to dynamically-typed languages, like Ruby and Python. And recently, I have come across this interesting project on GitHub: Reek – Code smell detector for Ruby. Well, I suppose that’s just a fancy way to name a static analysis tool. What can Reek detect? It does not do heavyweight data/control flow analysis, so the list is not very exciting: Code Duplication – AFAIU, it’s not very accurate, ’cause

    Read More »
  • Top Reasons To Not Go Scrum/Agile

    on Jun 25, 09 • by Todd Landry • with 5 Comments

    There was a recent blog on the top 10 good reasons for Scrum, so in the spirit of equality, I thought I would do one on the top 10 reasons not to go Scrum. Now, before I get started, let it be known that I am a huge fan of Scrum and agile (so much in fact that I am certified as a Product Owner), but there are definitely situations where it just might not make sense to go that route. 1. Your development team is geographically dispersed. In my opinion, this is the main

    Read More »
  • Parallel Lint

    on Jun 22, 09 • by Alen Zukich • with 2 Comments

    Interesting article on static analysis tools to help find concurrency issues.  These so called “Parallel Lint” tools are specific to finding these types of issues.  Overall there are some great discussions on certain tools, and it is always nice when Klocwork gets mentioned.  But my problem is with the categorization of these tools.  It always makes me feel sick every time someone puts Klocwork in the same category of “powerful static analysis” with JLint, C++Test, FXCop and my favorite PC-Lint. This article goes deeper into PC-Lint and what they are doing with deadlocks.  The author

    Read More »
  • Get the red out…

    on Jun 17, 09 • by Todd Landry • with 1 Comment

    When I first started at Klocwork, I didn’t really know a lot about source code analysis. I understood the basic concept of how it finds bugs in software, but that is was essentially it. Sure I knew about Memory leaks, but I truly believed that they were only found a day or two before the GA date…at least, that was when our testing team always found them. In one of my teams prior to joining Klocwork, we used Scrum. We were hard core, with daily 15 minute scrums, retrospective meetings, sprint planning sessions, defining “done”,

    Read More »
  • Klocwork Named to SD Times 100 List in Security Category

    on Jun 16, 09 • by Meranda Powers • with No Comments

    Recognition marks fifth consecutive year yhat company’s developer productivity solutions are recognized by SD Times 100 BURLINGTON, Mass. — Jun 16, 2009 — Klocwork Inc., the global leader in automated source code analysis solutions for improving developer productivity, today announced it has been named to the SD Times 100 List for the fifth consecutive year. SD Times names companies and organizations of all sizes who have demonstrated leadership and innovation that contributes to the advancement of software development managers, developers and the industry over the past calendar year. SD Times has recognized Klocwork in the

    Read More »
  • Agile compatible with safety-critical development?

    on Jun 15, 09 • by Brendan Harrison • with 1 Comment

    Agile Documentation

    Interesting paper and presentation (pdf) from Emmanuel Chenu at Thales Avionics that describes how they’re using several Agile concepts as part of their safety-critical avionics software projects. With the exception of pair programming, my read is that much of this is mapping activities that have been done in a safety-critical environment (e.g. test driven development) to several Agile principles, rather than the introduction of concepts that are foreign to safety-critical development. The other one that probably hasn’t been done in most safety-critical shops is continuous integration, but I’d argue that CI (or at least a

    Read More »
  • JavaOne 2009: On Trust and Types

    on Jun 11, 09 • by Lynn Gayowski • with No Comments

    The JVM’s promise of write once, run anywhere works most of the time. But it can also make programmers complacent about cases where the WORA promise fails, says Gwyn Fisher, CTO of Klocwork, maker of the eponymous code analysis tool. One such case is resource management, where the JVM’s latent garbage collector necessitates that developers think about the machine behind the VM. In this interview with Artima, Fisher describes cases where well‐known Java APIs work differently based on deployment platform, and how well‐defined type systems can make resource management more reliable: Read More

    Read More »
  • The Tech Herald: IT And The Economy

    on Jun 8, 09 • by Lynn Gayowski • with No Comments

    Like it or not, economics will pull the strings in any and, like other department, IT is affected. The next session of The Tech Herald’s look at IT and the economy involves Mike Laginski, CEO of Klocwork. Laginski took on all of the original questions, taking advantage of the extended deadline to the Q&A topic, and gave us some honest thoughts on what he sees. Klocwork is a company that deals mainly with software development teams who, like it or not, have been told to do more with less. As Laginski explains, Klocwork is stepping

    Read More »
  • “Oh, if only it were open source…”

    on Jun 8, 09 • by Gwyn Fisher • with 1 Comment

    Don’t get me wrong, I’m a big fan of open source, but why does everything have to be black and white? If it’s closed it must be evil and by association probably not written well, whereas if it’s open, it’s awesome and godly in its unnatural power to cure world hunger? I’m referring, in this particular instance, to the righteous indignation that surfaced as a result of the castigation served up for the manufacturers of that ever-popular device, the breathalyzer. And yes, I’ve been stood at the side of the road looking stupidly at the

    Read More »
Scroll to top