|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Secure Software Development by Example
July/August 2005 (vol. 3 no. 4)
pp. 10-17
| ASCII Text | x | ||
| Axelle Apvrille, Makan Pourzandi, "Secure Software Development by Example," IEEE Security & Privacy, vol. 3, no. 4, pp. 10-17, July/August, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/MSP.2005.103, author = {Axelle Apvrille and Makan Pourzandi}, title = {Secure Software Development by Example}, journal ={IEEE Security & Privacy}, volume = {3}, number = {4}, issn = {1540-7993}, year = {2005}, pages = {10-17}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2005.103}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Security & Privacy TI - Secure Software Development by Example IS - 4 SN - 1540-7993 SP10 EP17 EPD - 10-17 A1 - Axelle Apvrille, A1 - Makan Pourzandi, PY - 2005 KW - Security KW - software development KW - life cycle VL - 3 JA - IEEE Security & Privacy ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2005.103
When trying to incorporate security into a program, software developers face either too much theoretical information that they can't apply or exhaustive and discouraging recommendation lists. This article gives an overview of security concerns at each step of a project's life cycle.
Index Terms:
Security, software development, life cycle
Citation:
Axelle Apvrille, Makan Pourzandi, "Secure Software Development by Example," IEEE Security & Privacy, vol. 3, no. 4, pp. 10-17, July-Aug. 2005, doi:10.1109/MSP.2005.103
Usage of this product signifies your acceptance of the Terms of Use.