Code audit

"If you don't have time to do it right, when will you have time to do it over?"

- John wooden

It just proves to be right over and over again. Whenever it was decided that the best course of action is to take no action Murphy's[1] law just proves itself right once more and "Anything that can go wrong will go wrong, and it will happen at the worst possible time".

Lots of software companies faced this problem and it greatly affected their reputation or more their lives[2]. From small 3-4 teams writing internal software to huge teams, the problem of bugs being introduced to applications creeps at sometime to make life less enjoyable.

Being so important, the software community has always looked for methods of writing better code and building software with less bugs. The methods invloved ranged from static analysis tools to programming practices like pair programming[3].

We at Irisoft have built the experience over years to provide our services to help development teams:

  • Identify the most critical parts of their applications by making architecture reviews and threat models
  • Enhance their programming practices by reviewing their code and helping them fix problems while learning the best programming practices

We use code coverage analysis/testing, static code analysis tools and manual review to identity code problems that could impact performance, security and quality of the written software.

Technologies:

The main technologies we work with are PHP , SQL and C#

 

 

 


 

[1]http://en.wikipedia.org/wiki/Murphy's_law

[2]http://www.devtopics.com/20-famous-software-disasters/

[3]http://en.wikipedia.org/wiki/Pair_programming