Development Intelligence
How I love that phrase “Development Intelligence”, patterned after business intelligence. Unfortunately it appears Borland has got a lock on that phrase.
But the concept of continuous measurement and the ability to use metrics to proactively manage and monitor a software development project is so valuable.
I was recently discussing an automated QA tool with someone who had looked at it. It had several hundred rules for quality software. It even used McCabe’s complexity metric. Those were good things. Only problem is they run it at the end of a project, not during, for example when a single programmer’s work is being checked in or even before when something can still be done be done about quality issues. Congratulations, the 4000 function point application you just took ownership of violates 117 quality rules. What do I do with that except negotiate in an outsource environment.
But continuous Development Intelligence. Imagine, a developer skips a standard, or whose code is on immediately understandable… And ti getting flagged before check-in. The vast majority of developers want to do a good job and a tool that helps them find and catch quality errors sounds like a significant total ownership cost improvement.
Related posts
Comments
Leave a Reply
