Posts Tagged "static code analysis"
Imagine that your company has software maintenance issues, perhaps one reason is the technical debt you have, even if you are not aware of it. Many of the clients I deal with on pre-sales meetings, don’t know why, year after year, have maintenance cost growth, and they are not even familiar with the “technical debt” concept.
I have recently read a very interesting article by Steve Garnett. I would like to share with you some of the concepts presented in it, using a dummy situation between a doctor and her patient.Read More
Just a quick post about the importance of bug tracking. If you can spare some extra time, I encourage you to read Jim Bird’s recent article “A Bug is a Terrible Thing to Waste” in his blog. He writes about how bugs are tracked —or not tracked at all— in different kinds of projects, in particular in his projects
My takeaway is that you have to pay attention to every single bug you find. You should track the most important ones or the ones you can’t fix immediately.Read More
On many articles we have talked about software quality. However, it is almost always at a high level, but where does all this come from? In this article I would like to be more mundane, leave abstractions alone and focus on what software developers do in daily life. I am going to talk about something that to some people seems obvious, for others it is silly, but in my opinion it has great impact on the final outcome of a product, and it is very easy to overlook. I am referring to coding and naming conventions and best practices.Read More
Who are the target users of application quality tools?
This question has been banging in my head for some time now, and the answer is not simple. As probably know by now, here at Optimyth Software, we develop and sell quality assurance tools based on static code analysis. So, why has this been bothering me? I should now, right? Okay, you caught me, I do know. But, it is a tricky question. Let me explain myself.Read More
In previous posts we have seen the importance of using techniques such as static code analysis on your software. In fact, experts say that you can detect up to 60% of potential defects with these techniques.
When a static code analysis tool is checking the code, it is looking for the use of good practices used by developers in their implementations. Good practices can come from standards such as IBM standards for Cobol or Sun recommendations for Java, from books or from our experience. For static code analysis good practices are implemented by rules that the developers should comply with.Read More