Want to get rolling with a Source Code Analysis (SCA) tool as efficiently as possible? “Do what the smart companies do,” says Mark Grice, a Klocwork Director and Manager of the International Reseller/Partner Network. In our last discussion, Grice outlined three best practices for SCA tools selection: involve your...

Want to get rolling with a Source Code Analysis (SCA) tool as efficiently as possible?

“Do what the smart companies do,” says Mark Grice, a Klocwork Director and Manager of the International Reseller/Partner Network.

In our last discussion, Grice outlined three best practices for SCA tools selection: involve your developers, limit your selection to market-leading tools, and identify a deadline.

According to Grice, smart companies take those best practices and:

Buy an introductory package and pick one development team that will deploy the SCA tool.

Do an in-depth performance analysis after six months.

Expand the rollout to other teams…or not.

“After the six-month period,” says Grice, “a company will widen its deployment circle and get more licenses.”

On the other hand, Grice says it’s also possible that the company will decide to try another tool from their panel of tools. They won’t need to re-evaluate because they’ve got a short list to pull from.

“They don’t lose, whichever way it goes,” he says. “During that six-month period, they got value from that tool by applying it to their codebase, learning about SCA and cleaning up their code.”