Difference between revisions of "References"

From OWASP
Jump to: navigation, search
(References)
(References)
Line 3: Line 3:
 
==References==
 
==References==
  
# Brian Chess and Gary McGraw.  ''Static Analysis for Security,'' ''IEEE Security & Privacy'' 2(6), 2004, pp. 76-79.
+
# Brian Chess and Gary McGraw.  "Static Analysis for Security," ''IEEE Security & Privacy'' 2(6), 2004, pp. 76-79.
 
# M. E. Fagan.  "Design and Code Inspections to Reduce Errors in Program Development," ''IBM Systems J.'' 15(3), 1976, pp. 182-211.
 
# M. E. Fagan.  "Design and Code Inspections to Reduce Errors in Program Development," ''IBM Systems J.'' 15(3), 1976, pp. 182-211.
 
# Tom Gilb and Dorothy Graham.  ''Software Inspection''.  Addison-Wesley, Wokingham, England, 1993.
 
# Tom Gilb and Dorothy Graham.  ''Software Inspection''.  Addison-Wesley, Wokingham, England, 1993.

Revision as of 17:05, 19 January 2009

OWASP Code Review Guide Table of Contents

Contents


References

  1. Brian Chess and Gary McGraw. "Static Analysis for Security," IEEE Security & Privacy 2(6), 2004, pp. 76-79.
  2. M. E. Fagan. "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems J. 15(3), 1976, pp. 182-211.
  3. Tom Gilb and Dorothy Graham. Software Inspection. Addison-Wesley, Wokingham, England, 1993.
  4. Michael Howard and David LeBlanc. Writing Secure Code, 2nd edition. Microsoft Press, Redmond, WA, 2003.
  5. Gary McGraw. Software Security. Addison-Wesley, Boston, MA, 2006.
  6. Diomidis Spinellis. Code Reading: The Open Source Perspective. Addison-Wesley, Boston, MA, 2003.
  7. John Viega and Gary McGraw. Building Secure Software: How to Avoid Security Problems the Right Way. Addison-Wesley, Boston, MA, 2001.
  8. Karl E. Wiegers. Peer Reviews in Software. Addison-Wesley, Boston, MA, 2002.