This Article 
 Bibliographic References 
 Add to: 
A Clinic for "Secure" Programming
March/April 2010 (vol. 8 no. 2)
pp. 54-56
Matt Bishop, University of California, Davis
Everyone has had problems with software. Some problems are particularly serious, such as the program on a satellite that contains an error, causing the loss of expensive equipment. So how can we develop better software? One way is to make good programming as much a part of learning computer science as good writing is a part of studying English and law. To test this idea, we developed a secure-programming clinic.

1. P.G. Neumann, Computer-Related Risks, Addison-Wesley, 1995.
2. B. Curtis, "Top Five Causes of Poor Software Quality," Datamation, 1 July 2009; article.php/3827841Top-Five-Causes-of-Poor-Software-Quality.htm .
3. Computer Science Curriculum 2008: An Interim Revision of CS 2001, ACM and IEEE CS, Dec. 2008; .
4. M. Bishop and B.J. Orvis, "A Clinic to Teach Good Programming Practices," Proc. 10th Colloquium Information Systems Security Education, 2006, pp. 168–174.

Index Terms:
programming, robust programming, security and privacy, writing clinics, software engineering, software engineering education
Matt Bishop, "A Clinic for "Secure" Programming," IEEE Security & Privacy, vol. 8, no. 2, pp. 54-56, March-April 2010, doi:10.1109/MSP.2010.62
Usage of this product signifies your acceptance of the Terms of Use.