Compartir a través de

Top 25 software errors

  • Artículo

SANS, along with a coalition of individuals and software organizations, just released their list of top "25 most dangerous programming errors". There has been some talk of making these a "requirement" or some sort of logo program to help protect customers when deciding which software to use or purchase.

 

From a developer's perspective you should review these and ensure your design and code are doing the right thing. From a tester's perspective, be sure you have cases in place to validate and document how you are verifying these. If the items do become a hard requirement your group will probably have to provide proof of what was tested and how.

 

Ideally your team is doing all this anyway, but if not, here is a handy checklist to get started.

Comments

  • Anonymous
    October 08, 2012
    We develop software help desk, remote support, inventory and IT asset management, easy to implement and use. We wish we kept abreast of all the innovations that have been made today.

  • Anonymous
    September 25, 2014
    Great blog. Why have you stopped writing? Please feel free to provide me feedback on my blog at qetes.com/symantec-endpoint-protection